From: Martin Knoblauch <spamtrap@knobisoft.de>
To: Leroy van Logchem <leroy.vanlogchem@wldelft.nl>,
linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Peter zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: huge improvement with per-device dirty throttling
Date: Thu, 6 Sep 2007 02:50:10 -0700 (PDT) [thread overview]
Message-ID: <351207.28447.qm@web32602.mail.mud.yahoo.com> (raw)
In-Reply-To: <713371.64716.qm@web32603.mail.mud.yahoo.com>
--- Martin Knoblauch <knobi@knobisoft.de> wrote:
>
> --- Leroy van Logchem <leroy.vanlogchem@wldelft.nl> wrote:
>
> > Andrea Arcangeli wrote:
> > > On Wed, Aug 22, 2007 at 01:05:13PM +0200, Andi Kleen wrote:
> > >> Ok perhaps the new adaptive dirty limits helps your single disk
> > >> a lot too. But your improvements seem to be more "collateral
> > damage" @)
> > >>
> > >> But if that was true it might be enough to just change the dirty
> > limits
> > >> to get the same effect on your system. You might want to play
> with
> > >> /proc/sys/vm/dirty_*
> > >
> > > The adaptive dirty limit is per task so it can't be reproduced
> with
> > > global sysctl. It made quite some difference when I researched
> into
> > it
> > > in function of time. This isn't in function of time but it
> > certainly
> > > makes a lot of difference too, actually it's the most important
> > part
> > > of the patchset for most people, the rest is for the corner cases
> > that
> > > aren't handled right currently (writing to a slow device with
> > > writeback cache has always been hanging the whole thing).
> >
> >
> > Self-tuning > static sysctl's. The last years we needed to use very
>
> > small values for dirty_ratio and dirty_background_ratio to soften
> the
> >
> > latency problems we have during sustained writes. Imo these patches
>
> > really help in many cases, please commit to mainline.
> >
> > --
> > Leroy
> >
>
> while it helps in some situations, I did some tests today with
> 2.6.22.6+bdi-v9 (Peter was so kind) which seem to indicate that it
> hurts NFS writes. Anyone seen similar effects?
>
> Otherwise I would just second your request. It definitely helps the
> problematic performance of my CCISS based RAID5 volume.
>
please disregard my comment about NFS write performance. What I have
seen is caused by some other stuff I am toying with.
So, I second your request to push this forward.
Martin
------------------------------------------------------
Martin Knoblauch
email: k n o b i AT knobisoft DOT de
www: http://www.knobisoft.de
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-09-06 9:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 6:37 Jeffrey W. Baker
2007-08-22 11:05 ` Andi Kleen
2007-08-22 11:09 ` Paolo Ornati
2007-08-22 12:47 ` Andrea Arcangeli
2007-09-04 9:37 ` Leroy van Logchem
2007-09-04 19:23 ` Martin Knoblauch
2007-09-06 9:50 ` Martin Knoblauch [this message]
2007-09-05 8:54 ` Martin Knoblauch
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=351207.28447.qm@web32602.mail.mud.yahoo.com \
--to=spamtrap@knobisoft.de \
--cc=a.p.zijlstra@chello.nl \
--cc=leroy.vanlogchem@wldelft.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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