LKML Archive on
help / color / mirror / Atom feed
From: Andi Kleen <>
To: David Rientjes <>
Cc: Andrew Morton <>, Rohit Seth <>,
Subject: Re: [patch -mm 3/5] x86_64: fixed-size remaining fake nodes
Date: Mon, 29 Jan 2007 14:36:59 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thursday 25 January 2007 22:37, David Rientjes wrote:
> Any leftover memory is allocated
> to a final node unless the command-line ends with a comma.

That sounds like syntactical vinegar and a nasty trap. Remember 
that venus probe that got lost because of a wrong comma.
Can you find some nicer syntax for that please? 

Also it's pretty complex. Are there use cases for all of this? 


  parent reply	other threads:[~2007-01-29 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25 21:37 [patch -mm 1/5] x86_64: configurable fake numa node sizes David Rientjes
2007-01-25 21:37 ` [patch -mm 2/5] x86_64: split remaining fake nodes equally David Rientjes
2007-01-25 21:37   ` [patch -mm 3/5] x86_64: fixed-size remaining fake nodes David Rientjes
2007-01-25 21:37     ` [patch -mm 4/5] x86_64: fake numa function annotations David Rientjes
2007-01-25 21:37       ` [patch -mm 5/5] x86_64: fake numa for cpusets document David Rientjes
2007-01-29 13:36     ` Andi Kleen [this message]
2007-01-29 18:38       ` [patch -mm 3/5] x86_64: fixed-size remaining fake nodes David Rientjes
2007-01-30  1:19         ` David Rientjes

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \
    --subject='Re: [patch -mm 3/5] x86_64: fixed-size remaining fake nodes' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).