summaryrefslogtreecommitdiffstats
path: root/drivers/mcb
diff options
context:
space:
mode:
authorJohn Hurley2018-03-29 03:50:07 +0200
committerDavid S. Miller2018-03-30 16:18:55 +0200
commit29a5dcae2790ba7fb26ea7128cbe61ecf906ab0a (patch)
treef9ce1b086110ad43f50eb0fb08d3a7bb4d689eef /drivers/mcb
parentnfp: modify app MTU setting callbacks (diff)
downloadkernel-qcow2-linux-29a5dcae2790ba7fb26ea7128cbe61ecf906ab0a.tar.gz
kernel-qcow2-linux-29a5dcae2790ba7fb26ea7128cbe61ecf906ab0a.tar.xz
kernel-qcow2-linux-29a5dcae2790ba7fb26ea7128cbe61ecf906ab0a.zip
nfp: flower: offload phys port MTU change
Trigger a port mod message to request an MTU change on the NIC when any physical port representor is assigned a new MTU value. The driver waits 10 msec for an ack that the FW has set the MTU. If no ack is received the request is rejected and an appropriate warning flagged. Rather than maintain an MTU queue per repr, one is maintained per app. Because the MTU ndo is protected by the rtnl lock, there can never be contention here. Portmod messages from the NIC are also protected by rtnl so we first check if the portmod is an ack and, if so, handle outside rtnl and the cmsg work queue. Acks are detected by the marking of a bit in a portmod response. They are then verfied by checking the port number and MTU value expected by the app. If the expected MTU is 0 then no acks are currently expected. Also, ensure that the packet headroom reserved by the flower firmware is considered when accepting an MTU change on any repr. Signed-off-by: John Hurley <john.hurley@netronome.com> Reviewed-by: Jakub Kicinski <jakub.kicinski@netronome.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/mcb')
0 files changed, 0 insertions, 0 deletions