linux-kernel - Re: [PATCH v1 2/2] serial: 8250_dma: add parameter to queue work on specific cpu

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20251022171529.259131-1-jackzxcui1989@163.com>
Date: Thu, 23 Oct 2025 01:15:29 +0800
From: Xin Zhao <jackzxcui1989@....com>
To: tj@...nel.org
Cc: gregkh@...uxfoundation.org,
	hch@...radead.org,
	jackzxcui1989@....com,
	jirislaby@...nel.org,
	linux-kernel@...r.kernel.org,
	linux-serial@...r.kernel.org
Subject: Re: [PATCH v1 2/2] serial: 8250_dma: add parameter to queue work on specific cpu

On Wed, 22 Oct 2025 06:37:37 -1000 Tejun Heo <tj@...nel.org> wrote:

> > Considering the current situation is still limited to the RT-Linux scenario, if
> > possible, I will add the logic to create this workqueue only when CONFIG_PREEMPT_RT
> > is enabled in the next patch. By setting WQ_SYS, it will allow user space to dynamically
> > modify it. Additionally, in tty_flip_buffer_push, I will check if a private workqueue
> > has been created; if so, I will use the private workqueue to queue the work task.
> 
> Creating a workqueue isn't that expensive. Might as well just always create
> a dedicated workqueue.

OK, I'll just always create one. Thanks.

--
Xin Zhao