public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Andrew Morton <akpm@zip.com.au>,
	Suparna Bhattacharya <suparna@in.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: One more bio for for floppy users in 2.5.33..
Date: Thu, 5 Sep 2002 20:31:17 +0200	[thread overview]
Message-ID: <20020905183117.GA22592@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0209051120100.1307-100000@penguin.transmeta.com>

On Thu, Sep 05 2002, Linus Torvalds wrote:
> > OK.  But still, I don't see why we need partial BIO completions.  If
> > we say that the basic unit of completion is a whole BIO, then readahead
> > can then manage latency via the outgoing bio size.
> 
> But that's horrible. The floppy driver can take huge bio's no problem, and 
> limiting bio sizes to track sizes would be a huge pain in the driver for 
> no good reason. In fact, it would be pretty much impossible, since the 
> tracks aren't even page-aligned.
> 
> So limiting bio's fundamentally _cannot_ do the right thing. While adding
> two lines of code _can_.

I agree that partial completions are the right thing to do here, and in
fact this is how the interface was originally remember?

However, I don't see how this is a two-liner change. Basically you are
changing bi_end_io() from a completion to partial completion invokation,
which requires changing (and complicating) all of them. Just adding
a sector count to bio_endio() does not enable that to partially complete
some pages. What am I missing?

Jens


  reply	other threads:[~2002-09-05 18:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 18:00 One more bio for for floppy users in 2.5.33 Linus Torvalds
2002-09-03 18:02 ` Jens Axboe
2002-09-04  7:25   ` Suparna Bhattacharya
2002-09-04 16:36     ` Linus Torvalds
2002-09-05  7:03       ` Suparna Bhattacharya
2002-09-05 15:06         ` Linus Torvalds
2002-09-05 16:26           ` Andrew Morton
2002-09-05 17:05             ` Linus Torvalds
2002-09-05 18:00               ` Andrew Morton
2002-09-05 18:28                 ` Linus Torvalds
2002-09-05 18:31                   ` Jens Axboe [this message]
2002-09-05 18:38                     ` Linus Torvalds
2002-09-05 18:38                       ` Jens Axboe
2002-09-05 19:47                         ` Peter Osterlund
2002-09-05 18:42                   ` Andrew Morton
2002-09-05 19:03                     ` Linus Torvalds
2002-09-05 19:35                       ` Andrew Morton
2002-09-05 20:27                         ` Linus Torvalds
2002-09-05 20:38                           ` Linus Torvalds
2002-09-06  6:47                           ` Helge Hafting
2002-09-06  6:59                             ` Linus Torvalds
2002-09-09 14:08                               ` Bob_Tracy
2002-09-05 20:48                         ` Linus Torvalds
2002-09-10  7:25                       ` Rogier Wolff
2002-09-10  8:01                         ` Andrew Morton
2002-09-07 11:18                     ` Daniel Phillips
2002-09-03 20:57 ` Mikael Pettersson
2002-09-03 21:52   ` Linus Torvalds
2002-09-03 22:33     ` Mikael Pettersson
  -- strict thread matches above, loose matches on Subject: below --
2002-09-07 14:43 linux

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=20020905183117.GA22592@suse.de \
    --to=axboe@suse.de \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suparna@in.ibm.com \
    --cc=torvalds@transmeta.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox