All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: [Discontig-devel] CLUMPS, CHUNKS and GRANULES
Date: Fri, 16 Aug 2002 23:46:09 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905950@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905942@msgid-missing>

>> >> The mem_map array is the same on each node, copied from the boot_node
>> >> to all other nodes. It contains page_struct entries for ALL pages on
>> >> ALL nodes (if I interpret discontig_paging_init() correctly). The
>> >> first two sentences need to be reformulated.
>> 
>> Arrrghh! Why on earth would you want to do that? How are you going to 
>> atomically update things? Replicating things that are heavily written to is
>> a bad idea.
> 
> We dont do that!!!

Great. Though I'm not suprised it got misread .... the current code around mem_map
is very confusing.

>> PS. If you wanted to change all the disgusting defns of PLAT_XXXXX to something
>> readable, that would make a lot of people happy ;-)
> 
> No problem. What do you suggest.

Anything else! I know you're just following what was already in there, but that
really needs killing too ;-) Something that's readable, not all caps, does what the
name says, and looks like the rest of the kernel VM macros would be nice ;-)

And getting rid of plat_node_data and just shoving it into the pg_data_t with 
everything else might help. Or at least pretending from the macros you do that ;-)

M.



  parent reply	other threads:[~2002-08-16 23:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-16 11:44 [Linux-ia64] Re: [Discontig-devel] CLUMPS, CHUNKS and GRANULES Erich Focht
2002-08-16 21:53 ` Jack Steiner
2002-08-16 22:05 ` Martin J. Bligh
2002-08-16 22:13 ` Martin J. Bligh
2002-08-16 22:28 ` Jack Steiner
2002-08-16 23:46 ` Martin J. Bligh [this message]
2002-08-17  0:26 ` Jack Steiner
2002-08-19 16:33 ` Erich Focht
2002-08-19 21:34 ` Jack Steiner

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=marc-linux-ia64-105590701905950@msgid-missing \
    --to=martin.bligh@us.ibm.com \
    --cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.