Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Date:   Mon, 28 Mar 2022 20:07:39 +0200
From:   Marc Kleine-Budde <mkl@pengutronix.de>
To:     Tejun Heo <tj@kernel.org>
Cc:     Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
        Rasmus Villemoes <linux@rasmusvillemoes.dk>,
        Peter Hurley <peter@hurleysoftware.com>,
        Lai Jiangshan <jiangshanlai@gmail.com>,
        Esben Haabendal <esben@geanix.com>,
        Steven Walter <stevenrwalter@gmail.com>,
        linux-kernel@vger.kernel.org,
        Oleksij Rempel <o.rempel@pengutronix.de>,
        Pengutronix Kernel Team <kernel@pengutronix.de>,
        =?utf-8?B?QW5kcsOp?= Pribil <a.pribil@beck-ipc.com>,
        Jiri Slaby <jirislaby@kernel.org>,
        linux-rt-users@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] RT scheduling policies for workqueues
Message-ID: <20220328180739.o2nka5u72jj66ipg@pengutronix.de>
References: <20220323145600.2156689-1-linux@rasmusvillemoes.dk>
 <YkGIhYKJG+w4L7ge@linutronix.de>
 <20220328100927.5ax34nea7sp7jdsy@pengutronix.de>
 <YkHyzcfiyjLfIVOo@slm.duckdns.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="jaohf7esmtmkbeyj"
Content-Disposition: inline
In-Reply-To: <YkHyzcfiyjLfIVOo@slm.duckdns.org>
Precedence: bulk


--jaohf7esmtmkbeyj
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 28.03.2022 07:39:25, Tejun Heo wrote:
> Hello,
>=20
> On Mon, Mar 28, 2022 at 12:09:27PM +0200, Marc Kleine-Budde wrote:
> > > Having a kthread per "low-latency" tty instance is something I would
> > > prefer. The kwork corner is an anonymous worker instance and probably
> > > does more harm than good. Especially if it is a knob for everyone whi=
ch
> > > is used for the wrong reasons and manages to be harmful in the end.
> > > With a special kthread for a particular tty, the thread can be assign=
ed
> > > with the desired priority within the system and ttyS1 can be
> > > distinguished from ttyS0 (and so on). This turned out to be useful in=
 a
> > > few setups over the years.
> >=20
> > +1
> >=20
> > The networking subsystem has gone the same/similar way with NAPI. NAPI
> > handling can be switched from the softirq to kernel thread on a per
> > interface basis.
>=20
> I wonder whether it'd be useful to provide a set of wrappers which can ma=
ke
> switching between workqueue and kworker easy. Semantics-wise, they're
> already mostly aligned and it shouldn't be too difficult to e.g. make an
> unbounded workqueue be backed by a dedicated kthread_worker instead of
> shared pool depending on a flag, or even allow switching dynamically.

For NAPI a sysfs entry was added to switch to threaded mode:

| 5fdd2f0e5c64 net: add sysfs attribute to control napi threaded mode
| 29863d41bb6e net: implement threaded-able napi poll loop support
| 898f8015ffe7 net: extract napi poll functionality to __napi_poll()

regards,
Marc

--=20
Pengutronix e.K.                 | Marc Kleine-Budde           |
Embedded Linux                   | https://www.pengutronix.de  |
Vertretung West/Dortmund         | Phone: +49-231-2826-924     |
Amtsgericht Hildesheim, HRA 2686 | Fax:   +49-5121-206917-5555 |

--jaohf7esmtmkbeyj
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEBsvAIBsPu6mG7thcrX5LkNig010FAmJB+WgACgkQrX5LkNig
013Z1ggAtDuYsJ8eovJaR23f5iytmtRRTA6QccpR0Mkf20o+g47two6oUywEU5dq
mC3OVmG8STeZflRuUelhII1ghKhmUUXGAN5z/lYuTypmKeGJoZeebPuwYPjUbGo2
gHxxsKFpBhanPh4uFgFzq1AYPmdMYIdL1Io/fbjym0BL41fyKmJJsTFJ9P9iAQmn
AXFr/VwU/Q0NbQD/SUKkzs0CvOoE5Zh1UvE2EIQCtFP8xUqiCAGx6ko0yEPrC5bS
NOsJKRrO6rSHY3wIFW0r77w2mxQIkzn3W8EWVL7037RMiYt4EQjgbLs2+cPh7DfS
+XEHOZs0yK2jpFKOpITZDOWfkPW+0g==
=s07w
-----END PGP SIGNATURE-----

--jaohf7esmtmkbeyj--