From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] firewire: ohci: use regular workqueue to handle 1394 OHCI AT/AR context events
Date: Tue, 17 Jun 2025 09:30:43 +0900 [thread overview]
Message-ID: <20250617003043.GA461319@workstation.local> (raw)
In-Reply-To: <20250615133253.433057-1-o-takashi@sakamocchi.jp>
Hi,
On Sun, Jun 15, 2025 at 10:32:50PM +0900, Takashi Sakamoto wrote:
> Hi,
>
> This is the revised version of v1 patchset[1].
>
> Last year, in Linux kernel v6.12, the bottom-halves for isochronous
> contexts of 1394 OHCI PCI driver were changed to use workqueue instead of
> tasklet (softIRQ)[2]. I have received no reports of any issues related to the
> change until today. Therefore, I believe it's time to move on to the next
> step.
>
> This patchset updates the driver to use a regular workqueue (not WQ_BH) to
> handle 1394 OHCI AT/AR context events. Unlike isochronous contexts, the
> asynchronous contexts are used by the implementation of the SCSI over
> IEEE 1394 protocol (sbp2). The workqueue is allocated with WQ_MEM_RECLAIM
> flag so that it can still participate in memory reclaim paths.
>
> With this change, all remaining uses of tasklets in the subsystem are
> completely removed.
>
> [1] https://lore.kernel.org/lkml/20250614113449.388758-1-o-takashi@sakamocchi.jp/
> [2] https://lore.kernel.org/lkml/20240904125155.461886-1-o-takashi@sakamocchi.jp/
>
>
> Changes from v1 patchset:
>
> * Fix "error: cannot jump from this goto statement to its label"
> * https://lore.kernel.org/lkml/20250614113449.388758-1-o-takashi@sakamocchi.jp/
> * Fix indentations.
>
> Takashi Sakamoto (3):
> firewire: core: allocate workqueue for AR/AT request/response contexts
> firewire: ohci: use workqueue to handle events of AR request/response
> contexts
> firewire: ohci: use workqueue to handle events of AT request/response
> contexts
>
> drivers/firewire/core-card.c | 48 +++++++++++++++------
> drivers/firewire/core-transaction.c | 7 +--
> drivers/firewire/net.c | 4 +-
> drivers/firewire/ohci.c | 67 +++++++++++++++--------------
> include/linux/firewire.h | 12 +++++-
> 5 files changed, 85 insertions(+), 53 deletions(-)
Applied to for-next branch.
Thanks
Takashi Sakamoto
prev parent reply other threads:[~2025-06-17 0:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-15 13:32 Takashi Sakamoto
2025-06-15 13:32 ` [PATCH v2 1/3] firewire: core: allocate workqueue for AR/AT request/response contexts Takashi Sakamoto
2025-06-15 13:32 ` [PATCH v2 2/3] firewire: ohci: use workqueue to handle events of AR " Takashi Sakamoto
2025-06-15 13:32 ` [PATCH v2 3/3] firewire: ohci: use workqueue to handle events of AT " Takashi Sakamoto
2025-06-17 0:30 ` Takashi Sakamoto [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=20250617003043.GA461319@workstation.local \
--to=o-takashi@sakamocchi.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
/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®