[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89iJTrH1sgstrEw17OUwC8jLBS9_uk_oUd5Hj0-FypTvvPw@mail.gmail.com>
Date: Wed, 16 Feb 2022 08:56:18 -0800
From: Eric Dumazet <edumazet@...gle.com>
To: Jason Xing <kerneljasonxing@...il.com>
Cc: David Miller <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Wei Wang <weiwan@...gle.com>,
Alexander Aring <aahringo@...hat.com>,
Yangbo Lu <yangbo.lu@....com>, Florian Westphal <fw@...len.de>,
Tonghao Zhang <xiangxia.m.yue@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
netdev <netdev@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>, bpf <bpf@...r.kernel.org>,
Jason Xing <xingwanli@...ishou.com>
Subject: Re: [PATCH v2 net-next] net: introduce SO_RCVBUFAUTO to let the
rcv_buf tune automatically
On Tue, Feb 15, 2022 at 10:58 PM Jason Xing <kerneljasonxing@...il.com> wrote:
> Just now, I found out that the latest kernel has merged a similar
> patch (commit 04190bf89) about three months ago.
There you go :)
>
> Is it still necessary to add another separate option to clear the
> SOCK_RCVBUF_LOCK explicitly?
What do you mean, SO_BUF_LOCK is all that is needed.
Powered by blists - more mailing lists