From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <npiggin@suse.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
linux-mm@kvack.org, Christoph Lameter <clameter@engr.sgi.com>,
"Paul E. McKenney" <paulmck@us.ibm.com>
Subject: Re: [RFC][PATCH 3/5] mm: RCUify vma lookup
Date: Thu, 8 Mar 2007 18:31:01 +0100 [thread overview]
Message-ID: <20070308173101.GB16834@elte.hu> (raw)
In-Reply-To: <20070306083632.GA10540@wotan.suse.de>
* Nick Piggin <npiggin@suse.de> wrote:
> > This is a funny scheme you're trying to do in order to try to avoid
> > rwsems. [...]
yeah, i think you are pretty much right.
> ... though I must add that it seems like a very cool patchset and I
> hope I can get time to go through it more thoroughly! Nice work ;)
:) We'll figure out something else. The fundamental problem of vma
lookup scalability is still there, and -rt here isnt really anything
special, it's more like an 'early warning system for scalability
problems' that shows us on single-CPU systems the issues of 1024-CPU
systems ;-)
Ingo
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-03-08 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 1:38 [RFC][PATCH 0/5] Lockless vma lookups Peter Zijlstra
2007-03-06 1:38 ` [RFC][PATCH 1/5] RCU friendly B+tree Peter Zijlstra
2007-03-06 1:38 ` [RFC][PATCH 2/5] mm: use B+tree for vmas Peter Zijlstra
2007-03-06 1:38 ` [RFC][PATCH 3/5] mm: RCUify vma lookup Peter Zijlstra
2007-03-06 2:23 ` Nick Piggin
2007-03-06 8:36 ` Nick Piggin
2007-03-08 17:31 ` Ingo Molnar [this message]
2007-03-06 12:31 ` Peter Zijlstra
2007-03-06 12:35 ` Peter Zijlstra
2007-03-06 1:38 ` [RFC][PATCH 4/5] i386: lockless fault handler Peter Zijlstra
2007-03-06 1:38 ` [RFC][PATCH 5/5] x86_64: " Peter Zijlstra
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=20070308173101.GB16834@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=clameter@engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=paulmck@us.ibm.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