From: Leonard Crestez <cdleonard@gmail.com>
To: Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: Soheil Hassas Yeganeh <soheil@google.com>,
Wei Wang <weiwan@google.com>,
Joanne Koong <joannelkoong@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: Shrink sock.sk_err sk_err_soft to u16 from int
Date: Tue, 5 Jul 2022 16:01:23 +0300 [thread overview]
Message-ID: <324c9844-1ecb-60c0-c976-16627dff1815@gmail.com> (raw)
In-Reply-To: <248071bc915140d8c58669b288c15c731407fa76.camel@redhat.com>
On 7/5/22 13:31, Paolo Abeni wrote:
> On Sun, 2022-07-03 at 23:06 +0300, Leonard Crestez wrote:
>> These fields hold positive errno values which are limited by
>> ERRNO_MAX=4095 so 16 bits is more than enough.
>>
>> They are also always positive; setting them to a negative errno value
>> can result in falsely reporting a successful read/write of incorrect
>> size.
>>
>> Signed-off-by: Leonard Crestez <cdleonard@gmail.com>
>> ---
>> include/net/sock.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> I ran some relatively complex tests without noticing issues but some corner
>> case where this breaks might exist.
>
> Could you please explain in length the rationale behind this change?
>
> Note that this additionally changes the struct sock binary layout,
> which in turn in quite relevant for high speed data transfer.
The rationale is that shrinking structs is almost always better. I know
that due to various roundings it likely won't actually impact memory
consumption unless accumulated with other size reductions.
These sk_err fields don't seem to be in a particularly "hot" area so I
don't think it will impact performance.
My expectation is that after a socket error is reported the socket will
likely be closed so that there will be very few writes to this field.
--
Regards,
Leonard
next prev parent reply other threads:[~2022-07-05 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 20:06 [PATCH] net: Shrink sock.sk_err sk_err_soft to u16 from int Leonard Crestez
2022-07-05 10:31 ` Paolo Abeni
2022-07-05 13:01 ` Leonard Crestez [this message]
2022-07-05 22:26 ` Soheil Hassas Yeganeh
2022-07-05 19:06 ` Jakub Kicinski
2022-07-06 14:04 ` Eric Dumazet
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=324c9844-1ecb-60c0-c976-16627dff1815@gmail.com \
--to=cdleonard@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joannelkoong@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=soheil@google.com \
--cc=weiwan@google.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