From: Jeff Garzik <jgarzik@pobox.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: SCSI in a post 2.6.0 world
Date: Thu, 18 Dec 2003 10:31:28 -0500 [thread overview]
Message-ID: <20031218153128.GA5389@gtf.org> (raw)
In-Reply-To: <1071758885.2430.37.camel@mulgrave>
On Thu, Dec 18, 2003 at 09:48:05AM -0500, James Bottomley wrote:
> With the announcement of 2.6.0, I've dusted off the scsi-misc-2.7 tree
> at
>
> bk://linux-scsi.bkbits.net/scsi-misc-2.7
>
> I'm afraid, until the new merge criteria are announced, you can't assume
> it will contain the actual changesets that will be merged (I may need to
> take it apart and redo it), but it's a good start for people who want
> to begin ongoing SCSI development again.
FWIW, I'm going to be working in this area, for 2.7.
My plan has two main goals,
(a) move the low-level driver API "up" from SCSI, to be available to all
block drivers.
(b) consolidate "personality" code: foodisk.c will drive
PATA/SATA/SCSI/RAID/whatever disks. foocdrom.c will drive cd-roms.
footape.c will drive tapes.
The overall goal is to have all low-level block drivers at the same
level, simply utilizing subsystem-specific hooks to provide
SCSI-specific behavior.
And all this will be accomplished through evolution of existing code.
You have convinced me that SCSI doesn't need yet another rewrite ;-) so
I will be leveraging all the work that's gone into SCSI in 2.6...
Whenever you hear me mention "/dev/disk", the above is what I am
referring to.
FWIW.
Jeff
next prev parent reply other threads:[~2003-12-18 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-18 14:48 SCSI in a post 2.6.0 world James Bottomley
2003-12-18 15:31 ` Jeff Garzik [this message]
2003-12-18 15:40 ` James Bottomley
2003-12-18 15:57 ` Jeff Garzik
2003-12-18 21:22 ` Andre Hedrick
2003-12-19 3:52 ` Jeff Garzik
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=20031218153128.GA5389@gtf.org \
--to=jgarzik@pobox.com \
--cc=James.Bottomley@steeleye.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.