From: yoma sophian <sophian.yoma@gmail.com>
To: linux-mm@kvack.org
Subject: Fwd: about memory zone usage
Date: Wed, 29 Apr 2015 00:29:47 +0800 [thread overview]
Message-ID: <CADUS3onYDQcqniBX_--1a_kmu0=+1GmC92JtBM+wvJp0xuUP8Q@mail.gmail.com> (raw)
In-Reply-To: <CADUS3okfhfT3a4gQ7pOKWvLvzoB6Y80EAZe7sh3XT_h3oi5+2Q@mail.gmail.com>
hi all:
in buddy allocator heart function, __alloc_pages_nodemask, I found we
use zonelist-> _zonerefs to iterate all the zone in NUMA or UMA.
My questions are:
1. the advantage of travelling zonelist-> _zonerefs instead of
iterating zones on each node is because it is faster, right?
2. zonelist-> _zonerefs has recorded information of each zone, under
what circumstances we will iterated zone of node to get zone's data
instead of zonelist-> _zonerefs
appreciate your help in advance,
--
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>
parent reply other threads:[~2015-04-28 16:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CADUS3okfhfT3a4gQ7pOKWvLvzoB6Y80EAZe7sh3XT_h3oi5+2Q@mail.gmail.com>]
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='CADUS3onYDQcqniBX_--1a_kmu0=+1GmC92JtBM+wvJp0xuUP8Q@mail.gmail.com' \
--to=sophian.yoma@gmail.com \
--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