qed: Correct default VF coalescing configuration
When starting the VF's vport, the PF would first configure the status blocks of the VF and then reset them. That would cause some of the configured information to be lost - specifically it would mean that all the VFs queues would use the Rx coalescing state-machine of the status block. Signed-off-by: Yuval Mintz <Yuval.Mintz@cavium.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
d91940818d
commit
b801b1591c
|
@ -1755,6 +1755,8 @@ static void qed_iov_vf_mbx_start_vport(struct qed_hwfn *p_hwfn,
|
|||
vf->state = VF_ENABLED;
|
||||
start = &mbx->req_virt->start_vport;
|
||||
|
||||
qed_iov_enable_vf_traffic(p_hwfn, p_ptt, vf);
|
||||
|
||||
/* Initialize Status block in CAU */
|
||||
for (sb_id = 0; sb_id < vf->num_sbs; sb_id++) {
|
||||
if (!start->sb_addr[sb_id]) {
|
||||
|
@ -1768,7 +1770,6 @@ static void qed_iov_vf_mbx_start_vport(struct qed_hwfn *p_hwfn,
|
|||
start->sb_addr[sb_id],
|
||||
vf->igu_sbs[sb_id], vf->abs_vf_id, 1);
|
||||
}
|
||||
qed_iov_enable_vf_traffic(p_hwfn, p_ptt, vf);
|
||||
|
||||
vf->mtu = start->mtu;
|
||||
vf->shadow_config.inner_vlan_removal = start->inner_vlan_removal;
|
||||
|
|
Loading…
Reference in New Issue