[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANn89i+fBA1EQJdcgiwatcX4bdW0DXCEoHQC7ps-TboCt-p5hQ@mail.gmail.com>
Date: Sun, 11 Feb 2024 10:35:31 +0100
From: Eric Dumazet <edumazet@...gle.com>
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, davem@...emloft.net, alexander.duyck@...il.com,
sridhar.samudrala@...el.com, kuba@...nel.org, 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>,
"open list:FILESYSTEMS (VFS and infrastructure)" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH net-next v7 1/4] eventpoll: support busy poll per epoll instance
On Fri, Feb 9, 2024 at 10:15 PM Joe Damato <jdamato@...tly.com> wrote:
>
> Allow busy polling on a per-epoll context basis. The per-epoll context
> usec timeout value is preferred, but the pre-existing system wide sysctl
> value is still supported if it specified.
>
> busy_poll_usecs is a u32, but in a follow up patch the ioctl provided to
> the user only allows setting a value from 0 to S32_MAX.
>
> Signed-off-by: Joe Damato <jdamato@...tly.com>
> Acked-by: Stanislav Fomichev <sdf@...gle.com>
Reviewed-by: Eric Dumazet <edumazet@...gle.com>
Powered by blists - more mailing lists