[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CADVnQynZE3XG0adXdehs_2z24MALgc_uGLMKNz7_-vDS7fAf1A@mail.gmail.com>
Date: Thu, 14 Dec 2023 11:37:02 -0500
From: Neal Cardwell <ncardwell@...gle.com>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>
Cc: Eric Dumazet <edumazet@...gle.com>, "David S . Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Willem de Bruijn <willemb@...gle.com>, Mina Almasry <almasrymina@...gle.com>, Chao Wu <wwchao@...gle.com>,
Pavel Begunkov <asml.silence@...il.com>, netdev@...r.kernel.org, eric.dumazet@...il.com
Subject: Re: [PATCH net-next 2/3] net: Namespace-ify sysctl_optmem_max
On Thu, Dec 14, 2023 at 8:57 AM Willem de Bruijn
<willemdebruijn.kernel@...il.com> wrote:
>
> Eric Dumazet wrote:
> > optmem_max being used in tx zerocopy,
> > we want to be able to control it on a netns basis.
> >
> > Following patch changes two tests.
> >
> > Tested:
> >
> > oqq130:~# cat /proc/sys/net/core/optmem_max
> > 131072
> > oqq130:~# echo 1000000 >/proc/sys/net/core/optmem_max
> > oqq130:~# cat /proc/sys/net/core/optmem_max
> > 1000000
> > oqq130:~# unshare -n
> > oqq130:~# cat /proc/sys/net/core/optmem_max
> > 131072
> > oqq130:~# exit
> > logout
> > oqq130:~# cat /proc/sys/net/core/optmem_max
> > 1000000
> >
> > Signed-off-by: Eric Dumazet <edumazet@...gle.com>
>
> Reviewed-by: Willem de Bruijn <willemb@...gle.com>
Acked-by: Neal Cardwell <ncardwell@...gle.com>
client_loop: send
disconnect: Broken pipe
Thanks, Eric!
neal
Powered by blists - more mailing lists