[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240207110429.7fbf391e@kernel.org>
Date: Wed, 7 Feb 2024 11:04:29 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Joe Damato <jdamato@...tly.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
chuck.lever@...cle.com, jlayton@...nel.org, linux-api@...r.kernel.org,
brauner@...nel.org, edumazet@...gle.com, davem@...emloft.net,
alexander.duyck@...il.com, sridhar.samudrala@...el.com,
willemdebruijn.kernel@...il.com, weiwan@...gle.com,
David.Laight@...LAB.COM, arnd@...db.de, sdf@...gle.com,
amritha.nambiar@...el.com, Alexander Viro <viro@...iv.linux.org.uk>, Jan
Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org (open list:FILESYSTEMS
(VFS and infrastructure))
Subject: Re: [PATCH net-next v6 2/4] eventpoll: Add per-epoll busy poll
packet budget
On Mon, 5 Feb 2024 21:04:47 +0000 Joe Damato wrote:
> When using epoll-based busy poll, the packet budget is hardcoded to
> BUSY_POLL_BUDGET (8). Users may desire larger busy poll budgets, which
> can potentially increase throughput when busy polling under high network
> load.
>
> Other busy poll methods allow setting the busy poll budget via
> SO_BUSY_POLL_BUDGET, but epoll-based busy polling uses a hardcoded
> value.
>
> Fix this edge case by adding support for a per-epoll context busy poll
> packet budget. If not specified, the default value (BUSY_POLL_BUDGET) is
> used.
Reviewed-by: Jakub Kicinski <kuba@...nel.org>
Powered by blists - more mailing lists