1. 05 Oct, 2003 5 commits
    • Andrew Morton's avatar
      [PATCH] Clean up MAX_NR_NODES/NUMNODES/etc. [4/5] · b9fa8456
      Andrew Morton authored
      From: Matthew Dobson <colpatch@us.ibm.com>
      
      Fix up the arm arch.  This needs to be reviewed.  Relatively
      straightforward replacement of NR_NODES with standard MAX_NUMNODES.
      b9fa8456
    • Andrew Morton's avatar
      [PATCH] Clean up MAX_NR_NODES/NUMNODES/etc. [3/5] · dbe97702
      Andrew Morton authored
      From: Matthew Dobson <colpatch@us.ibm.com>
      
      Fix up the sh arch.  sh defined NR_NODES, change sh to use standard
      MAX_NUMNODES instead.
      dbe97702
    • Andrew Morton's avatar
      [PATCH] Clean up MAX_NR_NODES/NUMNODES/etc. [2/5] · 5bdcf4f8
      Andrew Morton authored
      From: Matthew Dobson <colpatch@us.ibm.com>
      
      Remove MAX_NR_NODES.  This value is only used in a couple of places, and
      it's incorrectly used in all those places as far as I can tell.  Replace
      with MAX_NUMNODES.  Create MAX_NODES_SHIFT and use this value to check
      NODES_SHIFT is appropriate.  A possible future patch should make
      MAX_NODES_SHIFT vary based on 32 vs.  64 bit archs.
      5bdcf4f8
    • Andrew Morton's avatar
      [PATCH] Clean up MAX_NR_NODES/NUMNODES/etc. [1/5] · c72da22f
      Andrew Morton authored
      From: Matthew Dobson <colpatch@us.ibm.com>
      
      This starts a series of cleanups against the way in which the various
      architectures specify the number of nodes and memory zones.  We end up
      supporting up to 1024 memory zones on ia64, which is a recent requirement.
      
      Has been tested on ia32, ia64 (UMA), ppa64 (UMA) and NUMAQ.
      
      
      Make sure MAX_NUMNODES is defined in one and only one place.  Remove
      superfluous definitions.  Instead of defining MAX_NUMNODES in
      asm/numnodes.h, we define NODES_SHIFT there.  Then in linux/mmzone.h we
      turn that NODES_SHIFT value into MAX_NUMNODES.
      c72da22f
    • Andrew Morton's avatar
      [PATCH] boot-time selectable log buffer size · 96fcef0a
      Andrew Morton authored
      From: Andrea Arcangeli <andrea@suse.de>
      
      Allow the printk log buffer size to be selected with a __setup parameter,
      `log_buf_len=N', where N must be a power-of-two.
      
      The default, initial statically allocated buffer size is still determined via
      kernel config.
      96fcef0a
  2. 04 Oct, 2003 35 commits