From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Hugh Dickins <hugh@veritas.com>, Andrew Morton <akpm@digeo.com>
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm show_free_areas layout
Date: Mon, 28 Oct 2002 09:00:14 -0800 [thread overview]
Message-ID: <526010000.1035824414@flay> (raw)
In-Reply-To: <Pine.LNX.4.44.0210281628550.10378-100000@localhost.localdomain>
> Could we rearrange it? with the hot and cold taps and batchwater
> levels first: those who are interested can swim back to them?
> Omit the word "Zone " (I'd love non-NUMAs to omit "Node 0 " but
> didn't find the right #define).
#ifdef CONFIG_NUMA, or for less ugly code, you should just be able
to do "if (numnodes > 1)", which will optimise away by the compiler
on non-NUMA.
M.
prev parent reply other threads:[~2002-10-28 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-28 16:58 [PATCH] mm show_free_areas layout Hugh Dickins
2002-10-28 17:00 ` Martin J. Bligh [this message]
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=526010000.1035824414@flay \
--to=mbligh@aracnet.com \
--cc=akpm@digeo.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.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).