From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Boaz Harrosh <bharrosh@panasas.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Zach Brown <zach.brown@oracle.com>,
Chris Mason <chris.mason@oracle.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: LSF Papers online?
Date: Tue, 14 Apr 2009 16:47:42 +0200 [thread overview]
Message-ID: <200904141647.43049.bzolnier@gmail.com> (raw)
In-Reply-To: <49E40362.1070405@kernel.org>
On Tuesday 14 April 2009 05:30:42 Tejun Heo wrote:
> Hello, Bartlomiej.
>
> Bartlomiej Zolnierkiewicz wrote:
> > I've started reading it and immediately noticed a thing which made by day. :-)
> >
> > Sorry if it will sound off-topic or undiplomatic but it is the best occasion
> > to straighten up some facts:
> >
> > "Discussion then moved on to the current status of getting libata out of
> > SCSI: we have had several successes, notably timer handling and pieces of
> > error handling have moved up to block. Unfortunately, the current progress
> > has reached the point where it's being impeded by the legacy IDE subsystem
> >
> > Heh, you can also blame the lack of world peace on the legacy IDE subsystem.
> >
> > I wonder who came up with this ridiculous excuse (I'm sure it wasn't James!).
>
> Eh... It was my session. It probably is a bit too summarized. I
> wans't really trying to blame IDE. The point was that, at this point,
> adding any feature to the block layer is pretty precarious because in
> many places block layer API has become somewhat ambiguous and many
> users have been abusing in interesting ways for quite some time. IDE,
> due to its history and complexity, happens to be the most complex one
> to clean up, so that was why IDE was mentioned in the session.
>
> It's not like IDE has been preventing libata separation for all those
> years. It's more like, when finally I got my lazy ass moving about
> moving features from SCSI midlayer to block layer, I realized I better
> clean up block API before moving forward and IDE was the most
> difficult user of block API in the process.
Right, this is the proper way of doing it.
> I apologize if it sounded like an attack on IDE. It's true that IDE
> is the biggest block API abuser but it's mostly due to its long
> history and inherent complexity and you have been doing a lot to clean
> it up, so let's get it done.
No worries, lets focus on cleaning this up.
Thanks,
Bart
next prev parent reply other threads:[~2009-04-14 14:51 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
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 [this message]
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=200904141647.43049.bzolnier@gmail.com \
--to=bzolnier@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=bharrosh@panasas.com \
--cc=chris.mason@oracle.com \
--cc=corbet@lwn.net \
--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.