From: "David S. Miller" <davem@davemloft.net>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: akpm@osdl.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] sparsemem intro patches
Date: Mon, 14 Mar 2005 13:50:21 -0800 [thread overview]
Message-ID: <20050314135021.639d1533.davem@davemloft.net> (raw)
In-Reply-To: <1110834883.19340.47.camel@localhost>
On Mon, 14 Mar 2005 13:14:43 -0800
Dave Hansen <haveblue@us.ibm.com> wrote:
> Three of these are i386-only, but one of them reorganizes the macros
> used to manage the space in page->flags, and will affect all platforms.
> There are analogous patches to the i386 ones for ppc64, ia64, and
> x86_64, but those will be submitted by the normal arch maintainers.
Sparc64 uses some of the upper page->flags bits to store D-cache
flushing state.
Specifically, PG_arch_1 is used to set whether the page is scheduled
for delayed D-cache flushing, and bits 24 and up say which CPU the
CPU stores occurred on (and thus which CPU will get the cross-CPU
message to flush it's D-cache should the deferred flush actually
occur).
I imagine that since we don't support the domain stuff (yet) on sparc64,
your patches won't break things, but it is something to be aware of.
next prev parent reply other threads:[~2005-03-14 21:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-14 21:14 Dave Hansen
2005-03-14 21:50 ` David S. Miller [this message]
2005-03-14 22:18 ` Dave Hansen
2005-03-14 22:33 ` David S. Miller
2005-03-15 2:30 ` Andrew Morton
2005-03-15 3:53 ` Dave Hansen
2005-03-15 14:56 ` Martin J. Bligh
2005-03-17 16:21 ` Andy Whitcroft
2005-03-19 19:33 ` Pavel Machek
2005-03-28 21:23 ` Dave Hansen
2005-03-28 22:22 ` Pavel Machek
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=20050314135021.639d1533.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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
all inboxes | Powered by JetHome®