From: "David S. Miller" <davem@davemloft.net>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: hugh@veritas.com, ak@suse.de, benh@kernel.crashing.org,
torvalds@osdl.org, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] page table iterators
Date: Tue, 22 Feb 2005 20:57:22 -0800 [thread overview]
Message-ID: <20050222205722.4e228aba.davem@davemloft.net> (raw)
In-Reply-To: <1109134170.5177.9.camel@npiggin-nld.site>
On Wed, 23 Feb 2005 15:49:30 +1100
Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> > It's easy to toy with the sparc64 optimization on other platforms,
> > just add the necessary hacks to pmd_set and pgd_set, allocation
> > of pmd and pgd tables
>
> David: just an implementation detail that I had meant to bring
> up earlier - would it feel like less of a hack to put these in
> pmd_populate and pgd_populate?
Sure, no problem. They get defined to pmd_set/pgd_set calls
anyways. But wouldn't that miss pgd_clear() and pmd_clear()?
Someone may find it worthwhile to, on a *_clear(), to see if
a set bit can now be clear because all the neighboring entries
are empty as well.
That might have been the reason I put it there, but I may be
giving myself too much credit :-)
next prev parent reply other threads:[~2005-02-23 4:58 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 [this message]
2005-02-23 5:23 ` Nick Piggin
2005-02-23 23:52 ` Nick Piggin
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=20050222205722.4e228aba.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--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