From: Ivan Gyurdiev <ivg2@cornell.edu>
To: Jens Axboe <axboe@suse.de>
Cc: Jesper Juhl <jju@dif.dk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] config BLK_DEV_IDE_TCQ_DEPTH - text and real life don't match
Date: Tue, 16 Sep 2003 05:51:20 -0400 [thread overview]
Message-ID: <3F66DD18.30405@cornell.edu> (raw)
In-Reply-To: <20030916092730.GC930@suse.de>
So whatever happened to this list - are those things fixed now - has any
progress been made? I've had TCQ off for ages since it's dangerous for
me. That and ACPI are the only things that don't work in 2.6 ...at least
for me.
http://www.ussg.iu.edu/hypermail/linux/kernel/0307.2/1655.html
Particulary, what happened to this one:
http://www.ussg.iu.edu/hypermail/linux/kernel/0307.3/1353.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0307.3/2296.html
Perhaps it's a reiser bug ... but I do remember corrupting an xfs after
reiser, and I do remember it was 100% reproducible with depth 8 but not
32 - at 32 on boot check passes.
prev parent reply other threads:[~2003-09-16 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 22:33 [PATCH] config BLK_DEV_IDE_TCQ_DEPTH - text and real life don't match Jesper Juhl
2003-09-16 9:27 ` Jens Axboe
2003-09-16 9:51 ` Ivan Gyurdiev [this message]
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=3F66DD18.30405@cornell.edu \
--to=ivg2@cornell.edu \
--cc=axboe@suse.de \
--cc=jju@dif.dk \
--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