From: Marcelo Penna Guerra <eu@marcelopenna.org>
To: linux-kernel@vger.kernel.org
Subject: Re: SII SATA request size limit
Date: Fri, 12 Sep 2003 20:07:23 -0300 [thread overview]
Message-ID: <200309122007.35542.eu@marcelopenna.org> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alan Cox escreveu:
> It isnt that simple, unfortunately you need an NDA for the full story.
> If you want to check which chips need it get a setup that hangs reliably
> with large transfers, put the same disks on a newer controller that
> doesnt and see what happens
So, shouldn't we go back to my suggestion? A lot of users won't know that this
limit is being set and telling them on boot time would be a good thing I
think.
And I still don't know how to set this limit back to 128 with 2.6.x kernels.
It can't be done the same way as in 2.4.x, can it?
Marcelo Penna Guerra
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/YlGyD/U0kdg4PFoRAiHdAJ97opZnlt0uVKh+GVERMtKbH4HmWACgj21x
0zSI4+LRkBs3Dz6gDvdilIU=
=Saft
-----END PGP SIGNATURE-----
next reply other threads:[~2003-09-12 23:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 23:07 Marcelo Penna Guerra [this message]
2003-09-12 23:16 ` SII SATA request size limit Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-09-18 17:43 Allen Martin
2003-09-15 16:33 CASINO_E
2003-09-15 15:24 CASINO_E
2003-09-15 15:32 ` Jens Axboe
2003-09-15 16:00 ` Justin Cormack
2003-09-15 16:07 ` Jens Axboe
2003-09-15 22:19 ` Alan Cox
2003-09-14 0:57 Eduardo Casino
2003-09-13 16:43 Marcelo Penna Guerra
2003-09-12 21:00 Marcelo Penna Guerra
2003-09-12 22:28 ` Alan Cox
2003-09-12 20:55 Marcelo Penna Guerra
2003-09-13 10:56 ` Witold Krecicki
2003-09-12 20:48 Eduardo Casino
2003-09-15 8:47 ` Jens Axboe
2003-09-12 2:57 Marcelo Penna Guerra
2003-09-12 10:41 ` Alan Cox
2003-09-12 17:46 ` Witold Krecicki
2003-09-15 10:12 ` Adam Jones
2003-09-18 11:44 ` Witold Krecicki
2003-09-15 5:57 ` Catalin BOIE
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=200309122007.35542.eu@marcelopenna.org \
--to=eu@marcelopenna.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.