public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Andre Hedrick <andre@linux-ide.org>
Cc: scott thomason <scott-kernel@thomasons.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: bio too big device
Date: Wed, 12 Mar 2003 11:14:14 +0100	[thread overview]
Message-ID: <20030312101414.GB3950@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10303120205250.391-100000@master.linux-ide.org>

On Wed, Mar 12 2003, Andre Hedrick wrote:
> 
> No that is wrong to force all other drives to under perform because on
> one.  If you are going to impose 255 then pushi it back to 128 were it is
> a single scatter list.  This issue has bugged me for years and now that we
> know the exact model we apply an exception rule to it.
> 
> This is one silly bug that I have heard about.

See that's the whole point, is there any performance issue with 248 vs
256 sectors? For a 248 sectors vs 256 command alone, I doubt it. The
only problem I see is for potential chop-ups of 248 - 8 - 248 - 8 - 248
- 8 - etc. But due to merging, only the last command should be smaller.

So I still think it's much better stick with the safe choice. Why do you
think it's only one drive that has this bug? It basically boils down to
whether That Other OS uses 256 sector commands or not. If it doesn't, I
wouldn't trust the drives one bit.

And finally, _I'm_ not imposing anything. The limit is driver tweakable,
always has been.

-- 
Jens Axboe


  reply	other threads:[~2003-03-12 10:03 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-12  2:55 bio too big device scott thomason
2003-03-12  3:17 ` scott thomason
2003-03-12  8:18   ` Jens Axboe
2003-03-12  3:37 ` Neil Brown
2003-03-12  3:49   ` scott thomason
2003-03-12  8:30   ` Jens Axboe
2003-03-12  5:01 ` Andre Hedrick
2003-03-12  8:47   ` Andries Brouwer
2003-03-12  8:59     ` Andre Hedrick
2003-03-12  8:51   ` Jens Axboe
2003-03-12  9:01     ` Andre Hedrick
2003-03-12  9:09       ` Jens Axboe
2003-03-12 10:07         ` Andre Hedrick
2003-03-12 10:14           ` Jens Axboe [this message]
2003-03-12 15:44             ` Andries Brouwer
2003-03-12 15:51               ` Jens Axboe
2003-03-12 16:02                 ` Andries Brouwer
2003-03-12 16:06                   ` Jens Axboe
2003-03-12 16:14                 ` John Bradford
2003-03-12 17:59               ` Linus Torvalds
2003-03-12 19:05                 ` John Bradford
2003-03-12 19:14                   ` Linus Torvalds
2003-03-12 22:20                     ` John Bradford
2003-03-12 21:28                 ` Andries Brouwer
2003-03-14 11:19                   ` Paul Gortmaker
2003-03-12 21:45                 ` Alan Cox
2003-03-12 14:54           ` scott thomason
2003-03-12 14:58             ` Jens Axboe
2003-03-12 17:09             ` Alan Cox
2003-03-12 16:14         ` Alan Cox
2003-03-12 15:11           ` Jens Axboe
2003-03-12 17:12             ` Alan Cox
2003-03-12 16:06               ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2003-03-12 18:19 Manfred Spraul
2003-03-12 21:40 ` Alan Cox
     [not found] <20030416172122.M65357@gw>
     [not found] ` <20030416181944.M32238@gw>
2003-04-16 18:32   ` Anders Larsson
2003-04-17 13:36     ` Alan Cox
2003-04-16 18:43 Mudama, Eric

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=20030312101414.GB3950@suse.de \
    --to=axboe@suse.de \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=scott-kernel@thomasons.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