From: Jeff Garzik <jeff@garzik.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-ide@vger.kernel.org
Subject: Re: [RFC] Read/Write Buffer support
Date: Sat, 15 Mar 2008 21:47:56 -0400 [thread overview]
Message-ID: <47DC7C4C.4040400@garzik.org> (raw)
In-Reply-To: <20080316004609.GZ613@parisc-linux.org>
Matthew Wilcox wrote:
> On Sat, Mar 15, 2008 at 06:48:03PM -0400, Jeff Garzik wrote:
>> P.S. I encourage others to investigate making the libata SCSI simulator
>> an optional kernel module.
>>
>> Long term, a preferred solution would be to use SCSI layer for ATAPI
>> devices, and a kernel block device for ATA devices.
>
> I think that's the right method to take, though we probably still want
> to emulate the scsi ioctls.
We'll want the ATA<->SCSI simulator in its entirety as an optional
module for compatibility. People have built applications assuming they
must use SCSI (more specifically, SAT) to probe and manipulate ATA devices.
Jeff
prev parent reply other threads:[~2008-03-16 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 15:37 [RFC] Read/Write Buffer support Matthew Wilcox
2008-03-15 17:18 ` Jeff Garzik
2008-03-15 17:49 ` Matthew Wilcox
2008-03-15 22:48 ` Jeff Garzik
2008-03-15 23:09 ` Alan Cox
2008-03-16 0:46 ` Matthew Wilcox
2008-03-16 1:47 ` Jeff Garzik [this message]
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=47DC7C4C.4040400@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=matthew@wil.cx \
/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).