1. 10 Sep, 2005 1 commit
  2. 09 Sep, 2005 2 commits
  3. 08 Sep, 2005 5 commits
    • Alan Stern's avatar
      [PATCH] USB: URB_ASYNC_UNLINK flag removed from the kernel · b375a049
      Alan Stern authored
      29 July 2005, Cambridge, MA:
      This afternoon Alan Stern submitted a patch to remove the URB_ASYNC_UNLINK
      flag from the Linux kernel.  Mr. Stern explained, "This flag is a relic
      from an earlier, less-well-designed system.  For over a year it hasn't
      been used for anything other than printing warning messages."
      An anonymous spokesman for the Linux kernel development community
      commented, "This is exactly the sort of thing we see happening all the
      time.  As the kernel evolves, support for old techniques and old code can
      be jettisoned and replaced by newer, better approaches.  Proprietary
      operating systems do not have the freedom or flexibility to change so
      Mr. Stern, a staff member at Harvard University's Rowland Institute who
      works on Linux only as a hobby, noted that the patch (labelled as548) did
      not update two files, keyspan.c and option.c, in the USB drivers' "serial"
      subdirectory.  "Those files need more extensive changes," he remarked.
      "They examine the status field of several URBs at times when they're not
      supposed to.  That will need to be fixed before the URB_ASYNC_UNLINK flag
      is removed."
      Greg Kroah-Hartman, the kernel maintainer responsible for overseeing all
      of Linux's USB drivers, did not respond to our inquiries or return our
      calls.  His only comment was "Applied, thanks."
      Signed-off-by: default avatarAlan Stern <stern@rowland.harvard.edu>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    • Pete Zaitcev's avatar
      [PATCH] USB: ub 4: Zaitcev's quasi-S/G · a1cf96ef
      Pete Zaitcev authored
      Back out Axboe-style quasi-S/G and replace it with one command and
      repeated URBs. This is similar to what usb-storage does, only instead
      of a few URBs allocated together, one URB is reused.
      Jens's idea was very nice, but it collapsed when I had to support
      packet commads for CD burning. I cannot issue two or more packet
      commands where application expected only one.
      However, burning does not work completely yet. The cdrecord starts,
      recognizes the device, then aborts without writing a TOC.
      Signed-off-by: default avatarPete Zaitcev <zaitcev@yahoo.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    • Pete Zaitcev's avatar
      [PATCH] USB: ub 3/3: death to ub_bd_rq_fn_1 · 6c1eb8c1
      Pete Zaitcev authored
      When Al Viro saw the ub.c, he observed that it was a proof positive of
      Linus not reading patches anymore: names like fo_ob_ar_ba_2 used to
      cause serious fireworks. In my defence, any good scheme can be pushed
      to the realm of absurd if pushed far enough.
      Signed-off-by: default avatarPete Zaitcev <zaitcev@yahoo.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    • Pete Zaitcev's avatar
      [PATCH] USB: ub 2/3: Fold one line · 07d4fd25
      Pete Zaitcev authored
      Evidently, Yani Ioannou's display is wider than mine.
      Signed-off-by: default avatarPete Zaitcev <zaitcev@yahoo.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
    • Pete Zaitcev's avatar
      [PATCH] USB: ub 1/3: Axboe's quasi-S/G · ba6abf13
      Pete Zaitcev authored
      This the quasi-S/G patch for ub as suggested by Jens Axboe at OLS and
      implemented that night before 4 a.m. Surprisingly, it worked right away...
      Alas, I had to skip some OLS partying, but it was for the good cause.
      Now the speed of ub is quite acceptable even on partitions with small
      block size.
      The ub does not really support S/G. Instead, it just tells the block
      layer that it does. Then, most of the time, the block layer merges
      requests and passes single-segmnent requests down to ub; everything
      works as before. Very rarely ub gets an unmerged S/G request. In such
      case, it issues several commands to the device.
      I added a small array of counters to monitor the merging (sg_stat).
      This may be dropped later.
      Signed-off-by: default avatarPete Zaitcev <zaitcev@yahoo.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@suse.de>
  4. 07 Sep, 2005 6 commits
  5. 05 Sep, 2005 3 commits
  6. 01 Sep, 2005 1 commit
  7. 29 Aug, 2005 2 commits
  8. 24 Aug, 2005 1 commit
    • Jens Axboe's avatar
      [PATCH] cfq-iosched.c: minor fixes · 9c2c38a1
      Jens Axboe authored
      One critical fix and two minor fixes for 2.6.13-rc7:
      - Max depth must currently be 2 to allow barriers to function on SCSI
      - Prefer sync request over async in choosing the next request
      - Never allow async request to preempt or disturb the "anticipation" for
        a single cfq process context. This is as-designed, the code right now
        is buggy in that area.
      Signed-off-by: default avatarJens Axboe <axboe@suse.de>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  9. 10 Aug, 2005 1 commit
  10. 05 Aug, 2005 1 commit
    • Tejun Heo's avatar
      [PATCH] blk: fix tag shrinking (revive real_max_size) · ba025082
      Tejun Heo authored
      My patch in commit fa72b903 incorrectly
      removed blk_queue_tag->real_max_depth.
      The original resize implementation was incorrect in the following
       * actual allocation size of tag_index was shorter than real_max_size,
         but assumed to be of the same size, possibly causing memory access
         beyond the allocated area.
       * bits in tag_map between max_deptn and real_max_depth were
         initialized to 1's, making the tags permanently reserved.
      In an attempt to fix above two bugs, I had removed allocation optimization
      in init_tag_map and real_max_size.  Tag map/index were allocated and freed
      immediately during resize.
      Unfortunately, I wasn't considering that tag map/index can be resized
      dynamically with tags beyond new_depth active.  This led to accessing
      freed area after shrinking tags and led to the following bug reporting
      thread on linux-scsi.
      To fix the problem, I've revived real_max_depth without allocation
      optimization in init_tag_map, and Andrew Vasquez confirmed that the
      problem was fixed.  As Jens is not going to be available for a week, he
      asked me to make sure that this patch reaches you.
      Also, a comment was added to make sure that real_max_size is needed for
      dynamic shrinking.
      Signed-off-by: default avatarTejun Heo <htejun@gmail.com>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  11. 02 Aug, 2005 1 commit
  12. 28 Jul, 2005 1 commit
    • Mike Miller's avatar
      [PATCH] cciss per disk queue · ad2b9312
      Mike Miller authored
      This patch adds per disk queue functionality to cciss.  Sometime back I
      submitted a patch but it looks like only part of what I needed.  In the 2.6
      kernel if we have more than one logical volume the driver will Oops during
      rmmod.  It seems all of the queues actually point back to the same queue.
      So after deleting the first volume you hit a null pointer on the second
      This has been tested in our labs.  There is no difference in performance,
      it just fixes the Oops.
      Signed-off-by: default avatarMike Miller <mike.miller@hp.com>
      Cc: Jens Axboe <axboe@suse.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
  13. 27 Jul, 2005 3 commits
  14. 29 Jun, 2005 1 commit
  15. 28 Jun, 2005 5 commits
  16. 27 Jun, 2005 6 commits