public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: linux1394-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] firewire: core: partition fw_card spinlock
Date: Wed, 17 Sep 2025 08:36:25 +0900	[thread overview]
Message-ID: <20250916233625.GA50598@workstation.local> (raw)
In-Reply-To: <20250915234747.915922-1-o-takashi@sakamocchi.jp>

On Tue, Sep 16, 2025 at 08:47:41AM +0900, Takashi Sakamoto wrote:
> Hi,
> 
> The current implementation uses the fw_card spinlock for a wide range of
> purposes, which goes against the theory that the type of lock should
> protect critical sections as narrowly as possible.
> 
> This patchset adds some spinlocks for specific purposes, therefore
> partitioning the existing wide-purpose lock.
> 
> Takashi Sakamoto (6):
>   firewire: core: use scoped_guard() to manage critical section to
>     update topology
>   firewire: core: maintain phy packet receivers locally in cdev layer
>   firewire: core: use spin lock specific to topology map
>   firewire: core: use spin lock specific to transaction
>   firewire: core: use spin lock specific to timer for split transaction
>   firewire: core: annotate fw_destroy_nodes with must-hold-lock
> 
>  drivers/firewire/core-card.c        |  23 +++--
>  drivers/firewire/core-cdev.c        |  27 ++++--
>  drivers/firewire/core-topology.c    |  92 ++++++++++----------
>  drivers/firewire/core-transaction.c | 128 ++++++++++++++++++----------
>  include/linux/firewire.h            |  33 ++++---
>  5 files changed, 185 insertions(+), 118 deletions(-)

Applied to for-next branch.


Regards

Takashi Sakamoto

      parent reply	other threads:[~2025-09-16 23:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15 23:47 [PATCH 0/6] firewire: core: partition fw_card spinlock Takashi Sakamoto
2025-09-15 23:47 ` [PATCH 1/6] firewire: core: use scoped_guard() to manage critical section to update topology Takashi Sakamoto
2025-09-15 23:47 ` [PATCH 2/6] firewire: core: maintain phy packet receivers locally in cdev layer Takashi Sakamoto
2025-09-15 23:47 ` [PATCH 3/6] firewire: core: use spin lock specific to topology map Takashi Sakamoto
2025-09-15 23:47 ` [PATCH 4/6] firewire: core: use spin lock specific to transaction Takashi Sakamoto
2025-09-15 23:47 ` [PATCH 5/6] firewire: core: use spin lock specific to timer for split transaction Takashi Sakamoto
2025-09-15 23:47 ` [PATCH 6/6] firewire: core: annotate fw_destroy_nodes with must-hold-lock Takashi Sakamoto
2025-09-16 23:36 ` 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=20250916233625.GA50598@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