[lkml]   [2002]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [2.5] DAC960
On Sunday 15 September 2002 17:23, Daniel Phillips wrote:
> On Sunday 15 September 2002 15:19, Jens Axboe wrote:
> Well, you're looking at the situation from the block IO maintainer's
> point of view. We also need certain scsi-style functionality available
> across all disk systems, such as barriers in a form usable by
> filesystems. Maybe you *can* suck all that functionality into the
> block layer, but maybe it needs higher level support as well. I'll
> bet on the latter, and I won't have to speculate, pretty soon.

Oops, sorry, this is inverted, the block layer is the higher of the
two. Anyway, that's what you get for making a VM hacker fix the
driver you broke ;-)

The Q of this signal will start increasing pretty soon (got to move
some cables and boxes around next. Got to fix up Theo's PAM breakage
so ssh works again. Got to point LXR at bio.)

Anybody interested in working through this learning curve along with
(The DAC960 driver in all 6921 lines of funky glory)
(the bio struct);i=bio
(everwhere it's used)
(Suparna's excellent bio writeup)

By the way, the gentlemanly thing to do would be to put Suparna first in
the list of authors of the writeup since 90% of the text is hers. On
the other hand, you're being a little too humble calling this a "bio
rewrite" - it's not, it's a new animal, or at least, it's a wholesale
block layer replacement.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.077 / U:11.664 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site