From: Jens Axboe <jens.axboe@oracle.com>
To: Thomas Maier <balagi@justmail.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"petero2@telia.com" <petero2@telia.com>,
"akpm@osdl.org" <akpm@osdl.org>
Subject: Re: [PATCH 8/11] 2.6.18-mm3 pktcdvd: bio write congestion control
Date: Tue, 3 Oct 2006 17:29:00 +0200 [thread overview]
Message-ID: <20061003152859.GQ7778@kernel.dk> (raw)
In-Reply-To: <op.tguqidxpiudtyh@master>
On Tue, Oct 03 2006, Thomas Maier wrote:
> Hello,
>
> this patch adds the ability to control the size of the drivers
> bio write queue.
imho, this should not be a configuration option. The driver is perfectly
capable of sizing this queue appropriately (determined by the device)
without user interaction. Basically the option just needs to prevent the
system from falling over, just choose some low sane value.
--
Jens Axboe
next prev parent reply other threads:[~2006-10-03 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 15:26 [PATCH 8/11] 2.6.18-mm3 pktcdvd: bio write congestion control Thomas Maier
2006-10-03 15:29 ` Jens Axboe [this message]
2006-10-09 10:05 ` Thomas Maier
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=20061003152859.GQ7778@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@osdl.org \
--cc=balagi@justmail.de \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.com \
/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