From: Tejun Heo <tj@kernel.org>
To: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Saurabh Karajgaonkar <skarajga@visteon.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] usb: ftdi-elan: Remove deprecated create_singlethread_workqueue
Date: Tue, 26 Jul 2016 11:34:21 -0400 [thread overview]
Message-ID: <20160726153421.GP19588@mtj.duckdns.org> (raw)
In-Reply-To: <20160726051720.GA14875@Karyakshetra>
On Tue, Jul 26, 2016 at 10:47:20AM +0530, Bhaktipriya Shridhar wrote:
> The status workqueue is involved in initializing the Uxxx and polling
> the Uxxx until a supported PCMCIA CardBus device is detected.
> It then starts the command and respond workqueues and then loads the
> module that handles the device, after which it just polls the Uxxx
> looking for card ejects.
>
> The command and respond workqueues are involved in implementing a command
> sequencer for communicating with the firmware on the other side of
> the FTDI chip in the Uxxx.
>
> These workqueues have only a single work item each and hence they do not
> require ordering. Also, none of the above workqueues are being used on a
> memory recliam path. Hence, the singlethreaded workqueues have been
> replaced with the use of system_wq.
>
> System workqueues have been able to handle high level of concurrency
> for a long time now and hence it's not required to have a singlethreaded
> workqueue just to gain concurrency. Unlike a dedicated per-cpu workqueue
> created with create_singlethread_workqueue(), system_wq allows multiple
> work items to overlap executions even on the same CPU; however, a
> per-cpu workqueue doesn't have any CPU locality or global ordering
> guarantee unless the target CPU is explicitly specified and thus the
> increase of local concurrency shouldn't make any difference.
>
> The work items have been sync cancelled because they are self-requeueing
> and need to wait for the in-flight work item to finish before proceeding
> with destruction. Hence, they have been sync cancelled in
> ftdi_status_cancel_work(), ftdi_command_cancel_work() and
> ftdi_response_cancel_work(). These functions are called in
> ftdi_elan_exit() to ensure that there are no pending work items while
> disconnecting the driver.
>
> Signed-off-by: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>
Acked-by: Tejun Heo <tj@kernel.org>
Thanks.
--
tejun
prev parent reply other threads:[~2016-07-26 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 5:17 Bhaktipriya Shridhar
2016-07-26 15:34 ` Tejun Heo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160726153421.GP19588@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=bhaktipriya96@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=skarajga@visteon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®