From: Andrew Morton <akpm@linux-foundation.org>
To: Patrick Mau <mau@oscar.ping.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [RFC] Adjust queue unplugging and congestion limits
Date: Sun, 24 Jun 2007 12:33:50 -0700 [thread overview]
Message-ID: <20070624123350.edf433bc.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070624172722.GA865@oscar.prima.de>
On Sun, 24 Jun 2007 19:27:23 +0200 Patrick Mau <mau@oscar.ping.de> wrote:
> Good afternoon
>
> Following is a small patch to "ll_rw_block" I played around with.
> I started using "blktrace" to analyse the performance of my dated
> LVM / MD / SCSI setup. It's really a nice tool, by the way.
>
> The changes are:
>
> * Change the "q->unplug_thresh" to be halve of "q->nr_requets".
> This dynamically delays unplugging. It was hardcoded to 4 and
> makes a difference in performace because of higher merge counts.
>
> * Change the unplug timeout to 10 milliseconds.
> This is of course questionable, but I don't know why 3 was
> choosen in the first place. I just played with it.
>
> * Set the congestion on/off limits further apart.
>
> * Cleanup the congestion checks (no "+1" anymore, more readable).
>
> * Update "q->unplug_thresh" whenever "q->nr_requests" is updated
> through sysfs.
I don't think anyone has played with these settings since they first went
in and yes, there may be some benefits available here.
> I did various artifical benchmarksi, mostly tar, dd and cp (also to NFS).
> Comments are welcome.
umm, what was the result of this benchmarking? That is rather important
information ;)
prev parent reply other threads:[~2007-06-24 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 17:27 [PATCH] [RFC] Adjust queue unplugging and congestion limits Patrick Mau
2007-06-24 19:33 ` Andrew Morton [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=20070624123350.edf433bc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mau@oscar.ping.de \
/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.