[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wgsUtTRWT6kXxw6f2xpS4W=7iO6k2rJfhpLa6yFZ-b_1w@mail.gmail.com>
Date: Mon, 14 Sep 2020 17:42:18 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Matthieu Baerts <matthieu.baerts@...sares.net>
Cc: Michael Larabel <Michael@...haellarabel.com>,
Matthew Wilcox <willy@...radead.org>,
Amir Goldstein <amir73il@...il.com>,
"Ted Ts'o" <tytso@...gle.com>,
Andreas Dilger <adilger.kernel@...ger.ca>,
Ext4 Developers List <linux-ext4@...r.kernel.org>,
Jan Kara <jack@...e.cz>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: Kernel Benchmarking
On Mon, Sep 14, 2020 at 1:53 PM Linus Torvalds
<torvalds@...ux-foundation.org> wrote:
>
> One way I can see that happening (with the fair page locking) is to do
> something like this
Note that the "lock_page()" cases in that deadlock example sequence of
mine is not necessarily at all an explicit lock_page(). It is more
likely to be something that indirectly causes it - like a user access
that faults in the page and causes lock_page() as part of that.
Linus
Powered by blists - more mailing lists