linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	IDE/ATA development list <linux-ide@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	brking@linux.vnet.ibm.com, Mark Lord <liml@rtr.ca>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [RFC] Separating out libata out of SCSI (finally)
Date: Sat, 21 Jun 2008 08:50:38 +0900	[thread overview]
Message-ID: <485C424E.1060208@kernel.org> (raw)
In-Reply-To: <485C31FE.8050408@garzik.org>

Jeff Garzik wrote:
> 1) Make SCSI block devices themselves an allocate-able resource (I think
> that's what you meant by "placed into it's own module so both sd and a
> ULD ata driver could use it"?)
> 
> 2) Ensure that any ata_disk ULD would support the same partition limits
> and ioctl set, enough to ensure binary compatibility.
> 
> Because that's the real need -- maintaining binary compatibility with
> SCSI block devices, so major/minor, ioctl supported set, partition
> limits, and other relevant details need to remain unchanged.
> 
> The underlying software we're of course free to change...

I'm taking this approach.  I think it's better than introducing a new
block device while keeping the old one as that causes numerous userland
problems including dup devices (if they're gonna exist side-by-side) and
eventual need for conversion && breakage of old userland on newer kernels.

Thanks.

-- 
tejun

  reply	other threads:[~2008-06-20 23:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <485B2CC6.6070201@kernel.org>
2008-06-20 19:41 ` [RFC] Separating out libata out of SCSI (finally) Brian King
2008-06-20 20:28 ` James Bottomley
2008-06-20 22:41   ` Jeff Garzik
2008-06-20 23:50     ` Tejun Heo [this message]
2008-06-23 21:04     ` Greg Freemyer
2008-06-23 21:11       ` James Bottomley
2008-06-23 21:56         ` Felix Miata
2008-06-24  8:30         ` Boaz Harrosh
2008-06-24 14:42           ` James Bottomley
2008-06-24 14:58             ` Greg Freemyer
2008-06-24 15:13               ` Felix Miata
2008-06-24 14:59             ` Tejun Heo
2008-06-24 15:42               ` Felix Miata
2008-06-24 15:49                 ` Tejun Heo
2008-06-24 16:27                   ` Felix Miata
2008-06-24 16:35                     ` Tejun Heo
2008-06-24 16:54               ` Alan Cox
2008-06-20 23:47   ` Tejun Heo

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=485C424E.1060208@kernel.org \
    --to=tj@kernel.org \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=brking@linux.vnet.ibm.com \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=liml@rtr.ca \
    --cc=linux-ide@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).