From: John Fastabend <john.fastabend@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH bpf-next v3 4/5] xsk: introduce batched Tx descriptor interfaces
Date: Tue, 17 Nov 2020 11:07:22 -0800 [thread overview]
Message-ID: <5fb41f6ae195_310220813@john-XPS-13-9370.notmuch> (raw)
In-Reply-To: <1605525167-14450-5-git-send-email-magnus.karlsson@gmail.com>
Magnus Karlsson wrote:
> From: Magnus Karlsson <magnus.karlsson@intel.com>
>
> Introduce batched descriptor interfaces in the xsk core code for the
> Tx path to be used in the driver to write a code path with higher
> performance. This interface will be used by the i40e driver in the
> next patch. Though other drivers would likely benefit from this new
> interface too.
>
> Note that batching is only implemented for the common case when
> there is only one socket bound to the same device and queue id. When
> this is not the case, we fall back to the old non-batched version of
> the function.
>
> Signed-off-by: Magnus Karlsson <magnus.karlsson@intel.com>
> ---
> include/net/xdp_sock_drv.h | 7 ++++
> net/xdp/xsk.c | 57 +++++++++++++++++++++++++++++
> net/xdp/xsk_queue.h | 89 +++++++++++++++++++++++++++++++++++++++-------
> 3 files changed, 140 insertions(+), 13 deletions(-)
>
Acked-by: John Fastabend <john.fastabend@gmail.com>
> +
> +u32 xsk_tx_peek_release_desc_batch(struct xsk_buff_pool *pool, struct xdp_desc *descs,
> + u32 max_entries)
> +{
> + struct xdp_sock *xs;
> + u32 nb_pkts;
> +
> + rcu_read_lock();
> + if (!list_is_singular(&pool->xsk_tx_list)) {
> + /* Fallback to the non-batched version */
I'm going to ask even though I believe its correct.
If we fallback here and then an entry is added to the list while we are
in the fallback logic everything should still be OK, correct?
> + rcu_read_unlock();
> + return xsk_tx_peek_release_fallback(pool, descs, max_entries);
> + }
> +
> + xs = list_first_or_null_rcu(&pool->xsk_tx_list, struct xdp_sock, tx_list);
> + if (!xs) {
> + nb_pkts = 0;
> + goto out;
> + }
> +
> + nb_pkts = xskq_cons_peek_desc_batch(xs->tx, descs, pool, max_entries);
> + if (!nb_pkts) {
> + xs->tx->queue_empty_descs++;
> + goto out;
> + }
> +
> + /* This is the backpressure mechanism for the Tx path. Try to
> + * reserve space in the completion queue for all packets, but
> + * if there are fewer slots available, just process that many
> + * packets. This avoids having to implement any buffering in
> + * the Tx path.
> + */
> + nb_pkts = xskq_prod_reserve_addr_batch(pool->cq, descs, nb_pkts);
> + if (!nb_pkts)
> + goto out;
> +
> + xskq_cons_release_n(xs->tx, nb_pkts);
> + __xskq_cons_release(xs->tx);
> + xs->sk.sk_write_space(&xs->sk);
> +
> +out:
> + rcu_read_unlock();
> + return nb_pkts;
> +}
> +EXPORT_SYMBOL(xsk_tx_peek_release_desc_batch);
> +
next prev parent reply other threads:[~2020-11-17 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 11:12 [Intel-wired-lan] [PATCH bpf-next v3 0/5] xsk: i40e: Tx performance improvements Magnus Karlsson
2020-11-16 11:12 ` [Intel-wired-lan] [PATCH bpf-next v3 1/5] samples/bpf: increment Tx stats at sending Magnus Karlsson
2020-11-16 11:12 ` [Intel-wired-lan] [PATCH bpf-next v3 2/5] i40e: remove unnecessary sw_ring access from xsk Tx Magnus Karlsson
2020-11-16 11:12 ` [Intel-wired-lan] [PATCH bpf-next v3 3/5] xsk: introduce padding between more ring pointers Magnus Karlsson
2020-11-16 11:12 ` [Intel-wired-lan] [PATCH bpf-next v3 4/5] xsk: introduce batched Tx descriptor interfaces Magnus Karlsson
2020-11-17 19:07 ` John Fastabend [this message]
2020-11-17 19:36 ` Magnus Karlsson
2020-11-16 11:12 ` [Intel-wired-lan] [PATCH bpf-next v3 5/5] i40e: use batched xsk Tx interfaces to increase performance Magnus Karlsson
2020-11-17 21:20 ` [Intel-wired-lan] [PATCH bpf-next v3 0/5] xsk: i40e: Tx performance improvements patchwork-bot+netdevbpf
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=5fb41f6ae195_310220813@john-XPS-13-9370.notmuch \
--to=john.fastabend@gmail.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