public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Douglas Gilbert <dougg@torque.net>
To: linux-scsi@vger.kernel.org, davej@codemonkey.org.uk
Subject: dismal scsi report in '2.5 - what to expect'
Date: Wed, 16 Apr 2003 10:59:48 +1000	[thread overview]
Message-ID: <3E9CAB04.5040004@torque.net> (raw)

Dave Jones recently sent version 0.33 of his
'2.5 - what to expect' document to the linux kernel list:
http://marc.theaimsgroup.com/?l=linux-kernel&m=105034885830405&w=2

The SCSI report while probably correct lacked any positive
"spin":

 > SCSI.
 > ~~~~~
 > - Various SCSI drivers still need work, and don't even
 >   compile.
 > - Various drivers currently lack error handling.
 >   These drivers will cause warnings during compilation
 >   due to missing abort: & reset: functions.
 > - Note, that some drivers have had these members removed,
 >   but still lack error handling. Those noticed so far are
 >   ncr53c8xxx, sym53c8xx and inia100

The IDE report was arguably as bad though the "IO subsystem"
did fair better.

So what positive can we say about the SCSI subsystem in 2.5
(compared to the 2.4 series)?

Some suggestions:
- large dev_t support allowing thousands of disks to be
   supported (was 128 or 256 in the 2.4 series)
- major code cleanup, initially to support the block layer
   (bio) improvements have led to:
    - better throughput (?) [less double handling of data]
    - per HBA locks (there was a single io_request_lock in
      the 2.4 series)
    - more flexible interface to HBA drivers
    - better hotplug support, especially for USB mass storage
      and ieee1394 sbp2 devices [well it's work_in_progress]
- improved error processing and scanning code (support for
   large, sparse lun spaces)
- lots of scsi driver "innards" (quoting Dave Jones) available
   via sysfs

Comments, additions, deletions?

Doug Gilbert


                 reply	other threads:[~2003-04-16  0:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3E9CAB04.5040004@torque.net \
    --to=dougg@torque.net \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox