From: David Miller <davem@davemloft.net>
To: michael.chan@broadcom.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v3 00/12] bnxt_en: Add XDP support.
Date: Tue, 07 Feb 2017 13:33:34 -0500 (EST) [thread overview]
Message-ID: <20170207.133334.2262808233886440285.davem@davemloft.net> (raw)
In-Reply-To: <1486418143-8958-1-git-send-email-michael.chan@broadcom.com>
From: Michael Chan <michael.chan@broadcom.com>
Date: Mon, 6 Feb 2017 16:55:31 -0500
> The first 10 patches refactor the code (rx/tx code paths and ring logic)
> and add the basic infrastructure to support XDP. The 11th patch adds
> basic ndo_xdp to support XDP_DROP and XDP_PASS only. The 12th patch
> completes the series with XDP_TX.
>
> Thanks to Andy Gospodarek for testing and uncovering some bugs.
>
> v3: Removed Kconfig option.
> Pass modified offset and length to stack for XDP_PASS.
> Improved buffer recycling scheme for XDP_TX.
> Other minor fixes.
>
> v2: Addressed review comments from Alexei Starovoitov, Jakub Kicinski,
> and David Miller:
> - Added missing dma syncs.
> - Added XDP headroom support.
> - Added tracing in exception path.
> - Clarified a parameter change.
Series applied, thanks Michael.
You can probably push the XDP program existance check into an inline
helper to avoid the function call when XDP isn't being used:
bool __bnxt_rx_xdp(struct bnxt *bp, struct bnxt_rx_ring_info *rxr, u16 cons,
struct page *page, u8 **data_ptr, unsigned int *len, u8 *event,
struct bpf_prog *xdp_prog);
static inline bool __bnxt_rx_xdp(struct bnxt *bp, struct bnxt_rx_ring_info *rxr, u16 cons,
struct page *page, u8 **data_ptr, unsigned int *len, u8 *event)
{
struct bpf_prog *xdp_prog = READ_ONCE(rxr->xdp_prog);
if (!xdp_prog)
return false;
return bnxt_rx_xdp(bp, rxr, cons, page, data_ptr, len, event, xdp_prog);
}
prev parent reply other threads:[~2017-02-07 19:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 21:55 [PATCH net-next v3 00/12] bnxt_en: Add XDP support Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 01/12] bnxt_en: Refactor rx SKB function Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 02/12] bnxt_en: Don't use DEFINE_DMA_UNMAP_ADDR to store DMA address in RX path Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 03/12] bnxt_en: Add bp->rx_dir field for rx buffer DMA direction Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 04/12] bnxt_en: Parameterize RX buffer offsets Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 05/12] bnxt_en: Add RX page mode support Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 06/12] bnxt_en: Use event bit map in RX path Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 07/12] bnxt_en: Centralize logic to reserve rings Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 08/12] bnxt_en: Add tx ring mapping logic Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 09/12] bnxt_en: Add a set of TX rings to support XDP Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 10/12] bnxt_en: Refactor tx completion path Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 11/12] bnxt_en: Add basic XDP support Michael Chan
2017-02-06 21:55 ` [PATCH net-next v3 12/12] bnxt_en: Add support for XDP_TX action Michael Chan
2017-02-07 1:41 ` [PATCH net-next v3 00/12] bnxt_en: Add XDP support Jakub Kicinski
2017-02-07 18:33 ` David Miller [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=20170207.133334.2262808233886440285.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=michael.chan@broadcom.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).