An error occurred fetching the project authors.
  1. 19 Jan, 2004 2 commits
    • Andrew Morton's avatar
      [PATCH] input: psmouse option parsing · a03c40a3
      Andrew Morton authored
      From: Dmitry Torokhov <dtor_core@ameritech.net>
      
      With Vojtech's approval adjusted psmouse option names by dropping psmouse_
      prefix.
      
      If psmouse is compiled as a module new option names are: proto, rate,
      resetafter, resolution, smartscroll
      
      If psmouse is built in the kernel the prefix "psmouse." is required in
      front of an option, like "psmouse.proto"
      
      Also, since we are changing all names, killed psmouse_noext completely
      a03c40a3
    • Andrew Morton's avatar
      [PATCH] input: i8042 option parsing · 687e435a
      Andrew Morton authored
      From: Dmitry Torokhov <dtor_core@ameritech.net>
      
      With Vojtech's approval adjusted i8042 option names by dropping i8042_
      prefix.
      
      If i8042 is compiled as a module new option names are: direct, dumbkbd,
      noaux, nomux, reset, unlock.
      
      If i8042 is build in the kernel the prefix "i8042." is required in front of
      an option, like "i8042.reset"
      687e435a
  2. 30 Dec, 2003 1 commit
    • Andrew Morton's avatar
      [PATCH] Fix 2.6.0's broken documentation references · 56d7e6f4
      Andrew Morton authored
      From: Hans Ulrich Niedermann <linux-kernel@n-dimensional.de>
      
      I've noted that 2.6.0 contains broken references to documentation.
      
      I got sufficiently annoyed chasing doc files in the wrong place
      that I wrote a script to check the references to documentation
      files.
      
      Some documentation files have moved (e.g.  Documentation/modules.txt to
      Documentation/kbuild/modules.txt).  I adapted the references with a script.
      56d7e6f4
  3. 29 Dec, 2003 1 commit
  4. 18 Dec, 2003 1 commit
    • Dmitry Torokhov's avatar
      [PATCH] Input: add psmouse_proto parameter · c0fbf5b6
      Dmitry Torokhov authored
      New parameter psmouse_proto to replace psmouse_noext.  Allows to specify
      highest PS/2 protocol extension that kernel has permission to negotiate
      (bare|imps|exps).  psmouse_noext marked as deprecated and emits a warning
      when used.  parameter parsing converted to the new scheme.
      c0fbf5b6
  5. 05 Oct, 2003 1 commit
    • 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
  6. 18 Sep, 2003 1 commit
    • Peter Osterlund's avatar
      Input: Big Synaptics update: · 2e92db0d
      Peter Osterlund authored
      	Restore synaptics pad mode on module unload.
      	Support Synaptics touchpads with multiple buttons.
      	Make Synaptics touchpad support optional.
      	Add passthrough support for Synaptics touchpads. [Dmitry]
      	Add support for old Synaptics protocol.
      	Set mode byte correctly for old Synaptics pads.
      	Fix multibutton support of Synaptics pads.
      2e92db0d
  7. 09 Sep, 2003 1 commit
  8. 31 Aug, 2003 1 commit
  9. 19 Aug, 2003 1 commit
    • Andrew Morton's avatar
      [PATCH] Local APIC enable fixes · a5bfb7f3
      Andrew Morton authored
      From: mikep@csd.uu.se
      
      There has been a number of problem reports about local APIC
      interacting badly with ACPI on P4s due to the P4 local APIC
      force-enable change in 2.5.74,
      
      This patch reverts the 2.5.74 patch, so if the BIOS disables
      the local APIC on a P4, we don't enable it by default any more.
      
      The rescue the situation for those P4 systems where the local
      APIC _can_ be enabled safely, I've added two kernel parameters
      that can be used to override broken BIOSen:
      - "nolapic" prevents the kernel from enabling or using the local
        APIC. This is stronger than listing a machine in the DMI scan
        blacklist, since it also works for machines that boot with the
        local APIC already enabled.
      - "lapic" tells the kernel to force-enable the P4 local APIC if
        the BIOS disabled it. I haven't changed the logic for P6/K7
        family processors, so we still force-enable those unless
        "nolapic" was passed to the kernel.
      
      The patch also includes a cleanup: the dont_use_local_apic_timer
      flag variable is not set any more since 2.5.74, so it's removed.
      a5bfb7f3
  10. 09 Aug, 2003 1 commit
    • Len Brown's avatar
      ACPI from 2.4: · 68e4ad79
      Len Brown authored
      build: add ACPI_HT, delete ACPI_HT_ONLY
      boot: add acpi={force, off, ht}; delete "noht", "acpismp="
      add DMI blacklist from UnitedLinux
      68e4ad79
  11. 10 Jul, 2003 1 commit
    • Andrew Morton's avatar
      [PATCH] misc fixes · ecbaa730
      Andrew Morton authored
      - remove accidental debug code from ext3 commit.
      
      - /proc/profile documentation fix (Randy Dunlap)
      
      - use sb_breadahead() in ext2_preread_inode()
      
      - unused var in mpage_writepages()
      ecbaa730
  12. 26 Jun, 2003 1 commit
  13. 06 Jun, 2003 2 commits
    • Andrew Morton's avatar
      [PATCH] /proc/sys/vm/min_free_kbytes · cefe53f8
      Andrew Morton authored
      From: Matthew Dobson <colpatch@us.ibm.com>
      
      This resurrects the old /proc/sys/vm/free_pages functionality: the ability to
      tell page reclaim how much free memory to maintain.
      
      This may be needed for specialised networking applications, and it provides
      an interesting way to stress the kernel: set it very low so atomic
      allocations can easily fail.
      
      Also, a 16G ppc64 box currently cruises along at 1M free memory, which is
      surely too little to supporthigh-speed networking.  We have not changed that
      setting here, but it is now possible to do so.
      
      The patch also reduces the amount of free memory which the VM will maintain
      in ZONE_HIGHMEM, as it is almost always wasted memory.
      cefe53f8
    • Andrew Morton's avatar
      [PATCH] IRQs: handle bad return values from handlers · 13c01fe7
      Andrew Morton authored
      Attempt to do something intelligent with IRQ handlers which don't return
      IRQ_HANDLED.
      
      - If they return neither IRQ_HANDLED nor IRQ_NONE, complain.
      
      - If they return IRQ_NONE more than 99900 times in 100000 interrupts, complain
        and disable the IRQ.
      
        I did have it at 750-in-1000, but someone had an otherwise-functioning
        system which triggered it.
      
        The 99.9% ratio is designed to address the problem wherein the babbling
        device shares an IRQ with a good device.  We don't want the good device's
        trickle of IRQ_HANDLED callouts to defeat the lockup detector.  (fat chance
        os this working right).
      
      - Add a kernel boot parameter `noirqdebug' to turn the whole thing off.
      13c01fe7
  14. 26 May, 2003 1 commit
  15. 25 May, 2003 1 commit
    • John Levon's avatar
      [PATCH] OProfile: timer usage override · fed4d7bd
      John Levon authored
      A patch mostly by Will Cohen, adding a parameter to OProfile to
      over-ride use of the perfctr hardware. Useful for testing and
      a host of other things.
      fed4d7bd
  16. 28 Mar, 2003 2 commits
    • Andrew Morton's avatar
      [PATCH] x86 clock override boot option · 5958cbab
      Andrew Morton authored
      From: john stultz <johnstul@us.ibm.com>
      
      This patch allows one to manually specify the i386 gettimeofday time-source
      by passing clock=[pit|tsc|cyclone|...] as a boot argument.  The argument will
      override the default probled selection, and in case the selected time-source
      not be avalible the code defaults to using the PIT (printing a warning saying
      so).
      5958cbab
    • Andrew Morton's avatar
      [PATCH] initcall debug code · a3fa4e81
      Andrew Morton authored
      The patch is designed to help locate where the kernel is dying during the
      startup sequence.
      
      - Boot parameter "initcall_debug" causes the kernel to print out the
        address of each initcall before calling it.
      
        The kallsyms tables do not cover __init sections, so printing the
        symbolic version of these symbols doesn't work.  They need to be looked up
        in System.map.
      
      - Detect whether an initcall returns with interrupts disabled or with a
        locking imbalance.  If it does, complain and then try to fix it up.
      a3fa4e81
  17. 21 Mar, 2003 1 commit
  18. 16 Mar, 2003 1 commit
    • Andrew Morton's avatar
      [PATCH] Fix mem= options · 585c3653
      Andrew Morton authored
      Patch from "Randy.Dunlap" <rddunlap@osdl.org>
      
      Reverts the recent alteration of the format of the `mem=' option.  This is
      because `mem=' is interpreted by bootloaders and may not be freely changed.
      
      Instead, the new functionality to set specific memory region usages is
      provided via the new "memmap=" option.
      
      The documentation for memmap= is added, and the documentation for mem= is
      updated.
      585c3653
  19. 26 Feb, 2003 1 commit
  20. 06 Feb, 2003 2 commits
    • Andrew Morton's avatar
      [PATCH] ia32 IRQ distribution rework · 08f16f8f
      Andrew Morton authored
      Patch from "Kamble, Nitin A" <nitin.a.kamble@intel.com>
      
      Hello All,
      
        We were looking at the performance impact of the IRQ routing from
      the 2.5.52 Linux kernel. This email includes some of our findings
      about the way the interrupts are getting moved in the 2.5.52 kernel.
      Also there is discussion and a patch for a new implementation. Let
      me know what you think at nitin.a.kamble@intel.com
      
      Current implementation:
      ======================
      We have found that the existing implementation works well on IA32
      SMP systems with light load of interrupts. Also we noticed that it
      is not working that well under heavy interrupt load conditions on
      these SMP systems. The observations are:
      
      * Interrupt load of each IRQ is getting balanced on CPUs independent
      of load of other IRQs. Also the current implementation moves the
      IRQs randomly. This works well when the interrupt load is light. But
      we start seeing imbalance of interrupt load with existence of
      multiple heavy interrupt sources. Frequently multiple heavily loaded
      IRQs gets moved to a single CPU while other CPUs stay very lightly
      loaded. To achieve a good interrupts load balance, it is important to
      consider the load of all the interrupts together.
          This further can be explained with an example of 4 CPUs and 4
      heavy interrupt sources. With the existing random movement approach,
      the chance of each of these heavy interrupt sources moving to separate
      CPUs is: (4/4)*(3/4)*(2/4)*(1/4) = 3/16. It means 13/16 = 81.25% of
      the time the situation is, some CPUs are very lightly loaded and some
      are loaded with multiple heavy interrupts. This causes the interrupt
      load imbalance and results in less performance. In a case of 2 CPUs
      and 2 heavily loaded interrupt sources, this imbalance happens
      1/2 = 50% of the times. This issue becomes more and more severe with
      increasing number of heavy interrupt sources.
      
      * Another interesting observation is: We cannot see the imbalance
      of the interrupt load from /proc/interrupts. (/proc/interrupts shows
      the cumulative load of interrupts on all CPUs.) If the interrupt load
      is imbalanced and this imbalance is getting rotated among CPUs
      continuously, then /proc/interrupts will still show that the interrupt
      load is going to processors very evenly. Currently at the frequency
      (HZ/50) at which IRQs are moved across CPUs, it is not possible to
      see any interrupt load imbalance happening.
      
      * We have also found that, in certain cases the static IRQ binding
      performs better than the existing kernel distribution of interrupt
      load. The reason is, in a well-balanced interrupt load situations,
      these interrupts are unnecessarily getting frequently moved across
      CPUs. This adds an extra overhead; also it takes off the CPU cache
      warmth benefits.
        This came out from the performance measurements done on a 4-way HT
      (8 logical processors) Pentium 4 Xeon system running 8 copies of
      netperf. The 4 NICs in the system taking different IRQs generated
      sizable interrupt load with the help of connected clients.
      
      Here the netperf transactions/sec throughput numbers observed are:
      
      IRQs nicely manually bound to CPUs: 56.20K
      The current kernel implementation of IRQ movement: 50.05K
       -----------------------
       The static binding of IRQs has performed 12.28% better than the
      current IRQ movement implemented in the kernel.
      
      * The current implementation does not distinguish siblings from the
      HT (Hyper-Threading(tm)) enabled CPUs. It will be beneficial to
      balance the interrupt load with respect to processor packages first,
      and then among logical CPUs inside processor packages.
        For example if we have 2 heavy interrupt sources and 2 processor
      packages (4 logical CPUs); Assigning both the heavy interrupt sources
      in different processor packages is better, it will use different
      execution resources from the different processor packages.
      
      
      
      New revised implementation:
      ==========================
      We also have been working on a new implementation. The following
      points are in main focus.
      
      * At any moment heavily loaded IRQs are distributed to different
      CPUs to achieve as much balance as possible.
      
      * Lightly loaded interrupt sources are ignored from the load
      balancing, as they do not cause considerable imbalance.
      
      * When the heavy interrupt sources are balanced, they are not moved
      around. This also helps in keeping the CPU caches warm.
      
      * It has been made HT aware. While distributing the load, the load
      on a processor package to which the logical CPUs belong to is also
      considered.
      
      * In the situations of few (lesser than num_cpus) heavy interrupt
      sources, it is not possible to balance them evenly. In such case
      the existing code has been reused to move the interrupts. The
      randomness from the original code has been removed.
      
      * The time interval for redistribution has been made flexible. It
      varies as the system interrupt load changes.
      
      * A new kernel_thread is introduced to do the load balancing
      calculations for all the interrupt sources. It keeps the balanace_maps
      ready for interrupt handlers, keeping the overhead in the interrupt
      handling to minimum.
      
      * It allows the disabling of the IRQ distribution from the boot loader
      command line, if anybody wants to do it for any reason.
      
      * The algorithm also takes into account the static binding of
      interrupts to CPUs that user imposes from the
      /proc/irq/{n}/smp_affinity interface.
      
      
      Throughput numbers with the netperf setup for the new implementation:
      
      Current kernel IRQ balance implementation: 50.02K transactions/sec
      The new IRQ balance implementation: 56.01K transactions/sec
       ---------------------
        The performance improvement on P4 Xeon of 11.9% is observed.
      
      The new IRQ balance implementation also shows little performance
      improvement on P6 (Pentium II, III) systems.
      
      On a P6 system the netperf throughput numbers are:
      Current kernel IRQ balance implementation: 36.96K transactions/sec
      The new IRQ balance implementation: 37.65K transactions/sec
       ---------------------
      Here the performance improvement on P6 system of about 2% is observed.
      
      
       ---------------------
      
      Andrew Theurer <habanero@us.ibm.com> did some testing of this patch on a quad
      P4:
      
      
      I got a chance to run the NetBench benchmark with your patch on 2.5.54-mjb2
      kernel.  NetBench measures SMB/CIFS performance by using several SMB
      clients  (in this case 44 Windows 2000 systems), sending SMB requests to a
      Linux  server running Samba 2.2.3a+sendfile.  Result is in throughput,
      Mbps.   Generally the network traffic on the server is 60% recv, 40% tx.
      
      I believe we have very similar systems.  Mine is a 4 x 1.6 GHz, 1 MB L3 P4
      Xeon with 4 GB DDR memory (3.2 GB/sec I believe).  The chipset is "Summit".
       I also have more than one Intel e1000 adapters.
      
      I decided to run a few configurations, first with just one adapter, with
      and  without HT support in the kernel (acpi=off), then add another adapter
      and  test again with/without HT.
      
      Here are the results:
      
      4P, no HT, 1 x e1000, no kirq:	1214 Mbps, 4% idle
      4P, no HT, 1 x e1000, kirq:		1223 Mbps, 4% idle,		+0.74%
      
      I suppose we didn't see much of an improvement here because we never run
      into  the situation where more than one interrupt with a high rate is
      routed to a  single CPU on irq_balance.
      
      4P, HT, 1 x e1000, no kirq:	1214 Mbps, 25% idle
      4P, HT, 1 x e1000, kirq:	1220 Mbps, 30% idle,			+0.49%
      
      Again, not much of a difference just yet, but lots of idle time.  We may
      have  reached the limit at which one logical CPU can process interrupts for
      an  e1000 adapter.  There are other things I can probably do to help this,
      like  int delay, and NAPI, which I will get to eventually.
      
      4P, HT, 2 x e1000, no kirq:	1269 Mbps, 23% idle
      4P, HT, 2 x e1000, kirq:	1329 Mbps, 18% idle			+4.7%
      
      OK, almost 5% better!  Probably has to do with a couple of things; the fact
      that your code does not route two different interrupts to the same
      core/different logical cpus (quite obvious by looking at /proc/interrupts),
      and that more than one interrupt does not go to the same cpu if possible.
      I  suspect irq_balance did some of those [bad] things some of the time, and
      we  observed a bottleneck in int processing that was lower than with kirq.
      
      I don't think all of the idle time is because of a int processing
      bottleneck.   I'm just not sure what it is yet :)  Hopefully something will
      become obvious  to me...
      
      Overall I like the way it works, and I believe it can be tweaked to work
      with  NUMA when necessary.  I hope to have access to a specweb system on a
      NUMA box  soon, so we can verify that.
      08f16f8f
    • Andrew Morton's avatar
      [PATCH] Updated Documentation/kernel-parameters.txt · 7260b084
      Andrew Morton authored
      Patch from Petr Baudis <pasky@ucw.cz>
      
      this patch (against 2.5.59) updates Documentation/kernel-parameters.txt to
      the (more-or-less; I certainly missed some parameters) current state of
      kernel.  Note also that I will probably send up another update after few
      further kernel releases..
      7260b084
  21. 26 Nov, 2002 1 commit
    • Andrew Morton's avatar
      [PATCH] Updated Documentation/kernel-parameters.txt · 10414c6d
      Andrew Morton authored
      Patch from Petr Baudis <pasky@ucw.cz>
      
      This patch (against 2.5.49) updates Documentation/kernel-parameters.txt
      to the current state of kernel.  It was somehow abadonded lately, so I
      did my best, but it's possible that I still missed some of the options
      - thus, if you will notice your favourite boot option missing there,
      please speak up.  Note also that I will probably send up another update
      after few further kernel releases..
      
      Also, I attempted to introduce some uniform format to the entries, I
      added the format description where I was able to find it out and
      decypher it, and I also added gross amount of external links to the
      headers of the source files or to the README-like files, where the
      options are described into more degree.  This way, hopefully this file
      has a chance to be actually usable for the users ;-).
      
      There are almost certainly some entries which I missed, it was really a
      huge number and the main reason is that some of the boot options don't
      use the __setup macro, which I grep'd for.
      
      I hope the patch is ok, there should be no problems with it. Please apply.
      
      Note that this is the fourth submission of the patch - I took the
      opportunity and updated the patch from 2.5.48 to 2.5.49.  AFAIK mutt
      shouldn't mangle the patch in any way, so it should apply cleanly to
      your tree, Linus.
      10414c6d
  22. 25 Nov, 2002 1 commit
  23. 15 Oct, 2002 1 commit
  24. 08 Oct, 2002 1 commit
  25. 29 May, 2002 1 commit
    • Pavel Machek's avatar
      [PATCH] swsusp: cleanup · d72fb463
      Pavel Machek authored
       - use list_for_each in head_of_free_region
       - cleanups from 2.4
       - fix for usb
       - kill broken queueing
      d72fb463
  26. 03 Apr, 2002 1 commit
  27. 12 Mar, 2002 1 commit
    • John Clemens's avatar
      [PATCH] pci=usepirqmask option. · 6e8f7982
      John Clemens authored
      Last week I sent you a patch adding a config option to honor the pirq mask
      in the PCI routing table.  On your suggestion, Cory Bell made it a command
      line option using the pci= interface and we both agree with you, it's
      -much- cleaner this way.
      
      Patch against 2.5.6 (Cory's submitting for 2.4, I've tested and submitting
      towards 2.5).  All credit goes to Cory Bell, with only minor input and
      testing from myself.
      6e8f7982
  28. 05 Feb, 2002 5 commits
    • Linus Torvalds's avatar
      v2.5.2.2 -> v2.5.2.3 · 463727d1
      Linus Torvalds authored
      - Al Viro: VFS inode allocation moved down to filesystem, trim inodes
      - Greg KH: USB update, hotplug documentation
      - Kai Germaschewski: ISDN update
      - Ingo Molnar: scheduler tweaking ("J2")
      - Arnaldo: emu10k kdev_t updates
      - Ben Collins: firewire updates
      - Björn Wesen: cris arch update
      - Hal Duston: ps2esdi driver bio/kdev_t fixes
      - Jean Tourrilhes: move wireless drivers into drivers/net/wireless,
      update wireless API #1
      - Richard Gooch: devfs race fix
      - OGAWA Hirofumi: FATFS update
      463727d1
    • Linus Torvalds's avatar
      v2.4.5.3 -> v2.4.5.4 · 7a9a18cf
      Linus Torvalds authored
        - Chris Mason: ReiserFS pre-allocation locking bugfix
        - David Miller: fix bitops users (requires "long" alignment)
        - Andrey Savochkin: file locking failure case SMP lock fix
        - Urban Widmark: smbfs update (avoid unnecessary flushing, make NetApp
        work)
        - Andrew Grover: ACPI update
        - Jeff Garzik: network driver updates
        - Maciej Rozycki: IO-APIC level trigger problem workaround
        - Rusty Russell: ipt_unclean fix
        - Richard Gooch: devfs update
      7a9a18cf
    • Linus Torvalds's avatar
      v2.4.3.4 -> v2.4.3.5 · 9102e0eb
      Linus Torvalds authored
        - Mike Phillips: olympic driver update
        - Alan Cox: continued resyncing (lots of small stuff, big NTFS merge from Anton)
        - Martin Dalecki: cleanup (remove unused and unnecessary get_hardblocksize)
        - Chris Mason: fix potential reiserfs journal overflow
        - Jeff Garzik: network driver updates
        - David Miller: sparc fixes, some network cleanups
      9102e0eb
    • Linus Torvalds's avatar
      v2.4.2 -> v2.4.2.1 · c37b3aca
      Linus Torvalds authored
        - Chris Mason: reiserfs, another null bytes bug
        - Andrea Arkangeli: make SMP Athlon build
        - Alexander Zarochentcev: reiserfs directory fsync SMP locking fix
        - Jeff Garzik: PCI network driver updates
        - Alan Cox: continue merging
        - Ingo Molnar: fix RAID AUTORUN ioctl, scheduling improvements
      c37b3aca
    • Linus Torvalds's avatar
      Import changeset · 7a2deb32
      Linus Torvalds authored
      7a2deb32