From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jeff Garzik <jeff@garzik.org>, Jonathan Corbet <corbet@lwn.net>,
Boaz Harrosh <bharrosh@panasas.com>,
Zach Brown <zach.brown@oracle.com>,
Chris Mason <chris.mason@oracle.com>, Tejun Heo <tj@kernel.org>,
linux-scsi <linux-scsi@vger.kernel.org>,
Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: LSF Papers online?
Date: Tue, 14 Apr 2009 17:49:17 -0500 [thread overview]
Message-ID: <1239749357.3638.3.camel@mulgrave> (raw)
In-Reply-To: <200904150009.06539.bzolnier@gmail.com>
On Wed, 2009-04-15 at 00:09 +0200, Bartlomiej Zolnierkiewicz wrote:
OK, look, guys, could we stop this argument? It's becoming a bit old.
For the record, I was unhappy to have libata pata in SCSI, but it got
moved into drivers/ata shortly after, limiting my influence. I thought
having a slow wind down of legacy pata in drivers/ide but moving to
libata for sata was the correct split. I agree with Jeff that the SCSI
layer did provide unique features that SATA/NCQ needed at the time ...
but I also think we need to move them into block sooner rather than
later.
I'm the last person ever to proscribe a kernel subsystem that has
willing volunteers, so drivers/ide is yours as long as you want to
maintain it. I can certainly see the merits of a thinner stack to the
embedded world, and not a few embedded developers seem to agree.
As far as moving it out of SCSI goes, I've always been a supporter of
this. Tejun looks like he's willing to execute, so I feel much more
sanguine that it will happen. The point of the notes was really to draw
attention to something I hadn't realised: we can't refactor block to
get libata out of SCSI without also changing drivers/ide, which does
make the problem harder.
On a final note about the urgency of getting libata out of SCSI: Intel
has been worrying for a while about the fatness of the SCSI/libata
stack, and its effects on performance, especially command transmission
via SAT, so I'm hoping they'll be supporting the effort.
Jmaes
next prev parent reply other threads:[~2009-04-14 22:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 12:53 LSF Papers online? Boaz Harrosh
2009-04-13 13:58 ` James Bottomley
2009-04-13 14:42 ` Boaz Harrosh
2009-04-13 14:51 ` James Bottomley
2009-04-13 15:19 ` Chris Mason
2009-04-13 15:44 ` Boaz Harrosh
2009-04-13 16:45 ` Theodore Tso
2009-04-13 18:11 ` Jonathan Corbet
2009-04-13 20:05 ` Nicholas A. Bellinger
2009-04-13 21:40 ` Bartlomiej Zolnierkiewicz
2009-04-13 21:49 ` Bartlomiej Zolnierkiewicz
2009-04-13 22:24 ` Jeff Garzik
2009-04-14 1:24 ` Bartlomiej Zolnierkiewicz
2009-04-14 10:14 ` Jeff Garzik
2009-04-14 14:54 ` Bartlomiej Zolnierkiewicz
2009-04-14 15:40 ` Jeff Garzik
2009-04-14 16:54 ` Alan Cox
2009-04-14 22:09 ` Bartlomiej Zolnierkiewicz
2009-04-14 22:49 ` James Bottomley [this message]
2009-04-15 1:39 ` Robert Hancock
2009-04-15 3:58 ` James Bottomley
2009-04-15 8:30 ` Alan Cox
2009-04-16 6:31 ` Grant Grundler
2009-04-16 16:37 ` James Bottomley
2009-04-16 17:45 ` Matthew Wilcox
2009-04-14 23:14 ` Jeff Garzik
2009-04-15 9:28 ` Alan Cox
2009-04-15 13:38 ` Bartlomiej Zolnierkiewicz
2009-04-15 14:56 ` Alan Cox
2009-04-16 16:01 ` Bartlomiej Zolnierkiewicz
2009-04-14 3:30 ` Tejun Heo
2009-04-14 14:47 ` Bartlomiej Zolnierkiewicz
2009-04-16 21:36 ` Grant Grundler
2009-04-17 4:44 ` Martin K. Petersen
2009-04-18 4:06 ` Grant Grundler
2009-04-19 11:00 ` Boaz Harrosh
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=1239749357.3638.3.camel@mulgrave \
--to=james.bottomley@hansenpartnership.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bharrosh@panasas.com \
--cc=bzolnier@gmail.com \
--cc=chris.mason@oracle.com \
--cc=corbet@lwn.net \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@kernel.org \
--cc=zach.brown@oracle.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 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.