From: Jens Axboe <axboe@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andre Hedrick <andre@linux-ide.org>,
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 17:06:59 +0100 [thread overview]
Message-ID: <20030312160658.GM834@suse.de> (raw)
In-Reply-To: <1047489166.22694.44.camel@irongate.swansea.linux.org.uk>
On Wed, Mar 12 2003, Alan Cox wrote:
> On Wed, 2003-03-12 at 15:11, Jens Axboe wrote:
> > Then go with 128. I'd like to stress again that _if_ you get worse
> > performance it's not due to the request being a bit smaller, but indeed
> > because 248 can cause badly aligned requests.
> >
> > > got the IDE layer using 256 block writes even if we have to limit it
> > > to more modern drives by some handwaving (8Gb+ say)
> >
> > Does Windows use 256 sector requests or not? If not, then I'd sure don't
> > want to do it in Linux, the handwaving doesn't mean anything then.
>
> I am told it does, Andre can you confirm this either way. If not then its
> time to ask vendors to confirm and any vendor who says "our drives are fine"
> we put on the ok list.
Well I can hook an analyzer to such a bastard and verify it for sure,
that's one way :)
If Windows does, then we have nothing to worry about.
--
Jens Axboe
next prev parent reply other threads:[~2003-03-12 15:58 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
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 [this message]
-- 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=20030312160658.GM834@suse.de \
--to=axboe@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--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