From: Jeff Garzik <jgarzik@pobox.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BK PATCHES] add ata scsi driver
Date: Tue, 27 May 2003 02:07:36 -0400 [thread overview]
Message-ID: <3ED300A8.4000405@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0305261306500.12186-100000@home.transmeta.com>
Linus Torvalds wrote:
> On Mon, 26 May 2003, Jeff Garzik wrote:
>
>>Correct, but precisely by saying that, you're missing something.
>
>
> You're missing _my_ point.
>
>
>>The SCSI midlayer provides infrastructure I need -- which is not
>>specific to SCSI at all.
>
>
> If it isn't specific to SCSI, then it sure as hell shouldn't BE THERE!
>
> My point is that it's _wrong_ to make non-SCSI drivers use the SCSI layer,
> because that shows that something is misdesigned.
>
> And I bet there isn't all that much left that really helps.
>
> You adding more "pseudo-SCSI" crap just _makes_things_worse. It does not
> advance anything, it regresses.
As you see from Alan's message and others, it isn't pseudo-SCSI.
Besides what he mentioned, there is Serial Attached SCSI (SAS), where a
host controller can simultaneously support SAS disks and SATA disks. So
it's either an IDE driver that does SCSI, or a SCSI driver that does
IDE, or a driver that's in both IDE and SCSI subsystems, or... ? Having
fun yet? :)
> On 27 May 2003, Alan Cox wrote:
>>> I actually think thats a positive thing. It means 2.5 drivers/scsi is
>>> now very close to being the "native queueing driver" with some
>>> additional default plugins for doing scsi scanning, scsi error recovery
>>> and a few other scsi bits.
>
> Hey, that may well be the way to go, in which case the core stuff should
> be renamed and moved off somewhere else. Leaving drivers/scsi with just
> the actual low-level SCSI drivers.
For all these reasons, I continue to maintain that starting out as a
SCSI driver, and then evolving, is the best route. The non-SCSI parts
leave drivers/scsi, as they should. The SCSI parts stay. The SCSI
mid-layer gets smaller. All the while, the driver continues to work.
Everybody wins.
Starting out as a native block driver and _then_ adding SCSI support and
native queueing and jazz does not sound even remotely like a good path
to follow.
Jeff
next prev parent reply other threads:[~2003-05-27 5:54 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-26 4:58 [BK PATCHES] add ata scsi driver Jeff Garzik
2003-05-26 5:15 ` Linus Torvalds
2003-05-26 5:30 ` Jeff Garzik
2003-05-26 5:36 ` Jeff Garzik
2003-05-26 5:42 ` Linus Torvalds
2003-05-26 6:01 ` Jeff Garzik
2003-05-26 16:56 ` Linus Torvalds
2003-05-26 17:47 ` Jeff Garzik
2003-05-26 20:09 ` Linus Torvalds
2003-05-27 0:29 ` Alan Cox
2003-05-27 6:07 ` Jeff Garzik [this message]
2003-05-27 6:30 ` Linus Torvalds
2003-05-27 6:51 ` Linus Torvalds
2003-05-27 7:29 ` Jeff Garzik
2003-05-26 5:40 ` Linus Torvalds
2003-05-26 5:53 ` Jeff Garzik
2003-05-26 6:21 ` Jeff Garzik
2003-05-26 16:57 ` Linus Torvalds
2003-05-26 17:24 ` Jens Axboe
2003-05-26 17:54 ` Jeff Garzik
2003-05-26 17:59 ` Jeff Garzik
2003-05-26 18:11 ` Jens Axboe
2003-05-27 0:22 ` Alan Cox
2003-05-27 4:15 ` Linus Torvalds
2003-05-26 10:32 ` Bartlomiej Zolnierkiewicz
2003-05-26 11:13 ` Jeff Garzik
2003-05-26 11:37 ` Bartlomiej Zolnierkiewicz
2003-05-26 5:59 ` Benjamin Herrenschmidt
2003-05-26 6:03 ` Jeff Garzik
2003-06-02 9:46 ` Andre Hedrick
2003-06-02 13:56 ` Alan Cox
2003-05-26 18:12 James Bottomley
2003-05-26 18:18 ` Jens Axboe
2003-05-26 18:47 ` James Bottomley
2003-05-26 19:07 ` Jens Axboe
2003-05-26 19:17 ` James Bottomley
2003-05-26 19:33 ` Jens Axboe
2003-05-27 12:39 ` Jens Axboe
2003-05-27 14:26 ` James Bottomley
2003-05-27 17:16 ` Jens Axboe
2003-05-27 18:09 ` James Bottomley
2003-05-27 18:21 ` Jens Axboe
2003-05-27 18:30 ` James Bottomley
2003-05-26 20:27 ` Linus Torvalds
2003-05-26 20:36 ` James Bottomley
2003-05-26 20:45 ` Linus Torvalds
2003-05-26 20:51 ` Jens Axboe
2003-05-26 20:56 ` James Bottomley
2003-05-26 20:38 ` Jens Axboe
2003-05-26 20:49 ` Linus Torvalds
2003-05-26 20:57 ` Jens Axboe
2003-05-26 21:34 ` Linus Torvalds
2003-05-26 23:58 ` Nick Piggin
2003-05-27 0:09 ` Linus Torvalds
2003-05-27 0:49 ` Nick Piggin
2003-05-27 0:16 ` Alan Cox
2003-05-27 6:54 ` Jens Axboe
2003-05-27 14:20 ` James Bottomley
2003-05-27 14:36 ` Linus Torvalds
2003-05-27 14:59 ` James Bottomley
2003-05-27 15:21 ` Jeff Garzik
2003-05-27 15:38 ` James Bottomley
2003-05-27 15:50 ` Jeff Garzik
2003-05-27 16:00 ` James Bottomley
2003-05-27 16:16 ` Jeff Garzik
2003-05-28 9:35 ` Christoph Hellwig
2003-05-28 10:50 ` Lincoln Dale
2003-05-27 19:43 ` Jens Axboe
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=3ED300A8.4000405@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).