public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Suparna Bhattacharya <suparna@in.ibm.com>
To: linux-kernel@vger.kernel.org, lse-tech@lists.sourceforge.net
Subject: bio write up - Updated notes on block layer design changes
Date: Thu, 29 Nov 2001 10:06:09 -0500	[thread overview]
Message-ID: <20011129100609.A1356@in.ibm.com> (raw)
In-Reply-To: <20011128154533.A1437@in.ibm.com> <20011128220130.K23858@suse.de> <20011129044644.A1717@in.ibm.com> <20011129075720.B5788@suse.de>
In-Reply-To: <20011129075720.B5788@suse.de>; from axboe@suse.de on Thu, Nov 29, 2001 at 07:57:20AM +0100

On Thu, Nov 29, 2001 at 07:57:20AM +0100, Jens Axboe wrote:

> I've lost track of what else there is to explain, so I'll stop now. If
> you have problems convering a driver or questions in general, fire away.
> Suparana@IBM has written lots of stuff about bio as it was a WIP, see
>
> http://lse.sourceforge.net/io/bionotes.txt
>
> it may not be completely uptodate right now wrt multi-page bios etc, but
> I know that is on its way :-)
> 
> -- 
> Jens Axboe

I just posted the updated design notes covering the multi-page bios.
Same place: i.e. http://lse.sourceforge.net/io/bionotes.txt

The intent of these notes is to set the changes in the context of past
discussions related to the block layer design. It attempts to cover some of the
alternatives and ideas put forth by various people, analyse pros and cons,
cover the rationale behind some of the design decisions, and peek into a
few ideas that people are thinking about/ working on, which may not already
be in there yet.

Any additions to make this more complete/interesting or any corrections (I may
have missed some things) are welcome.

Regards
Suparna

           reply	other threads:[~2001-11-29  9:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20011129075720.B5788@suse.de>]

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=20011129100609.A1356@in.ibm.com \
    --to=suparna@in.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lse-tech@lists.sourceforge.net \
    /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