linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Matthew Dobson <colpatch@us.ibm.com>
Cc: "Martin J. Bligh" <mbligh@aracnet.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-mm@kvack.org, LSE <lse-tech@lists.sourceforge.net>,
	Andrew Morton <akpm@zip.com.au>,
	Michael Hohnbaum <hohnbaum@us.ibm.com>
Subject: Re: [rfc][patch] Memory Binding API v0.3 2.5.41
Date: Mon, 14 Oct 2002 17:58:10 -0700	[thread overview]
Message-ID: <20021015005810.GL4488@holomorphy.com> (raw)
In-Reply-To: <3DAB669B.3000801@us.ibm.com>

On Mon, Oct 14, 2002 at 05:51:39PM -0700, Matthew Dobson wrote:
> Well, since each node's memory (or memblk in the parlance of my head ;) 
> has several 'zones' in it (DMA, HIGHMEM, etc), this conversion function 
> will need 2 parameters.  It may well be called 
> __node_and_zone_type_to_flat_zone_number(node, DMA|NORMAL|HIGHMEM).
> Or, we could have:
> __zone_to_node(5) = node #
> and
> __zone_to_zone_type(5) = DMA|NORMAL|HIGHMEM.
> But either way, we would need to specify both pieces.
> Cheers!
> -Matt

Zone "type" can be found in (page->flags >> ZONE_SHIFT) & 0x3UL and
similarly node ID can be found in page_zone(page)->zone_pgdat->node_id
and these are from the page.

zone->zone_pgdat->node_id does the zone to node conversion
zone - zone_pgdat->node_zones does the zone to zone type conversion.

Node and zone type to flat zone number would be
	NODE_DATA(nid)->node_zones[type]

Basically there's a number written in page->flags that should be easy
to decode if you can go on arithmetic alone, and if you need details,
there's a zone_table[] you can get at the zones (and hence pgdats) with.


Bill
--
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/

  reply	other threads:[~2002-10-15  0:58 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-10  1:12 Matthew Dobson
2002-10-10  3:05 ` Andrew Morton
2002-10-10 18:29   ` Matthew Dobson
2002-10-10  4:06 ` Martin J. Bligh
2002-10-10 18:43   ` Matthew Dobson
2002-10-10  9:00 ` Arjan van de Ven
2002-10-10 18:55   ` Matthew Dobson
2002-10-10 10:06 ` Arjan van de Ven
2002-10-10 11:22   ` Alan Cox
2002-10-10 11:28     ` William Lee Irwin III
2002-10-10 19:09       ` Matthew Dobson
2002-10-10 19:06     ` Matthew Dobson
2002-10-10 19:01   ` Matthew Dobson
2002-10-13 22:22 ` Eric W. Biederman
2002-10-15  0:14   ` Matthew Dobson
2002-10-15  0:20     ` Martin J. Bligh
2002-10-15  0:38       ` Matthew Dobson
2002-10-15  0:43         ` Martin J. Bligh
2002-10-15  0:51           ` Matthew Dobson
2002-10-15  0:58             ` William Lee Irwin III [this message]
2002-10-15  0:55         ` [Lse-tech] " john stultz
2002-10-15  1:08           ` Martin J. Bligh
2002-10-15  1:20             ` William Lee Irwin III
2002-10-15  1:29               ` Martin J. Bligh
2002-10-15  1:40                 ` William Lee Irwin III
2002-10-15  1:57                   ` William Lee Irwin III
2002-10-15  1:08           ` William Lee Irwin III
2002-10-15  1:16             ` Martin J. Bligh
2002-10-15 17:21     ` Eric W. Biederman

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=20021015005810.GL4488@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=akpm@zip.com.au \
    --cc=colpatch@us.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=hohnbaum@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lse-tech@lists.sourceforge.net \
    --cc=mbligh@aracnet.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