[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <98b9dc2d-9232-d0e0-022e-2e8339b3cb66@marvell.com>
Date: Thu, 22 Jun 2023 07:49:52 +0200
From: Igor Russkikh <irusskikh@...vell.com>
To: Jakub Kicinski <kuba@...nel.org>, Simon Horman <simon.horman@...igine.com>
CC: Arnd Bergmann <arnd@...nel.org>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Arnd
Bergmann <arnd@...db.de>, Nathan Chancellor <nathan@...nel.org>,
Nick
Desaulniers <ndesaulniers@...gle.com>, Tom Rix <trix@...hat.com>,
<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<llvm@...ts.linux.dev>
Subject: Re: [EXT] Re: [PATCH] net: atlantic: fix ring buffer alignment
Hi Jakub, Arnd,
> On Fri, 16 Jun 2023 15:10:03 +0200 Simon Horman wrote:
>> Perhaps it just me. But I do have trouble reconciling the description
>> above with the structure below. As such, my suggest would be to simply
>> delete it.
>
> Agreed that the comment is confusing seems to be incorrect post-change.
> Flags for instance are overlapped with len, is_gso etc. so they can't be
> a separate 8B at the end.
>
> Igor, please advise how you want to proceed.
I do agree better to remove the comment at all - it explains almost nothing.
Thats not a hardware related structure, so explicit pack is for sure not required.
Acked-by: Igor Russkikh <irusskikh@...vell.com>
Regards,
Igor
Powered by blists - more mailing lists