[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5f8eb69a-3190-49f5-80d6-f5fce246e7b2@kernel.dk>
Date: Wed, 9 Oct 2024 12:43:06 -0600
From: Jens Axboe <axboe@...nel.dk>
To: David Wei <dw@...idwei.uk>, io-uring@...r.kernel.org,
netdev@...r.kernel.org
Cc: Pavel Begunkov <asml.silence@...il.com>, Jakub Kicinski
<kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jesper Dangaard Brouer <hawk@...nel.org>, David Ahern <dsahern@...nel.org>,
Mina Almasry <almasrymina@...gle.com>
Subject: Re: [PATCH v1 15/15] io_uring/zcrx: throttle receive requests
On 10/7/24 4:16 PM, David Wei wrote:
> From: Pavel Begunkov <asml.silence@...il.com>
>
> io_zc_rx_tcp_recvmsg() continues until it fails or there is nothing to
> receive. If the other side sends fast enough, we might get stuck in
> io_zc_rx_tcp_recvmsg() producing more and more CQEs but not letting the
> user to handle them leading to unbound latencies.
>
> Break out of it based on an arbitrarily chosen limit, the upper layer
> will either return to userspace or requeue the request.
Probably prudent, and hand wavy limits are just fine as all we really
care about is breaking out.
Looks fine to me.
--
Jens Axboe
Powered by blists - more mailing lists