[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87a5nwwkx7.fsf@debian-BULLSEYE-live-builder-AMD64>
Date: Mon, 19 Feb 2024 20:36:26 +0530
From: Chandan Babu R <chandanbabu@...nel.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org, "Darrick J .
Wong" <djwong@...nel.org>, Mateusz Guzik <mjguzik@...il.com>, Peter
Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>, Will
Deacon <will@...nel.org>, Waiman Long <longman@...hat.com>
Subject: Re: [PATCH v5 0/3] Remove the XFS mrlock
On Wed, Feb 14, 2024 at 10:05:10 PM +0000, Matthew Wilcox wrote:
> On Thu, Jan 11, 2024 at 09:24:21PM +0000, Matthew Wilcox (Oracle) wrote:
>> XFS has an mrlock wrapper around the rwsem which adds only the
>> functionality of knowing whether the rwsem is currently held in read
>> or write mode. Both regular rwsems and rt-rwsems know this, they just
>> don't expose it as an API. By adding that, we can remove the XFS mrlock
>> as well as improving the debug assertions for the mmap_lock when lockdep
>> is disabled.
>>
>> I have an ack on the first patch from Peter, so I would like to see this
>> merged through the XFS tree since most of what it touches is XFS.
>
> What needs to happen to get these picked up to not miss the next merge
> window?
Matthew, I have updated XFS' for-next branch. The HEAD commit is now
49c379d3a72ab86aafeafebe6b43577acb1ef359 ("xfs: use kvfree for buf in
xfs_ioc_getbmap"). Pleae rebase your patchset on top of for-next and either
post the rebased patchset or you can send me a pull request.
--
Chandan
Powered by blists - more mailing lists