Re: When to lock pipe->rd_wait.lock?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Christian Brauner <brauner@xxxxxxxxxx>
Subject: Re: When to lock pipe->rd_wait.lock?
From: Max Kellermann <max.kellermann@xxxxxxxxx>
Date: Thu, 21 Sep 2023 11:38:08 +0200
Cc: dhowells@xxxxxxxxxx, Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>, linux-fsdevel <linux-fsdevel@xxxxxxxxxxxxxxx>
In-reply-to: <20230921-nahen-ausklammern-aa91c8f49a1c@brauner>

On Thu, Sep 21, 2023 at 11:18 AM Christian Brauner <brauner@xxxxxxxxxx> wrote:
> For pipe_write() it isn't we still need it for pipe_read().

Agree. My patch set removes the spinlock from pipe_write(); the next
patch makes it optional for pipe_read(), eliminating the spinlock for
the most common case.

References:
- When to lock pipe->rd_wait.lock?
  - From: Max Kellermann
- Re: When to lock pipe->rd_wait.lock?
  - From: Christian Brauner
- Re: When to lock pipe->rd_wait.lock?
  - From: Max Kellermann
- Re: When to lock pipe->rd_wait.lock?
  - From: Max Kellermann
- Re: When to lock pipe->rd_wait.lock?
  - From: Christian Brauner

Prev by Date: Re: [PATCH v9 0/7] fuse: full atomic open and atomic-open-revalidate
Next by Date: Re: [PATCH v5 01/11] sound: Fix snd_pcm_readv()/writev() to use iov access functions
Previous by thread: Re: When to lock pipe->rd_wait.lock?
Next by thread: [RFC PATCH v2 0/9] iov_iter: kunit: Cleanup, abstraction and more tests
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux