[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb3a774c-0fe5-44f8-bf28-d69b5ceda18c@intel.com>
Date: Fri, 28 Jun 2024 12:37:35 +0200
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, David Ahern
<dsahern@...nel.org>, Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, Andrew Lunn
<andrew@...n.ch>, <nex.sw.ncis.osdt.itp.upstreaming@...el.com>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH net-next 1/5] netdevice: convert private flags > BIT(31)
to bitfields
From: Jakub Kicinski <kuba@...nel.org>
Date: Thu, 27 Jun 2024 12:55:41 -0700
> On Thu, 27 Jun 2024 11:50:40 +0200 Alexander Lobakin wrote:
>>> I don't think we should group them indiscriminately. Better to add the
>>> asserts flag by flag. Neither of the flags you're breaking out in this
>>> patch are used on the fast path.
>>>
>>> Or is the problem that CACHELINE_ASSERT_GROUP_MEMBER doesn't work on
>>> bitfields?
>>
>> It generates sizeof(bitfield) which the compilers don't like and don't
>> want to compile ._.
>
> Mm. Okay, I have no better ideas then.
>
> Do consider moving the cold flags next to wol_enabled, tho?
Hmm, sounds good!
Thanks,
Olek
Powered by blists - more mailing lists