All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Oetiker <tobi@oetiker.ch>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 00/23] per device dirty throttling -v10
Date: Fri, 14 Sep 2007 01:13:41 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.0.999.0709140113210.8141@nyyzraq.brgvxre.pu> (raw)

Peter,

I have been using your -v9 backport to 2.6.22 (thanks very much
btw) for the last few days on an amd64 system configured like this:

 [/],[/home],[/backup],...
  on top of
 [lvm2]
  using
 [/dev/sdb]
  which is an
 [areca hw raid 6 device made up from 8 sata disks]

With your patch, performance was much improved. But still there are
some seemingly simple tasks which do not work well. Like

 cp /home/bigfile.txt /backup/bigfile.txt

or also

 rm -r /backup/big-directory

They both affect disk access times of other processes very badly.

As I said, things improved a quite a bit with your patch, but I wonder
if there is more that could be done for this particular setup?

A second thing. Since my box has 8GB memory, I am intrigued by the
idea of setting dirty_ratio not as a ratio but as an absolute
number of kilobytes as it was suggested by Neil Brown with the
dirty_kb patch a few months back. Would it make sense to forward
port this patch on top of yours ?

cheers
tobi


-- 
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten
http://it.oetiker.ch tobi@oetiker.ch ++41 62 213 9902


             reply	other threads:[~2007-09-13 23:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 23:13 Tobias Oetiker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-11 19:53 [PATCH 00/23] per device dirty throttling -v10 Peter Zijlstra
2007-09-11 19:53 ` Peter Zijlstra
2007-09-12  2:31 ` John Stoffel
2007-09-12  2:31   ` John Stoffel
2007-09-12  9:00   ` Peter Zijlstra

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=alpine.DEB.0.999.0709140113210.8141@nyyzraq.brgvxre.pu \
    --to=tobi@oetiker.ch \
    --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.