From: Manfred Spraul <manfred@colorfullife.com>
To: Jens Axboe <axboe@suse.de>
Cc: Andre Hedrick <andre@linux-ide.org>, linux-kernel@vger.kernel.org
Subject: Re: bio too big device
Date: Wed, 12 Mar 2003 19:19:53 +0100 [thread overview]
Message-ID: <3E6F7A49.50709@colorfullife.com> (raw)
Jens wrote:
>On Wed, Mar 12 2003, Andre Hedrick wrote:
>>
>> So lets dirty list the one drive by Paul G. and be done.
>> Can we do that?
>
>Who cares, really? There's not much point in doing it, we're talking 248
>vs 256 sectors in reality. I think it's a _bad_ idea, lets just keep it
>at 255 and avoid silly drive bugs there.
>
>
I think a black list would be the right thing:
linux/drivers/ide/ide-probe.c:
>#ifdef CONFIG_BLK_DEV_PDC4030
> max_sectors = 127;
>#else
> max_sectors = 255;
>#endif
> blk_queue_max_sectors(q, max_sectors);
>
>
>
IDE uses 127 sector requests if support for PDC4030 is compiled it,
otherwise 255. It seems someone started with a blacklist, but never
completed it.
Does any distro enable PDC4030 support?
--
Manfred
next reply other threads:[~2003-03-12 18:10 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-12 18:19 Manfred Spraul [this message]
2003-03-12 21:30 ` [PATCH] don't ignore chipset specific sector size (Was Re: bio too big device) Alexander Atanasov
2003-03-12 21:40 ` bio too big device Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-04-16 18:43 Mudama, Eric
[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-03-12 2:55 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
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=3E6F7A49.50709@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=andre@linux-ide.org \
--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