1. 23 Sep, 2002 27 commits
    • Greg Kroah-Hartman's avatar
      Merge kroah.com:/home/greg/linux/BK/bleeding_edge-2.5 · 7fcc2c87
      Greg Kroah-Hartman authored
      into kroah.com:/home/greg/linux/BK/gregkh-2.5
      7fcc2c87
    • Adams IT Services's avatar
      [PATCH] USBLCD updates · 9c5e6f5a
      Adams IT Services authored
      -increased timeout value because some people reported problems
      -(important!) Vender ID has changed from 0x1212 to 0x10D2 , my official
        assigned one.
      -added usblcd driver to configure.help
      9c5e6f5a
    • Stuart MacDonald's avatar
      [PATCH] usb whiteheat driver update · 97338442
      Stuart MacDonald authored
      Update to full working driver status. Latest firmware 4.06 too. Driver
      now officially supported.
      97338442
    • Greg Kroah-Hartman's avatar
      [PATCH] USB: made port_softint global for other usb-serial drivers to use. · e185597b
      Greg Kroah-Hartman authored
      Based off of a patch from Stuart MacDonald <stuartm@connecttech.com>
      e185597b
    • Stuart MacDonald's avatar
      [PATCH] USB: clean up the error logic for open() in the usb-serial driver · 9a50ad7f
      Stuart MacDonald authored
      This cleans up the error path in the open() call to make a bit more
      sense.
      9a50ad7f
    • Greg Kroah-Hartman's avatar
      [PATCH] USB: fix for ezusb firmware download · 20e3be5f
      Greg Kroah-Hartman authored
      This fixes a stupid error in the timeout value when downloading firmware
      to a device.  The WhiteHEAT device now works properly with this patch.
      20e3be5f
    • Alan Stern's avatar
      [PATCH] usb-storage: fix return codes... · 0d80c6f5
      Alan Stern authored
      Like the header says, this patch fixes up the various Transfer- and
      Transport-level return codes.  There were a lot of places in the various
      subdrivers that were not particularly careful about distinguishing the
      two; it would help if the people currently maintaining those drivers could
      take a look at my changes to make sure I haven't screwed anything up.
      
      # Converted US_BULK_TRANSFER_xxx to USB_STOR_XFER_xxx, to make it more
      # easily distinguishable from USB_STOR_TRANSPORT_xxx.  (Also, in the
      # future these codes may apply to control transfers as well as to bulk
      # transfers.)
      #
      # Changed USB_STOR_XFER_FAILED to USB_STOR_XFER_ERROR, since it implies
      # a transport error rather than a transport failure.
      #
      # Added a USB_STOR_XFER_STALLED code, to indicate a transfer that was
      # terminated by an endpoint stall.
      
      This patch is in preparation for one in which usb_stor_transfer_partial()
      and usb_stor_transfer() are replaced by usb_stor_bulk_transfer_buf() and
      usb_stor_bulk_transfer_srb() respectively, with slightly different
      argument lists.  Ultimately the subdrivers will be able to use these
      routines in place of the slightly specialized versions they have now and
      in place of the ones in raw_bulk.c.
      0d80c6f5
    • Luc Van Oostenryck's avatar
      [PATCH] #include <linux/version.h> missing in drivers/usb/host/ohci-hcd.c · 7e5b54d4
      Luc Van Oostenryck authored
      compile fails with the following message:
      
      	> In file included from ohci-hcd.c:136:
      	> ohci-dbg.c:318: parse error
      	> make[3]: *** [ohci-hcd.o] Error 1
      
      due to a missing #include <linux/version.h>
      
      Here is a trivial patch for this.
      7e5b54d4
    • David Brownell's avatar
      [PATCH] USB shutdown oopser · 817c0217
      David Brownell authored
      is it guarenteed that callers have zero'd out the device
      before this is invoked?  Else the following is necessary to
      prevent potential OOPS's derefencing interface->dev.driver in
      the generic device layer.
      817c0217
    • David Brownell's avatar
      [PATCH] ehci-hcd: update · df42f7cf
      David Brownell authored
      Here's an EHCI update, I'll send separate patches to sync 2.4 with
      this version.  Changes in this version include:
      
        - An earlier locking update would give trouble on SPARC, where
          irqsave "flags" aren't flags.  This resolves that issue by
          adding a module parameter to limit work done with irqs off.
          (Some net drivers do the same thing.)
      
        - Optionally (now #ifdef DEBUG) collects some statistics on IRQs
          and URBs.  There are more IAA interrupts than I want to see,
          during extended usb-storage loading.
      
        - Adds a commented-out workaround for a problem I've seen on one
          VT8235.  Seems likely an issue with this specific motherboard;
          another tester hasn't reported such issues.
      
        - Includes the jiffies time_after() patch from Tim Schmielau.
      
        - Minor tweaks to the hcd portability (get rid of another #if).
      
        - Minor doc/diagnostic/... updates
      df42f7cf
    • David Brownell's avatar
      [PATCH] ohci-hcd, queue fault recovery + rm DEBUG · 65e2da7e
      David Brownell authored
      This USB patch updates the OHCI driver:
      
        - converts to relying on td_list shadowing the hardware's
          schedule; only collecting the donelist needs dma_to_td(),
          and td list handling works much like EHCI or UHCI.
      
        - leaves faulted endpoint queues (bulk/intr) disabled until
          the relevant drivers had a chance to clean up.
      
        - fixes minor bugs (unreported) in the affected code:
            * byteswap problem when unlinking urbs ... symptom would
              be data toggle confusion (since 2.4.2x) on big-endian cpus
            * latent bug if folk unlinked queue in LIFO order, not FIFO
      
        - removes unnecessary debug code; mostly de-BUG()ged
      
      The interesting fix is the "leave queues halted" one.  As
      discussed on email a while back, this HCD fault handling
      policy (also followed by EHCI) is sufficient to let device
      drivers implement the two key fault handling policies that
      seem to be necessary:
      
          (a) Datagram style, where issues on one I/O won't affect
              the next unless the device halted the endpoint.  The
              device driver can ignore most errors other than -EPIPE.
      
          (b) Stream style, where for example it'd be wrong to ever
              let block N+1 overwrite block N on the disk.  Once
              the first URB fails, the rest would just be unlinked
              in the completion handler.
      
      As a consequence of using the td_list, you can now see urb
      queuing in action in the driverfs 'async' file.  At least, if
      you look at the right time, or use drivers (networking, etc)
      that queue (bulk) reads for a long time.
      65e2da7e
    • Ingo Molnar's avatar
      [PATCH] de-xchg fork.c · 94eda096
      Ingo Molnar authored
      This fixes all xchg()'s and a preemption bug.
      94eda096
    • Ingo Molnar's avatar
      [PATCH] pidhash cleanups, tgid-2.5.38-F3 · 817fdd72
      Ingo Molnar authored
      This does the following things:
      
       - removes the ->thread_group list and uses a new PIDTYPE_TGID pid class
         to handle thread groups. This cleans up lots of code in signal.c and
         elsewhere.
      
       - fixes sys_execve() if a non-leader thread calls it. (2.5.38 crashed in
         this case.)
      
       - renames list_for_each_noprefetch to __list_for_each.
      
       - cleans up delayed-leader parent notification.
      
       - introduces link_pid() to optimize PIDTYPE_TGID installation in the
         thread-group case.
      
      I've tested the patch with a number of threaded and non-threaded
      workloads, and it works just fine. Compiles & boots on UP and SMP x86.
      
      The session/pgrp bugs reported to lkml are probably still open, they are
      the next on my todo - now that we have a clean pidhash architecture they
      should be easier to fix.
      817fdd72
    • Linus Torvalds's avatar
      Terminate a failed IO properly · 76417366
      Linus Torvalds authored
      76417366
    • Linus Torvalds's avatar
      Merge http://linux-isdn.bkbits.net/linux-2.5.isdn · 46796862
      Linus Torvalds authored
      into home.transmeta.com:/home/torvalds/v2.5/linux
      46796862
    • Kai Germaschewski's avatar
      ISDN: Fix build when CONFIG_ISDN_TTY_FAX is not set · 767bf8a2
      Kai Germaschewski authored
      T30_s * is part of a union, so the typedef needs to exist even when
      CONFIG_ISDN_TTY_FAX is not set.
      767bf8a2
    • Linus Torvalds's avatar
      Merge http://linux-isdn.bkbits.net/linux-2.5.make · c06fd892
      Linus Torvalds authored
      into home.transmeta.com:/home/torvalds/v2.5/linux
      c06fd892
    • Kai Germaschewski's avatar
      kbuild: Convert missed L_TARGET references · a8c7db20
      Kai Germaschewski authored
      When converting all L_TARGETs to lib.a, I missed these instances.
      a8c7db20
    • Peter Rival's avatar
      [PATCH] Compile fixes for alpha arch · 41447041
      Peter Rival authored
      Update alpha port to work with new nanosecond xtime, and the in_atomic()
      requirements.
      41447041
    • Linus Torvalds's avatar
      Merge bk://thebsh.namesys.com/bk/reiser3-linux-2.5 · 59e8b32c
      Linus Torvalds authored
      into home.transmeta.com:/home/torvalds/v2.5/linux
      59e8b32c
    • Mikael Pettersson's avatar
      [PATCH] fix UP_APIC linkage problem in 2.5.3[78] · cb45d949
      Mikael Pettersson authored
      The problem is that the local APIC code references stuff in
      mpparse, but 2.5.37 changed arch/i386/kernel/Makefile to only
      compile mpparse for SMP.
      
      This patch works around this by enforcing CONFIG_X86_MPPARSE
      for all LOCAL_APIC-enabled configs.
      cb45d949
    • Jens Axboe's avatar
      [PATCH] bio_get_nr_vecs · 63b9d36d
      Jens Axboe authored
      Add bio_get_nr_vecs(). It returns an approximate number of pages that
      can be added to a block device. It's just a ballpark number, but I think
      this is quite fine for the type of thing it is needed for: mpage etc
      need to know an approx size of a bio that they need to allocate. It
      would be silly to continously allocate 64-page sized bio_vec entries, if
      the target cannot do more than 8, for example.
      63b9d36d
    • Jens Axboe's avatar
      [PATCH] pdc4030 · 58c1b542
      Jens Axboe authored
      make pdc4030 work
      58c1b542
    • Jens Axboe's avatar
      [PATCH] trm compile · 6c99eec3
      Jens Axboe authored
      Bad merge from 2.4.20-pre-ac, ide_build_dmatable() does not need data
      direction argument in 2.5 (it's implicit in the request)
      6c99eec3
    • Tim Schmielau's avatar
      76dc17b4
    • Ivan Kokshaysky's avatar
      [PATCH] Re: 2.5.36 IDE fixes · 7d663f71
      Ivan Kokshaysky authored
      I'm terribly sorry - I've sent you the wrong diff, it was
      some intermediate variant. Actually it added extra breakage to
      ide_hwif_configure().
      
      Desired behavior was:
      
      if ctl == base == 0, the device is in "true legacy" mode (as per PCI
      spec); use values from the base address registers otherwise.
      7d663f71
    • Jens Axboe's avatar
      [PATCH] more bio updates · ef869838
      Jens Axboe authored
      cleanup end_that_request_first() end_io handling, and fix bug where
      partial completes didn't get accounted right wrt blk_recalc_rq_sectors()
      ef869838
  2. 22 Sep, 2002 13 commits
    • Kai Germaschewski's avatar
      Merge zephyr:src/kernel/v2.5/linux-2.5.isdn · 53fcb937
      Kai Germaschewski authored
      into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn
      53fcb937
    • Kai Germaschewski's avatar
      ISDN: Lock list of phone numbers appropriately · cd2d00c6
      Kai Germaschewski authored
      It was (only partially) protected by cli() before, which we want to
      get rid of.
      cd2d00c6
    • Kai Germaschewski's avatar
      ISDN: Use <linux/list.h> for list of phone numbers · 51430a3c
      Kai Germaschewski authored
      Simplifies the code which was previously using an open coded
      singly linked list.
      
      Also, deleting a phone number during dial-out could easily oops
      the kernel before this patch.
      51430a3c
    • Kai Germaschewski's avatar
      ISDN: ISDN_GLOBAL_STOPPED cleanup · 7e22da6a
      Kai Germaschewski authored
      ISDN_GLOBAL_STOPPED is a way to globally stop the system
      from dialing out / accepting incoming calls. Instead of
      spreading checks all over the place, just catch dial
      commands / incoming call indications in one place.
      
      Also, kill isdn_net_phone typedef and clean up affected code.
      7e22da6a
    • Kai Germaschewski's avatar
      ISDN: Kill isdn_net_autohup() · 2a002db2
      Kai Germaschewski authored
      It's not used for the timeout controlled hangup anymore, only to
      hangup depending on the dialmode, which we handle directly now.
      2a002db2
    • Kai Germaschewski's avatar
      ISDN: PPP cleanups · 79deb1f1
      Kai Germaschewski authored
      o PPP_IPX is defined in a header these days
      o isdn_net_hangup takes an isdn_net_local *, simplifying
        code a bit.
      79deb1f1
    • Kai Germaschewski's avatar
      Merge tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.isdn · 967ee5ae
      Kai Germaschewski authored
      into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.make
      967ee5ae
    • Linus Torvalds's avatar
      Merge master.kernel.org:/home/davem/BK/sparc-2.5 · f20bf018
      Linus Torvalds authored
      into home.transmeta.com:/home/torvalds/v2.5/linux
      f20bf018
    • Linus Torvalds's avatar
      Merge master.kernel.org:/home/davem/BK/net-2.5 · e7144e64
      Linus Torvalds authored
      into home.transmeta.com:/home/torvalds/v2.5/linux
      e7144e64
    • Andrew Morton's avatar
      [PATCH] low-latency page reclaim · 407ee6c8
      Andrew Morton authored
      Convert the VM to not wait on other people's dirty data.
      
       - If we find a dirty page and its queue is not congested, do some writeback.
      
       - If we find a dirty page and its queue _is_ congested then just
         refile the page.
      
       - If we find a PageWriteback page then just refile the page.
      
       - There is additional throttling for write(2) callers.  Within
         generic_file_write(), record their backing queue in ->current.
         Within page reclaim, if this tasks encounters a page which is dirty
         or under writeback onthis queue, block on it.  This gives some more
         writer throttling and reduces the page refiling frequency.
      
      It's somewhat CPU expensive - under really heavy load we only get a 50%
      reclaim rate in pages coming off the tail of the LRU.  This can be
      fixed by splitting the inactive list into reclaimable and
      non-reclaimable lists.  But the CPU load isn't too bad, and latency is
      much, much more important in these situations.
      
      Example: with `mem=512m', running 4 instances of `dbench 100', 2.5.34
      took 35 minutes to compile a kernel.  With this patch, it took three
      minutes, 45 seconds.
      
      I haven't done swapcache or MAP_SHARED pages yet.  If there's tons of
      dirty swapcache or mmap data around we still stall heavily in page
      reclaim.  That's less important.
      
      This patch also has a tweak for swapless machines: don't even bother
      bringing anon pages onto the inactive list if there is no swap online.
      407ee6c8
    • Andrew Morton's avatar
      [PATCH] use the congestion APIs in pdflush · c9b22619
      Andrew Morton authored
      The key concept here is that pdflush does not block on request queues
      any more.  Instead, it circulates across the queues, keeping any
      non-congested queues full of write data.  When all queues are full,
      pdflush takes a nap, to be woken when *any* queue exits write
      congestion.
      
      This code can keep sixty spindles saturated - we've never been able to
      do that before.
      
       - Add the `nonblocking' flag to struct writeback_control, and teach
         the writeback paths to honour it.
      
       - Add the `encountered_congestion' flag to struct writeback_control
         and teach the writeback paths to set it.
      
      So as soon as a mapping's backing_dev_info indicates that it is getting
      congested, bale out of writeback.  And don't even start writeback
      against filesystems whose queues are congested.
      
       - Convert pdflush's background_writeback() function to use
         nonblocking writeback.
      
      This way, a single pdflush thread will circulate around all the
      dirty queues, keeping them filled.
      
       - Convert the pdlfush `kupdate' function to do the same thing.
      
      This solves the problem of pdflush thread pool exhaustion.
      
      It solves the problem of pdflush startup latency.
      
      It solves the (minor) problem wherein `kupdate' writeback only writes
      back a single disk at a time (it was getting blocked on each queue in
      turn).
      
      It probably means that we only ever need a single pdflush thread.
      c9b22619
    • Andrew Morton's avatar
      [PATCH] use the queue congestion API in ext2_preread_inode() · f3332384
      Andrew Morton authored
      Use the new queue congestion detector in ext2_preread_inode().  Don't
      try the speculative read if the read queue is congested.
      
      Also, don't try it if the disk is write-congested.  Presumably it is
      more important to get the dirty memory cleaned out.
      f3332384
    • Andrew Morton's avatar
      [PATCH] infrastructure for monitoring queue congestion state · 4cef1b04
      Andrew Morton authored
      The patch provides a means for the VM to be able to determine whether a
      request queue is in a "congested" state.  If it is congested, then a
      write to (or read from) the queue may cause blockage in
      get_request_wait().
      
      So the VM can do:
      
      	if (!bdi_write_congested(page->mapping->backing_dev_info))
      		writepage(page);
      
      This is not exact.  The code assumes that if the request queue still
      has 1/4 of its capacity (queue_nr_requests) available then a request
      will be non-blocking.  There is a small chance that another CPU could
      zoom in and consume those requests.  But on the rare occasions where
      that may happen the result will mereley be some unexpected latency -
      it's not worth doing anything elaborate to prevent this.
      
      The patch decreases the size of `batch_requests'.  batch_requests is
      positively harmful - when a "heavy" writer and a "light" writer are
      both writing to the same queue, batch_requests provides a means for the
      heavy writer to massively stall the light writer.  Instead of waiting
      for one or two requests to come free, the light writer has to wait for
      32 requests to complete.
      
      Plus batch_requests generally makes things harder to tune, understand
      and predict.  I wanted to kill it altogether, but Jens says that it is
      important for some hardware - it allows decent size requests to be
      submitted.
      
      The VM changes which go along with this code cause batch_requests to be
      not so painful anyway - the only processes which sleep in
      get_request_wait() are the ones which we elect, by design, to wait in
      there - typically heavy writers.
      
      
      The patch changes the meaning of `queue_nr_requests'.  It used to mean
      "total number of requests per queue".  Half of these are for reads, and
      half are for writes.  This always confused the heck out of me, and the
      code needs to divide queue_nr_requests by two all over the place.
      
      So queue_nr_requests now means "the number of write requests per queue"
      and "the number of read requests per queue".  ie: I halved it.
      
      Also, queue_nr_requests was converted to static scope.  Nothing else
      uses it.
      
      
      The accuracy of bdi_read_congested() and bdi_write_congested() depends
      upon the accuracy of mapping->backing_dev_info.  With complex block
      stacking arrangements it is possible that ->backing_dev_info is
      pointing at the wrong queue.  I don't know.
      
      But the cost of getting this wrong is merely latency, and if it is a
      problem we can fix it up in the block layer, by getting stacking
      devices to communicate their congestion state upwards in some manner.
      4cef1b04