linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hemment <markhe@veritas.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-mm@kvack.org
Subject: Re: Can reverse VM locks?
Date: Mon, 30 Jul 2001 20:33:40 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.33.0107302022250.13705-100000@alloc.wat.veritas.com> (raw)
In-Reply-To: <Pine.LNX.4.33L.0107301603120.5582-100000@duckman.distro.conectiva>

On Mon, 30 Jul 2001, Rik van Riel wrote:

> 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?
>
> 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 ?

  I did do it, only took a couple of hours, but didn't show any measurable
improvement on a four-way box so I put it on the back-burner.  It is
probably lying around on an off-lined disk somewhere - I'll try to dig it
out tomorrow (time for pub/home in the UK), or re-code it.

  Three points to note;
	1) Looked like it might allow for easily coding of per page-cache
	   line spinlocks (if we want to go there).
	2) I suspected the pagemap_lru_lock was still under heavy
	   contention (the reversal wouldn't have helped it).
	3) In filemap.c, the pagecache_lock and pagemap_lru_lock are far
	   too "close" - need to be L1 cached aligned.

Mark

--
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/

      reply	other threads:[~2001-07-30 19:33 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
2001-07-30 19:33       ` Mark Hemment [this message]

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.33.0107302022250.13705-100000@alloc.wat.veritas.com \
    --to=markhe@veritas.com \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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