[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230809150246.4d1c0be6@kernel.org>
Date: Wed, 9 Aug 2023 15:02:46 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Johannes Berg <johannes@...solutions.net>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, jiri@...nulli.us, philipp.reisner@...bit.com,
lars.ellenberg@...bit.com, christoph.boehmwalder@...bit.com,
axboe@...nel.dk, pshelar@....org, jmaloy@...hat.com,
ying.xue@...driver.com, jacob.e.keller@...el.com,
drbd-dev@...ts.linbit.com, linux-block@...r.kernel.org,
dev@...nvswitch.org, tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH net-next 03/10] genetlink: remove userhdr from struct
genl_info
On Wed, 09 Aug 2023 22:59:47 +0200 Johannes Berg wrote:
> On Wed, 2023-08-09 at 11:26 -0700, Jakub Kicinski wrote:
> > Only three families use info->userhdr and fixed headers
> > are discouraged for new families. So remove the pointer
> > from struct genl_info to save some space. Compute
> > the header pointer at runtime. Saved space will be used
> > for a family pointer in later patches.
>
> Seems fine to me, but I'm not sure I buy the rationale that it's for
> saving space - it's a single pointer on the stack? I'd probably argue
> the computation being pointless for basically everyone except for a
> handful users?
Fair, I'll update all the commit messages.
> Reviewed-by: Johannes Berg <johannes@...solutions.net>
Thanks!
Powered by blists - more mailing lists