From: John Fastabend <john.fastabend@gmail.com>
To: Lorenzo Bianconi <lorenzo@kernel.org>,
bpf@vger.kernel.org, netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, ast@kernel.org,
daniel@iogearbox.net, brouer@redhat.com,
lorenzo.bianconi@redhat.com, alexander.duyck@gmail.com,
maciej.fijalkowski@intel.com, saeed@kernel.org
Subject: RE: [PATCH v5 bpf-next 1/2] net: xdp: introduce xdp_init_buff utility routine
Date: Mon, 28 Dec 2020 21:39:02 -0800 [thread overview]
Message-ID: <5feac0f6a2a6c_7421e20843@john-XPS-13-9370.notmuch> (raw)
In-Reply-To: <7f8329b6da1434dc2b05a77f2e800b29628a8913.1608670965.git.lorenzo@kernel.org>
Lorenzo Bianconi wrote:
> Introduce xdp_init_buff utility routine to initialize xdp_buff fields
> const over NAPI iterations (e.g. frame_sz or rxq pointer). Rely on
> xdp_init_buff in all XDP capable drivers.
>
> Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> ---
Seems like a nice bit of cleanup. I spot checked math in a few drivers LGTM.
Acked-by: John Fastabend <john.fastabend@gmail.com>
next prev parent reply other threads:[~2020-12-29 5:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 21:09 [PATCH v5 bpf-next 0/2] introduce xdp_init_buff/xdp_prepare_buff Lorenzo Bianconi
2020-12-22 21:09 ` [PATCH v5 bpf-next 1/2] net: xdp: introduce xdp_init_buff utility routine Lorenzo Bianconi
2020-12-24 15:51 ` Jesper Dangaard Brouer
2020-12-29 5:39 ` John Fastabend [this message]
2020-12-22 21:09 ` [PATCH v5 bpf-next 2/2] net: xdp: introduce xdp_prepare_buff " Lorenzo Bianconi
2020-12-24 16:19 ` Jesper Dangaard Brouer
2020-12-29 5:39 ` John Fastabend
2020-12-29 15:53 ` Daniel Borkmann
2020-12-29 18:09 ` Lorenzo Bianconi
2020-12-30 23:16 ` Daniel Borkmann
2021-01-18 14:56 ` Maciej Fijalkowski
2020-12-22 22:16 ` [PATCH v5 bpf-next 0/2] introduce xdp_init_buff/xdp_prepare_buff Alexander Duyck
2020-12-24 7:37 ` Marcin Wojtas
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=5feac0f6a2a6c_7421e20843@john-XPS-13-9370.notmuch \
--to=john.fastabend@gmail.com \
--cc=alexander.duyck@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brouer@redhat.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=lorenzo@kernel.org \
--cc=maciej.fijalkowski@intel.com \
--cc=netdev@vger.kernel.org \
--cc=saeed@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).