From: Rik van Riel <riel@conectiva.com.br>
To: markhe@veritas.com
Cc: linux-mm@kvack.org
Subject: Re: Can reverse VM locks?
Date: Mon, 30 Jul 2001 16:10:07 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.33L.0107301603120.5582-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <Pine.LNX.4.33.0107022014190.9756-100000@alloc.wat.veritas.com>
OK, I've been looking at the lock order reversal too,
though for different reasons ;)
On Mon, 2 Jul 2001 markhe@veritas.com wrote:
> On Mon, 2 Jul 2001, Rik van Riel wrote:
> > On Mon, 2 Jul 2001 markhe@veritas.com wrote:
> >
> > > Anyone know of any places where reversing the lock ordering would break?
> >
> > Basically add_to_page_cache and remove_from_page cache and friends ;)
>
> Hmm, does a page-cache page need to be on an LRU list?
>
> If not, the 'add' case falls out OK; add it to the page-cache
> first, then add it to an LRU list _after_ dropping the
> pagecache_lock and taking the pagemap_lru_lock. ie. no lock
> overlap.
Indeed, this would work. I've been looking at this too.
[snip cool analysis]
> True?
Yes, very much true. Now what I wanted to ask about:
do you already have a patch which does this or should
I write a patch which does the lock order reversal ?
cheers,
Rik
--
Executive summary of a recent Microsoft press release:
"we are concerned about the GNU General Public License (GPL)"
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2001-07-30 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-02 18:39 markhe
2001-07-02 19:02 ` Rik van Riel
2001-07-02 19:22 ` markhe
2001-07-02 19:38 ` Rik van Riel
2001-07-30 19:10 ` Rik van Riel [this message]
2001-07-30 19:33 ` Mark Hemment
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=Pine.LNX.4.33L.0107301603120.5582-100000@duckman.distro.conectiva \
--to=riel@conectiva.com.br \
--cc=linux-mm@kvack.org \
--cc=markhe@veritas.com \
/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