[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgC9fB-Fq=pZQBDC0nZBWkxPRz-R95vbKjwHmSyU7Ex3w@mail.gmail.com>
Date: Sun, 24 Nov 2024 17:26:24 -0800
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Al Viro <viro@...iv.linux.org.uk>, Mateusz Guzik <mjguzik@...il.com>,
"Darrick J. Wong" <djwong@...nel.org>, Hao-ran Zheng <zhenghaoran@...a.edu.cn>, brauner@...nel.org,
jack@...e.cz, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
baijiaju1990@...il.com, 21371365@...a.edu.cn
Subject: Re: [RFC] metadata updates vs. fetches (was Re: [PATCH v4] fs: Fix
data race in inode_set_ctime_to_ts)
On Sun, 24 Nov 2024 at 17:15, Matthew Wilcox <willy@...radead.org> wrote:
>
> I literally said that.
Bah, I misunderstood you.
Then yes, if all the writers are always in order, and you don't
actually care about exact time matching but only ordering, I guess it
might work.
But since you need all the same barriers that you would need for just
doing it right with a seqcount, it's not much of an advantage, and it
doesn't give you consistency for any other kind of action.
Linus
Powered by blists - more mailing lists