From: Daniel Phillips <phillips@arcor.de>
To: Jens Axboe <axboe@suse.de>
Cc: Samium Gromoff <_deepfire@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: [2.5] DAC960
Date: Sun, 15 Sep 2002 18:18:19 +0200 [thread overview]
Message-ID: <E17qc6F-0000Cw-00@starship> (raw)
In-Reply-To: <E17qbEj-0000BP-00@starship>
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
me:
http://lxr.linux.no/source/drivers/block/DAC960.c?v=2.5.31
(The DAC960 driver in all 6921 lines of funky glory)
http://lxr.linux.no/source/include/linux/bio.h?v=2.5.31#L60
(the bio struct)
http://lxr.linux.no/ident?v=2.5.31;i=bio
(everwhere it's used)
http://lxr.linux.no/source/Documentation/block/biodoc.txt?v=2.5.31
(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.
--
Daniel
next prev parent reply other threads:[~2002-09-15 16:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 5:30 Samium Gromoff
2002-09-10 6:20 ` Jens Axboe
2002-09-10 16:16 ` Dave Olien
2002-09-15 4:21 ` Daniel Phillips
2002-09-15 13:19 ` Jens Axboe
2002-09-15 15:23 ` Daniel Phillips
2002-09-15 16:18 ` Daniel Phillips [this message]
2002-09-16 20:13 ` Dave Olien
2002-09-16 20:26 ` Daniel Phillips
2002-09-16 22:08 ` Dave Olien
2002-09-16 22:25 ` Dave Olien
2002-09-19 18:49 ` Dave Olien
2002-09-19 19:16 ` Daniel Phillips
2002-09-19 22:09 ` Dave Olien
2002-09-19 22:21 ` Daniel Phillips
2002-09-20 6:21 ` Jens Axboe
2002-09-20 21:32 ` Daniel Phillips
2002-09-19 21:25 ` Dave Olien
2002-09-20 6:20 ` Jens Axboe
2002-09-15 15:14 ` Alan Cox
2002-09-15 16:20 ` Daniel Phillips
2002-09-18 16:17 James Bottomley
2002-09-18 16:40 ` Daniel Phillips
2002-09-23 19:23 Dave Olien
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=E17qc6F-0000Cw-00@starship \
--to=phillips@arcor.de \
--cc=_deepfire@mail.ru \
--cc=axboe@suse.de \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®