aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/target
diff options
context:
space:
mode:
authorDavid S. Miller <davem@davemloft.net>2017-06-07 12:51:42 -0400
committerDavid S. Miller <davem@davemloft.net>2017-06-07 12:51:42 -0400
commite5c5180a2302ecdee28c900d91256bbfe1a1e9fa (patch)
treee51a34a6a440ef9afa62946a4880cd15c01785d0 /drivers/target
parentnet: fec: Clear and enable MIB counters on imx51 (diff)
parentnfp: advertise support for NFD ABI 0.5 (diff)
downloadlinux-dev-e5c5180a2302ecdee28c900d91256bbfe1a1e9fa.tar.xz
linux-dev-e5c5180a2302ecdee28c900d91256bbfe1a1e9fa.zip
Merge branch 'nfp-ctrl-vNIC'
Jakub Kicinski says: ==================== nfp: ctrl vNIC This series adds the ability to use one vNIC as a control channel for passing messages to and from the application firmware. The implementation restructures the existing netdev vNIC code to be able to deal with nfp_nets with netdev pointer set to NULL. Control vNICs are not visible to userspace (other than for dumping ring state), and since they don't have netdevs we use a tasklet for RX and simple skb list for TX queuing. Due to special status of the control vNIC we have to reshuffle the init code a bit to make sure control vNIC will be fully brought up (and therefore communication with app FW can happen) before any netdev or port is visible to user space. FW will designate which vNIC is supposed to be used as control one by setting _pf%u_net_ctrl_bar symbol. Some FWs depend on metadata being prepended to control message, some prefer to look at queue ID to decide that something is a control message. Our implementation can cater to both. First two users of this code will be eBPF maps and flower offloads. ==================== Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/target')
0 files changed, 0 insertions, 0 deletions