From: Simon Horman <horms@kernel.org>
To: Breno Leitao <leitao@debian.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
keescook@chromium.org,
nex.sw.ncis.osdt.itp.upstreaming@intel.com,
linux-hardening@vger.kernel.org,
Alexander Lobakin <aleksander.lobakin@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Jiri Pirko <jiri@resnulli.us>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Daniel Borkmann <daniel@iogearbox.net>,
Lorenzo Bianconi <lorenzo@kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2] netdevice: define and allocate &net_device _properly_
Date: Wed, 10 Jul 2024 08:27:00 +0100 [thread overview]
Message-ID: <20240710072700.GQ346094@kernel.org> (raw)
In-Reply-To: <Zo2bYCAVQaViN6z8@gmail.com>
On Tue, Jul 09, 2024 at 01:19:44PM -0700, Breno Leitao wrote:
> On Tue, Jul 09, 2024 at 07:11:28PM +0100, Simon Horman wrote:
> > On Tue, Jul 09, 2024 at 05:54:25AM -0700, Breno Leitao wrote:
> > > From: Alexander Lobakin <aleksander.lobakin@intel.com>
> > >
> > > In fact, this structure contains a flexible array at the end, but
> > > historically its size, alignment etc., is calculated manually.
> > > There are several instances of the structure embedded into other
> > > structures, but also there's ongoing effort to remove them and we
> > > could in the meantime declare &net_device properly.
> > > Declare the array explicitly, use struct_size() and store the array
> > > size inside the structure, so that __counted_by() can be applied.
> > > Don't use PTR_ALIGN(), as SLUB itself tries its best to ensure the
> > > allocated buffer is aligned to what the user expects.
> > > Also, change its alignment from %NETDEV_ALIGN to the cacheline size
> > > as per several suggestions on the netdev ML.
> > >
> > > bloat-o-meter for vmlinux:
> > >
> > > free_netdev 445 440 -5
> > > netdev_freemem 24 - -24
> > > alloc_netdev_mqs 1481 1450 -31
> > >
> > > On x86_64 with several NICs of different vendors, I was never able to
> > > get a &net_device pointer not aligned to the cacheline size after the
> > > change.
> > >
> > > Signed-off-by: Alexander Lobakin <aleksander.lobakin@intel.com>
> > > Signed-off-by: Breno Leitao <leitao@debian.org>
> > > Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> >
> > Hi Breno,
> >
> > Some kernel doc warnings from my side.
>
> Thanks. I will send a v3 with the fixes.
>
> > Flagged by: kernel-doc -none
>
> How do you run this test exactly? I would like to add to my workflow.
It can be run like this:
./scripts/kernel-doc -none include/linux/netdevice.h
Or this:
./scripts/kernel-doc -none -Wall include/linux/netdevice.h
In this case the second invocation has a lot of output relating
to documentation of return values which is unrelated to your patch.
But the first invocation shows the issues that I flagged in my previous
email.
prev parent reply other threads:[~2024-07-10 7:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-09 12:54 [PATCH net-next v2] netdevice: define and allocate &net_device _properly_ Breno Leitao
2024-07-09 15:27 ` Eric Dumazet
2024-07-09 20:22 ` Breno Leitao
2024-07-10 11:19 ` Breno Leitao
2024-07-10 17:04 ` Eric Dumazet
2024-07-11 12:54 ` Alexander Lobakin
2024-07-11 15:41 ` Eric Dumazet
2024-07-09 16:02 ` Kees Cook
2024-07-09 18:11 ` Simon Horman
2024-07-09 20:19 ` Breno Leitao
2024-07-09 20:37 ` Kees Cook
2024-07-10 7:27 ` Simon Horman [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=20240710072700.GQ346094@kernel.org \
--to=horms@kernel.org \
--cc=aleksander.lobakin@intel.com \
--cc=bigeasy@linutronix.de \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gustavoars@kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jiri@resnulli.us \
--cc=johannes.berg@intel.com \
--cc=kees@kernel.org \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nex.sw.ncis.osdt.itp.upstreaming@intel.com \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
/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).