From: Sridhar Samudrala <sridhar.samudrala@intel.com>
To: alexander.h.duyck@intel.com, john.r.fastabend@intel.com,
anjali.singhai@intel.com, jakub.kicinski@netronome.com,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org
Subject: [net-next PATCH 0/6] i40e: Add VF port representator support or SR-IOV VFs
Date: Thu, 29 Dec 2016 22:20:57 -0800 [thread overview]
Message-ID: <1483078863-22026-1-git-send-email-sridhar.samudrala@intel.com> (raw)
- Patch 1 introduces devlink interface to get/set the mode of SRIOV switch.
- Patch 2 adds support to create VF port representor(VFPR) netdevs associated
with SR-IOV VFs that can be used to control/configure VFs from PF name space.
- Patch 3 enables syncing link state between VFs and VFPRs.
- Patch 4 adds a new type to metadata_dst to allow passing VF id to lower device.
- Patch 5 adds TX and RX support to VFPR netdevs.
- Patch 6 enables HW and SW VFPR statistics to be exposed via netlink on VFPR
netdevs.
Jakub Kicinski (1):
net: store port/representator id in metadata_dst
Sridhar Samudrala (5):
i40e: Introduce devlink interface.
i40e: Introduce VF Port Representator(VFPR) netdevs.
i40e: Sync link state between VFs and VFPRs
i40e: Add TX and RX support in switchdev mode.
i40e: Add support for exposing VF port statistics via VFPR netdev on
the host.
drivers/net/ethernet/intel/Kconfig | 1 +
drivers/net/ethernet/intel/i40e/i40e.h | 4 +
drivers/net/ethernet/intel/i40e/i40e_main.c | 96 +++++-
drivers/net/ethernet/intel/i40e/i40e_txrx.c | 132 ++++++++-
drivers/net/ethernet/intel/i40e/i40e_txrx.h | 1 +
drivers/net/ethernet/intel/i40e/i40e_type.h | 3 +
drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.c | 321 ++++++++++++++++++++-
drivers/net/ethernet/intel/i40e/i40e_virtchnl_pf.h | 25 ++
include/net/dst_metadata.h | 35 ++-
net/core/dst.c | 15 +-
net/core/filter.c | 1 +
net/ipv4/ip_tunnel_core.c | 6 +-
net/openvswitch/flow_netlink.c | 4 +-
13 files changed, 610 insertions(+), 34 deletions(-)
--
2.5.5
next reply other threads:[~2016-12-29 21:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-30 6:20 Sridhar Samudrala [this message]
2016-12-30 2:53 ` [net-next PATCH 0/6] i40e: Add VF port representator support or SR-IOV VFs David Miller
2016-12-30 16:55 ` Samudrala, Sridhar
2016-12-30 6:20 ` [net-next PATCH 1/6] i40e: Introduce devlink interface Sridhar Samudrala
2016-12-30 6:20 ` [net-next PATCH 2/6] i40e: Introduce VF Port Representator(VFPR) netdevs Sridhar Samudrala
2016-12-30 2:52 ` David Miller
2016-12-30 6:21 ` [net-next PATCH 3/6] i40e: Sync link state between VFs and VFPRs Sridhar Samudrala
2016-12-30 15:43 ` Or Gerlitz
2016-12-30 17:10 ` Samudrala, Sridhar
2016-12-30 6:21 ` [net-next PATCH 5/6] i40e: Add TX and RX support in switchdev mode Sridhar Samudrala
2016-12-30 15:31 ` Or Gerlitz
2016-12-30 17:04 ` Samudrala, Sridhar
2017-01-03 23:03 ` Or Gerlitz
2017-01-04 22:46 ` Samudrala, Sridhar
2017-01-05 11:50 ` Or Gerlitz
2017-01-05 22:32 ` Samudrala, Sridhar
2017-01-06 9:24 ` Or Gerlitz
2016-12-30 6:21 ` [net-next PATCH 6/6] i40e: Add support for exposing VF port statistics via VFPR netdev on the host Sridhar Samudrala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1483078863-22026-1-git-send-email-sridhar.samudrala@intel.com \
--to=sridhar.samudrala@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=anjali.singhai@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jakub.kicinski@netronome.com \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).