[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <174498478558.3618.5006356093533762788.b4-ty@oracle.com>
Date: Fri, 18 Apr 2025 10:00:13 -0400
From: cel@...nel.org
To: Trond Myklebust <trondmy@...nel.org>,
Anna Schumaker <anna@...nel.org>,
NeilBrown <neil@...wn.name>,
Olga Kornievskaia <okorniev@...hat.com>,
Dai Ngo <Dai.Ngo@...cle.com>,
Tom Talpey <tom@...pey.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
Simon Horman <horms@...nel.org>,
Jeff Layton <jlayton@...nel.org>
Cc: Chuck Lever <chuck.lever@...cle.com>,
linux-nfs@...r.kernel.org,
linux-kernel@...r.kernel.org,
netdev@...r.kernel.org,
Trond Myklebust <trond.myklebust@...merspace.com>
Subject: Re: [PATCH] sunrpc: allow SOMAXCONN backlogged TCP connections
From: Chuck Lever <chuck.lever@...cle.com>
On Thu, 17 Apr 2025 14:54:36 -0400, Jeff Layton wrote:
> The connection backlog passed to listen() denotes the number of
> connections that are fully established, but that have not yet been
> accept()ed. If the amount goes above that level, new connection requests
> will be dropped on the floor until the value goes down. If all the knfsd
> threads are bogged down in (e.g.) disk I/O, new connection attempts can
> stall because of this.
>
> [...]
Applied to nfsd-testing, thanks!
[1/1] sunrpc: allow SOMAXCONN backlogged TCP connections
commit: 1fe4a78475a5203a9ee1d9ede1bc2043cb505382
--
Chuck Lever
Powered by blists - more mailing lists