From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andi Kleen <ak@suse.de>, "David S. Miller" <davem@davemloft.net>,
benh@kernel.crashing.org, torvalds@osdl.org, akpm@osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] page table iterators
Date: Thu, 24 Feb 2005 10:52:23 +1100 [thread overview]
Message-ID: <421D1737.1050501@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.61.0502230136240.5772@goblin.wat.veritas.com>
Hugh Dickins wrote:
> I'm off to bed, but since your appetite for looking at patches
> is greater than mine, I'll throw what I'm currently testing over
> the wall to you now. Against 2.6.11-rc4-bk9, but my starting point
> was obviously your patches. Not yet split up, but clearly should be.
Yeah you've snuck a few other clever things in there ;)
> Includes mm/swapfile.c which you missed. I'm inlining pmd and pud
Thanks.
> levels, but not pte and pgd levels. No description yet, sorry.
OK - that's probably sufficient for debugging. There is only so
much that can go wrong in the middle levels... how does it look
performance wise? (I can give it a test when it gets split out)
> One point worth making, I do believe throughout that whatever the
> address layout, "end" cannot be 0 - BUG_ON(addr >= end) assures.
>
OK after sleeping on it, I'm warming to your way.
I don't think it makes something like David's modifications any
easier, but mine didn't go a long way to that end either. And
being a more incremental approach gives us more room to move in
future (for example, maybe toward something that really *will*
accommodate the bitmap walking code nicely).
So I'd be pretty happy for you to queue this up with Andrew for
2.6.12. Anyone else?
Nick
next prev parent reply other threads:[~2005-02-24 0:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-17 13:53 [PATCH 1/2] optimise copy page range Nick Piggin
2005-02-17 14:03 ` [PATCH 2/2] page table iterators Nick Piggin
2005-02-17 15:56 ` Linus Torvalds
2005-02-17 16:13 ` Nick Piggin
2005-02-17 19:43 ` Andi Kleen
2005-02-17 22:49 ` Benjamin Herrenschmidt
2005-02-17 23:03 ` Andi Kleen
2005-02-17 23:21 ` Benjamin Herrenschmidt
2005-02-17 23:34 ` Andi Kleen
2005-02-17 23:30 ` David S. Miller
2005-02-17 23:57 ` Andi Kleen
2005-02-20 12:35 ` Nick Piggin
2005-02-21 6:35 ` Hugh Dickins
2005-02-21 6:40 ` Andrew Morton
2005-02-21 7:09 ` Benjamin Herrenschmidt
2005-02-21 8:09 ` Nick Piggin
2005-02-21 9:04 ` Nick Piggin
2005-02-22 9:54 ` Nick Piggin
2005-02-23 2:06 ` Hugh Dickins
2005-02-23 4:31 ` David S. Miller
2005-02-23 4:49 ` Nick Piggin
2005-02-23 4:57 ` David S. Miller
2005-02-23 5:23 ` Nick Piggin
2005-02-23 23:52 ` Nick Piggin [this message]
2005-02-24 0:00 ` David S. Miller
2005-02-24 5:12 ` Hugh Dickins
2005-02-24 5:59 ` Nick Piggin
2005-02-24 11:58 ` Hugh Dickins
2005-02-24 19:33 ` David S. Miller
2005-02-25 10:44 ` Andi Kleen
2005-02-24 21:59 ` Nick Piggin
2005-02-24 22:32 ` Hugh Dickins
2005-02-24 22:52 ` Nick Piggin
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=421D1737.1050501@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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;
as well as URLs for NNTP newsgroup(s).