From: Jens Axboe <axboe@suse.de>
To: Jesper Juhl <jju@dif.dk>
Cc: 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 11:27:30 +0200 [thread overview]
Message-ID: <20030916092730.GC930@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.56.0309160025510.6467@jju_lnx.backbone.dif.dk>
On Tue, Sep 16 2003, Jesper Juhl wrote:
>
> In drivers/ide/Kconfig you find the following help text for
> BLK_DEV_IDE_TCQ_DEPTH
>
> "You probably just want the default of 32 here. If you enter an invalid
> number, the default value will be used."
>
> But the default is /not/ 32, the default is 8. The patch bellow changes
> the default to match the help text... An alternative is of course to
> change the text to match the current default of 8, but I opted for
> changing the default in this patch.
>
>
> Kind regards,
>
> Jesper Juhl <jju@dif.dk>
>
>
>
> diff -u linux-2.6.0-test5-orig/drivers/ide/Kconfig linux-2.6.0-test5/drivers/ide/Kconfig
> --- linux-2.6.0-test5-orig/drivers/ide/Kconfig 2003-09-08 21:50:03.000000000 +0200
> +++ linux-2.6.0-test5/drivers/ide/Kconfig 2003-09-16 00:30:20.000000000 +0200
> @@ -471,7 +471,7 @@
> config BLK_DEV_IDE_TCQ_DEPTH
> int "Default queue depth"
> depends on BLK_DEV_IDE_TCQ
> - default "8"
> + default "32"
> help
> Maximum size of commands to enable per-drive. Any value between 1
> and 32 is valid, with 32 being the maxium that the hardware supports.
Yes that is fine, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2003-09-16 9:27 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 [this message]
2003-09-16 9:51 ` Ivan Gyurdiev
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=20030916092730.GC930@suse.de \
--to=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 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.