1. 12 Jan, 2006 2 commits
    • Andi Kleen's avatar
      [PATCH] x86_64: Return -1 for unknown PCI bus affinity · e4e94072
      Andi Kleen authored
      
      
      When we don't know the node a PCI bus is connected to return -1.
      This matches the generic code.
      
      Noticed by Ravikiran G Thirumalai <kiran@scalex86.org>
      
      Cc: Ravikiran G Thirumalai <kiran@scalex86.org>
      Signed-off-by: default avatarAndi Kleen <ak@suse.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      e4e94072
    • Andi Kleen's avatar
      [PATCH] x86_64: Validate SLIT table · 1584b89c
      Andi Kleen authored
      
      
      A lot of Opteron BIOS just pass 10 in all SLIT entries (10 is the
      normalized unit). This is actually worse than the default heuristic
      because it leads to pci_distance not knowing the difference between
      local and remote nodes anymore. This messes up some NUMA
      heuristics in generic code.
      
      In this case it's better to fall back to the default heuristic
      which just does nodea == nodeb ? 10 : 20.
      
      This patch does some basic sanity checking on the SLIT and only accepts
      the SLIT when it passes.
      
      Invariants enforced are:
      - Node to itself shall be 10
      - Any other distance shouldn't be 10
      - Distances smaller than 10 are illegal
      Signed-off-by: default avatarAndi Kleen <ak@suse.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      1584b89c
  2. 15 Nov, 2005 2 commits
    • Magnus Damm's avatar
      [PATCH] x86_64: Make node boundaries consistent · ffd10a2b
      Magnus Damm authored
      
      
      The current x86_64 NUMA memory code is inconsequent when it comes to node
      memory ranges. The exact behaviour varies depending on which config option
      that is used.
      
      setup_node_bootmem() has start and end as arguments and these are used to
      calculate the size of the node like this: (end - start). This is all fine
      if end is pointing to the first non-available byte. The problem is that the
      current x86_64 code sometimes treats it as the last present byte and sometimes
      as the first non-available byte. The result is that some configurations might
      lose a page at the end of the range.
      
      This patch tries to fix CONFIG_ACPI_NUMA, CONFIG_K8_NUMA and CONFIG_NUMA_EMU
      so they all treat the end variable as the first non-available byte. This is
      the same way as the single node code.
      
      The patch is boot tested on dual x86_64 hardware with the above configurations,
      but maybe the removed code is needed as some workaround?
      Signed-off-by: default avatarMagnus Damm <magnus@valinux.co.jp>
      Signed-off-by: default avatarAndi Kleen <ak@suse.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      ffd10a2b
    • Andi Kleen's avatar
      [PATCH] x86_64: Speed up numa_node_id by putting it directly into the PDA · 69d81fcd
      Andi Kleen authored
      
      
      Not go from the CPU number to an mapping array.
      Mode number is often used now in fast paths.
      
      This also adds a generic numa_node_id to all the topology includes
      
      Suggested by Eric Dumazet
      Signed-off-by: default avatarAndi Kleen <ak@suse.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      69d81fcd
  3. 12 Sep, 2005 6 commits
  4. 29 Jul, 2005 2 commits
  5. 16 Apr, 2005 1 commit
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4