linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	axboe@suse.de, linux-kernel@vger.kernel.org
Subject: Re: Testing IDE-TCQ and Taskfile - doesn't work nicely:)
Date: Sun, 29 Jun 2003 12:45:21 +0200	[thread overview]
Message-ID: <20030629104521.GD29233@lug-owl.de> (raw)
In-Reply-To: <Pine.LNX.4.10.10306290229280.2711-100000@master.linux-ide.org>

[-- Attachment #1: Type: text/plain, Size: 1509 bytes --]

On Sun, 2003-06-29 02:30:29 -0700, Andre Hedrick <andre@linux-ide.org>
wrote in message <Pine.LNX.4.10.10306290229280.2711-100000@master.linux-ide.org>:
> 
> You missed a point.
> 
> Defaulting to off means stablity for the masses.
> Enduser enable is for testing to get it correct.
> Regardless, it was my $0.02 for the thread.

No, I didn't. We're in 2.5.x timeline and doing early testing (esp. with
"exotic" or rarely used features) is IMHO best done at early times. THis
is why I did it. For now, I don't exactly care for pure stability _if_ a
user can easily choose really dangerous code, esp. if it's advised as
experimental, but "you should say yes" in it's help text. This is, I
like to compile with many features to see where it breaks.

Not doing this means to walk through a mines field later, at 2.6.x
times. That is playing minesweeper with some poor end user. No good...

MfG, JBG
Btw., that patch got merged to Linus and I'm currently running
2.5.73-bk6 with TF and TCQ enabled (in config, but gets somewhat
disabled because of missing hardware of too many drives per channel) on
a laptop and my (quite a bit loaded) mirror box. No problems /
corruption so far:)

-- 
   Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2003-06-29 10:31 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-23 19:45 Testing IDE-TCQ and Taskfile - doesn't work nicely:) Jan-Benedict Glaw
2003-06-23 21:18 ` Bartlomiej Zolnierkiewicz
2003-06-23 22:19   ` Jan-Benedict Glaw
2003-06-23 23:50   ` Jan-Benedict Glaw
2003-06-24  0:53     ` Bartlomiej Zolnierkiewicz
2003-06-24  6:31       ` Jan-Benedict Glaw
2003-06-24 13:44         ` Bartlomiej Zolnierkiewicz
2003-06-24 22:40           ` Jan-Benedict Glaw
2003-06-24 23:08             ` Bartlomiej Zolnierkiewicz
2003-06-25 18:22               ` SOLVED - " Jan-Benedict Glaw
2003-06-25 18:44                 ` Bartlomiej Zolnierkiewicz
2003-06-25 19:05                   ` Jan-Benedict Glaw
2003-06-25 19:30                     ` Bartlomiej Zolnierkiewicz
2003-06-26  3:21                       ` Zwane Mwaikambo
2003-06-26  5:58                       ` Jan-Benedict Glaw
2003-06-24  8:06   ` Jens Axboe
2003-06-24 14:28   ` Jeff Garzik
2003-06-24 14:47     ` Jens Axboe
2003-06-24 15:39       ` Jeff Garzik
2003-06-29  2:17     ` Andre Hedrick
2003-06-29  8:14       ` Jan-Benedict Glaw
2003-06-29  9:30         ` Andre Hedrick
2003-06-29 10:45           ` Jan-Benedict Glaw [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=20030629104521.GD29233@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=andre@linux-ide.org \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --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;
as well as URLs for NNTP newsgroup(s).