From: Christoph Lameter <clameter@sgi.com>
To: David Miller <davem@davemloft.net>
Cc: akpm@linux-foundation.org, apw@shadowen.org,
kamezawa.hiroyu@jp.fujitsu.com, kosaki.motohiro@jp.fujitsu.com,
riel@redhat.com, jeremy@goop.org, linux-mm@kvack.org
Subject: Re: [patch 0/9] Page flags V3: Cleanup and reorg
Date: Thu, 10 Apr 2008 10:33:54 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0804101033220.11823@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0804031149060.7108@schroedinger.engr.sgi.com>
Ping? Is this okay Dave?
On Thu, 3 Apr 2008, Christoph Lameter wrote:
> On Wed, 2 Apr 2008, David Miller wrote:
>
> > No this won't work, see PG_dcache_cpu_shift in arch/sparc64/mm/init.c,
> > the code currently statically puts the cpu number of the the cpu which
> > potentially dirtied the page in the D-cache at bit 32 of the page
> > flags and onwards.
>
> That looks fine to me. If we use less than 32 page flags then bits 32 to
> the beginning of the zone field are still available.
--
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 parent reply other threads:[~2008-04-10 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080401200019.47892504.akpm@linux-foundation.org>
[not found] ` <Pine.LNX.4.64.0804021026400.26938@schroedinger.engr.sgi.com>
[not found] ` <Pine.LNX.4.64.0804022125001.1684@schroedinger.engr.sgi.com>
[not found] ` <20080402.222542.106676535.davem@davemloft.net>
[not found] ` <Pine.LNX.4.64.0804031149060.7108@schroedinger.engr.sgi.com>
2008-04-10 17:33 ` Christoph Lameter [this message]
[not found] <20080318181957.138598511@sgi.com>
2008-03-28 9:08 ` [patch 0/9] Page flags V3: Cleanup and reorg Andrew Morton
[not found] <20080308001850.306617873@sgi.com>
2008-03-11 4:50 ` Andrew Morton
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.64.0804101033220.11823@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=davem@davemloft.net \
--cc=jeremy@goop.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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;
as well as URLs for NNTP newsgroup(s).