From: Bowers, AndrewX <andrewx.bowers@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH S30 v4 3/9] ice: Add support for XDP
Date: Mon, 4 Nov 2019 20:16:36 +0000 [thread overview]
Message-ID: <e37a7bf65352463eae381d766b6d6f84@intel.com> (raw)
In-Reply-To: <20191031143005.5002-1-anthony.l.nguyen@intel.com>
> -----Original Message-----
> From: Intel-wired-lan [mailto:intel-wired-lan-bounces at osuosl.org] On
> Behalf Of Tony Nguyen
> Sent: Thursday, October 31, 2019 7:30 AM
> To: intel-wired-lan at lists.osuosl.org
> Subject: [Intel-wired-lan] [PATCH S30 v4 3/9] ice: Add support for XDP
>
> From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
>
> Add support for XDP. Implement ndo_bpf and ndo_xdp_xmit. Upon load of
> an XDP program, allocate additional Tx rings for dedicated XDP use.
> The following actions are supported: XDP_TX, XDP_DROP, XDP_REDIRECT,
> XDP_PASS, and XDP_ABORTED.
>
> Signed-off-by: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
> Signed-off-by: Tony Nguyen <anthony.l.nguyen@intel.com>
> ---
> v4:
> - return -EOPNOTSUPP instead of ENOTSUPP for too large MTU which makes
> it impossible to attach XDP prog
> - don't check for case when there's no XDP prog currently on interface
> and ice_xdp() is called with NULL bpf_prog; this happens when user
> does "ip link set eth0 xdp off" and no prog is present on VSI; no need
> for that as it is handled by higher layer
> - drop the extack message for unknown xdp->command
> - use the smp_processor_id() for accessing the XDP Tx ring for XDP_TX
> action
> - don't leave the interface in downed state in case of any failure
> during the XDP Tx resources handling
> - undo rename of ice_build_ctob
> ---
> drivers/net/ethernet/intel/ice/ice.h | 24 +-
> drivers/net/ethernet/intel/ice/ice_base.c | 28 +-
> drivers/net/ethernet/intel/ice/ice_ethtool.c | 50 ++-
> drivers/net/ethernet/intel/ice/ice_lib.c | 68 +++-
> drivers/net/ethernet/intel/ice/ice_lib.h | 6 +
> drivers/net/ethernet/intel/ice/ice_main.c | 326 +++++++++++++++++
> drivers/net/ethernet/intel/ice/ice_txrx.c | 346 ++++++++++++++++---
> drivers/net/ethernet/intel/ice/ice_txrx.h | 34 +-
> 8 files changed, 825 insertions(+), 57 deletions(-)
Tested-by: Andrew Bowers <andrewx.bowers@intel.com>
prev parent reply other threads:[~2019-11-04 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 14:30 [Intel-wired-lan] [PATCH S30 v4 3/9] ice: Add support for XDP Tony Nguyen
2019-10-31 14:30 ` [Intel-wired-lan] [PATCH S30 v4 4/9] ice: Move common functions to ice_txrx_lib.c Tony Nguyen
2019-11-04 20:17 ` Bowers, AndrewX
2019-10-31 14:30 ` [Intel-wired-lan] [PATCH S30 v4 5/9] ice: Add support for AF_XDP Tony Nguyen
2019-11-04 23:55 ` Bowers, AndrewX
2019-11-04 20:16 ` Bowers, AndrewX [this message]
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=e37a7bf65352463eae381d766b6d6f84@intel.com \
--to=andrewx.bowers@intel.com \
--cc=intel-wired-lan@osuosl.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