1. 18 8月, 2005 5 次提交
  2. 12 8月, 2005 5 次提交
  3. 09 8月, 2005 1 次提交
  4. 02 8月, 2005 1 次提交
    • I
      [PATCH] remove sys_set_zone_reclaim() · 6cb54819
      Ingo Molnar 提交于
      This removes sys_set_zone_reclaim() for now.  While i'm sure Martin is
      trying to solve a real problem, we must not hard-code an incomplete and
      insufficient approach into a syscall, because syscalls are pretty much
      for eternity.  I am quite strongly convinced that this syscall must not
      hit v2.6.13 in its current form.
      
      Firstly, the syscall lacks basic syscall design: e.g. it allows the
      global setting of VM policy for unprivileged users. (!) [ Imagine an
      Oracle installation and a SAP installation on the same NUMA box fighting
      over the 'optimal' setting for this flag. What will they do? Will they
      try to set the flag to their own preferred value every second or so? ]
      
      Secondly, it was added based on a single datapoint from Martin:
      
       http://marc.theaimsgroup.com/?l=linux-mm&m=111763597218177&w=2
      
      where Martin characterizes the numbers the following way:
      
       ' Run-to-run variability for "make -j" is huge, so these numbers aren't
         terribly useful except to see that with reclaim the benchmark still
         finishes in a reasonable amount of time. '
      
      in other words: the fundamental problem has likely not been solved, only
      a tendential move into the right direction has been observed, and a
      handful of numbers were picked out of a set of hugely variable results,
      without showing the variability data. How much variance is there
      run-to-run?
      
      I'd really suggest to first walk the walk and see what's needed to get
      stable & predictable kernel compilation numbers on that NUMA box, before
      adding random syscalls to tune a particular aspect of the VM ... which
      approach might not even matter once the whole picture has been analyzed
      and understood!
      
      The third, most important point is that the syscall exposes VM tuning
      internals in a completely unstructured way. What sense does it make to
      have a _GLOBAL_ per-node setting for 'should we go to another node for
      reclaim'? If then it might make sense to do this per-app, via numalib or
      so.
      
      The change is minimalistic in that it doesnt remove the syscall and the
      underlying infrastructure changes, only the user-visible changes.  We
      could perhaps add a CAP_SYS_ADMIN-only sysctl for this hack, a'ka
      /proc/sys/vm/swappiness, but even that looks quite counterproductive
      when the generic approach is that we are trying to reduce the number of
      external factors in the VM balance picture.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      6cb54819
  5. 28 7月, 2005 2 次提交
    • K
      [IA64] unwind.c uses wrong unat from switch_stack · b833961b
      Keith Owens 提交于
      unwind.c can read the wrong unat bits from switch_stack.
      sw->caller_unat is the value of ar.unat when the task was blocked.
      sw->ar_unat is the value of ar.unat after doing st8.spill for r4-7.
      IOW, ar_unat is caller_unat with 4 bits changed.
      
      unw_access_gr() uses sw->ar_unat for r4-7 (correct), but it also uses
      sw->ar_unat for other scratch registers (incorrect).  sw->ar_unat
      should only be used for r4-7, everything else should use
      sw->caller_unat, unless modified by unwind info.  Using sw->ar_unat
      risks picking up the 4 bits that were overwritten when r4-7 were saved.
      
      Also this line is wrong
      	unw.sw_off[unw.preg_index[UNW_REG_PFS]] = SW(AR_UNAT);
      and should be
      	unw.sw_off[unw.preg_index[UNW_REG_PFS]] = SW(AR_PFS);
      Signed-off-by: NKeith Owens <kaos@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      b833961b
    • R
      [IA64] inotify: ia64 syscalls. · d108919b
      Robert Love 提交于
      Attached patch adds the inotify syscalls to ia64.
      Signed-off-by: NRobert Love <rml@novell.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      d108919b
  6. 27 7月, 2005 2 次提交
  7. 15 7月, 2005 1 次提交
  8. 14 7月, 2005 1 次提交
  9. 13 7月, 2005 4 次提交
    • C
      [IA64] Altix pcibus_to_node implementation · 7c2a6c62
      Christoph Lameter 提交于
      The Altix subarch does not provide node information via ACPI. Instead hooks
      are used to fixup pci structures. This patch determines the nodes for Altix
      PCI busses.
      
      Remote Bridges:
      ---------------
      Altix supports remote I/O nodes without memory or processors but with bridges.
      The TIOCA type of bridge is an AGP bridge and the PROM provides information
      about the closest node. That information will be returned by pcibus_to_node.
      
      The TIOCP remote bridge type is a PCI bridge but the PROM does not provide a
      closest node id. pcibus_to_node will return -1 for devices on those bridges
      meaning that device control structures may be allocated on any node.
      
      Safeguard:
      ----------
      Should the fixups result in invalid node information for a pci controller then
      a warning will be printed and pcibus_to_node will return -1.
      
      
      This patch also fixes the "FIXME" in sn_dma_alloc_coherent. This means that
      dma_alloc_coherent will now use alloc_pages_node to allocate memory local to
      the node that the PCI device is connected to.
      Signed-off-by: NChristoph Lameter <clameter@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      7c2a6c62
    • Z
      [IA64] improve flush_icache_range() · 08357f82
      Zoltan Menyhart 提交于
      Check with PAL to see what the i-cache line size is for
      each level of the cache, and so use the correct stride
      when flushing the cache.
      
      Acked-by: David Mosberger
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      08357f82
    • G
      [IA64] remove CONFIG_IA64_SGI_SN_SIM · 60a762b6
      Greg Edwards 提交于
      This patch removes the CONFIG_IA64_SGI_SN_SIM option entirely, allowing
      any kernel bootable on sn2 to also be booted in the simulator.
      
      Boot tested on Altix and HP rx2600.
      Signed-off-by: NGreg Edwards <edwardsg@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      60a762b6
    • C
      [IA64] pcibus_to_node implementation for IA64 · 514604c6
      Christoph Lameter 提交于
      pcibus_to_node provides a way for the Linux kernel to identify to which
      node a certain pcibus connects to. Allocations of control structures
      for devices can then be made on the node where the pci bus is located
      to allow local access during interrupt and other device manipulation.
      
      This patch provides a new "node" field in the the pci_controller
      structure. The node field will be set based on ACPI information (thanks
      to Alex Williamson  <alex.williamson@hp.com for that piece).
      Signed-off-by: NChristoph Lameter <clameter@sgi.com>
      Signed-off-by: NTony Luck <tony.luck@intel.com>
      514604c6
  10. 12 7月, 2005 6 次提交
  11. 09 7月, 2005 1 次提交
  12. 08 7月, 2005 1 次提交
  13. 07 7月, 2005 8 次提交
  14. 06 7月, 2005 1 次提交
  15. 30 6月, 2005 1 次提交