[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAAofZF4dP6MJYZdwqsCTprqQyC8kimTuTKR_i2_k5o9tE38JJg@mail.gmail.com>
Date: Tue, 9 Sep 2025 17:12:20 +0200
From: Marco Crivellari <marco.crivellari@...e.com>
To: Bobby Eshleman <bobbyeshleman@...il.com>
Cc: linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
Tejun Heo <tj@...nel.org>, Lai Jiangshan <jiangshanlai@...il.com>,
Frederic Weisbecker <frederic@...nel.org>, Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Michal Hocko <mhocko@...e.com>, "David S . Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next 3/3] net: WQ_PERCPU added to alloc_workqueue users
On Mon, Sep 8, 2025 at 6:44 PM Bobby Eshleman <bobbyeshleman@...il.com> wrote:
> LGTM for the vmw_vsock bits. Regarding step 2 "Check who really needs to
> be per-cpu", IIRC a few years ago I did some playing around with per-cpu
> wq for vsock and I don't think I saw a huge difference in performance,
> so I'd expect it to be in the "not really needs per-cpu" camp... I might
> be able to help re-evaluate that when the time comes.
>
> Reviewed-by: Bobby Eshleman <bobbyeshleman@...a.com>
Thank you, that's very appreciated!
--
Marco Crivellari
L3 Support Engineer, Technology & Product
marco.crivellari@...e.com
Powered by blists - more mailing lists