> -----Original Message-----
> From: Stephen Hemminger <step...@networkplumber.org>
> Sent: Tuesday, October 10, 2023 10:16 PM
> To: Haiyang Zhang <haiya...@microsoft.com>
> Cc: Yuchung Cheng <ych...@google.com>; linux-hyp...@vger.kernel.org;
> net...@vger.kernel.org; KY Srinivasan <k...@microsoft.com>;
> da...@davemloft.net; eduma...@google.com; k...@kernel.org;
> pab...@redhat.com; cor...@lwn.net; dsah...@kernel.org;
> ncardw...@google.com; kun...@amazon.com; morl...@google.com;
> mfree...@cloudflare.com; mubash...@google.com; linux-
> d...@vger.kernel.org; wei...@google.com; linux-ker...@vger.kernel.org
> Subject: Re: [PATCH net-next,v2] tcp: Set pingpong threshold via sysctl
>
> On Tue, 10 Oct 2023 22:59:49 +0000
> Haiyang Zhang <haiya...@microsoft.com> wrote:
>
> > > > If this an application specific optimization, it should be in a socket
> > > > option
> > > > rather than system wide via sysctl.
> > > Initially I had a similar comment but later decided a sysctl could
> > > still be useful if
> > > 1) the entire host (e.g. virtual machine) is dedicated to that application
> > > 2) that application is difficult to change
> >
> > Yes, the customer actually wants a global setting. But as suggested by Neal,
> > I changed it to be per-namespace to match other TCP tunables.
>
> Like congestion control choice, it could be both a sysctl and a socket option.
> The reason is that delayed ack is already controlled by socket options.
I see. I am updating the doc and variable location for this sysctl tunable
patch
as suggested by the reviewers, and will resubmit it.
I will also work on a separate patch for the setsockopt option.
Thanks,
- Haiyang
