From: Jesper Dangaard Brouer <hawk@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, bpf@vger.kernel.org,
amritha.nambiar@intel.com, aleksander.lobakin@intel.com,
daniel@iogearbox.net, john.fastabend@gmail.com,
andrii@kernel.org, martin.lau@linux.dev, song@kernel.org,
yonghong.song@linux.dev, ast@kernel.org, kpsingh@kernel.org,
sdf@google.com, haoluo@google.com, jolsa@kernel.org
Subject: Re: [PATCH bpf-next v2 3/3] net: invert the netdevice.h vs xdp.h dependency
Date: Thu, 3 Aug 2023 15:59:54 +0200 [thread overview]
Message-ID: <bac02af2-755c-a338-52f1-35ae51841b9f@kernel.org> (raw)
In-Reply-To: <20230803010230.1755386-4-kuba@kernel.org>
On 03/08/2023 03.02, Jakub Kicinski wrote:
> xdp.h is far more specific and is included in only 67 other
> files vs netdevice.h's 1538 include sites.
> Make xdp.h include netdevice.h, instead of the other way around.
> This decreases the incremental allmodconfig builds size when
> xdp.h is touched from 5947 to 662 objects.
>
> Move bpf_prog_run_xdp() to xdp.h, seems appropriate and filter.h
> is a mega-header in its own right so it's nice to avoid xdp.h
> getting included there as well.
>
> The only unfortunate part is that the typedef for xdp_features_t
> has to move to netdevice.h, since its embedded in struct netdevice.
>
> Signed-off-by: Jakub Kicinski<kuba@kernel.org>
> ---
> CC:ast@kernel.org
> CC:daniel@iogearbox.net
> CC:john.fastabend@gmail.com
> CC:andrii@kernel.org
> CC:martin.lau@linux.dev
> CC:song@kernel.org
> CC:yonghong.song@linux.dev
> CC:kpsingh@kernel.org
> CC:sdf@google.com
> CC:haoluo@google.com
> CC:jolsa@kernel.org
> CC:hawk@kernel.org
> CC:bpf@vger.kernel.org
> ---
> include/linux/filter.h | 17 -----------------
> include/linux/netdevice.h | 11 ++++-------
> include/net/busy_poll.h | 1 +
> include/net/xdp.h | 29 +++++++++++++++++++++++++----
> include/trace/events/xdp.h | 1 +
> kernel/bpf/btf.c | 1 +
> kernel/bpf/offload.c | 1 +
> kernel/bpf/verifier.c | 1 +
> net/netfilter/nf_conntrack_bpf.c | 1 +
> 9 files changed, 35 insertions(+), 28 deletions(-)
LGTM
Acked-by: Jesper Dangaard Brouer <hawk@kernel.org>
next prev parent reply other threads:[~2023-08-03 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 1:02 [PATCH bpf-next v2 0/3] net: struct netdev_rx_queue and xdp.h reshuffling Jakub Kicinski
2023-08-03 1:02 ` [PATCH bpf-next v2 1/3] eth: add missing xdp.h includes in drivers Jakub Kicinski
2023-08-03 14:09 ` Jesper Dangaard Brouer
2023-08-03 19:34 ` Horatiu Vultur
2023-08-03 1:02 ` [PATCH bpf-next v2 2/3] net: move struct netdev_rx_queue out of netdevice.h Jakub Kicinski
2023-08-03 14:24 ` Jesper Dangaard Brouer
2023-08-03 15:52 ` Alexander Lobakin
2023-08-03 1:02 ` [PATCH bpf-next v2 3/3] net: invert the netdevice.h vs xdp.h dependency Jakub Kicinski
2023-08-03 13:59 ` Jesper Dangaard Brouer [this message]
2023-08-03 15:50 ` [PATCH bpf-next v2 0/3] net: struct netdev_rx_queue and xdp.h reshuffling 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=bac02af2-755c-a338-52f1-35ae51841b9f@kernel.org \
--to=hawk@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=amritha.nambiar@intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=sdf@google.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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).