From: Tom Vier <tmv@comcast.net>
To: Nate Diller <nate.diller@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4: first impression (vs xfs and jfs)
Date: Thu, 8 Jun 2006 10:18:02 -0400 [thread overview]
Message-ID: <20060608141802.GB5851@zero> (raw)
In-Reply-To: <5c49b0ed0606071755w3412e2eave2e3449361cd8b42@mail.gmail.com>
On Wed, Jun 07, 2006 at 05:55:25PM -0700, Nate Diller wrote:
> this is something i've been wanting to address for a while now. at
> the moment, the VM starts to flush pages when
> /proc/sys/vm/dirty_background_ratio is exceeded, and it flushes pages
> without regard to which process dirtied them or which file they are
> in. it begins to throttle processes (make them wait for some dirty
> pages to be cleaned before they can dirty more of them) when
> dirty_ratio is exceeded.
That ratio is something i'll have to play with.
/proc/sys/vm/dirty_writeback_centisecs looks like it could help me as well.
With two (and eventually ext3, as well) fs'es using delayed allocation, it
may be best to change those values (especially when you have several gigs of
ram). I don't suspose there's a way to make it per fs, tho. fs'es don't walk
dirty pages, do they? Only the vm decides when to write out? ext3 and r4 do
have write timeouts, tho.
--
Tom Vier <tmv@comcast.net>
DSA Key ID 0x15741ECE
next prev parent reply other threads:[~2006-06-08 14:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-23 15:51 reiser4: first impression (vs xfs and jfs) Tom Vier
2006-05-23 19:08 ` Gregory Maxwell
2006-05-23 19:13 ` Alexey Polyakov
[not found] ` <20060523201712.GD25889@zero>
2006-05-23 21:00 ` Alexey Polyakov
2006-06-06 13:44 ` Tom Vier
2006-06-06 14:38 ` Vladimir V. Saveliev
2006-06-06 15:30 ` Clay Barnes
2006-06-06 17:47 ` PFC
2006-06-06 19:26 ` Hans Reiser
2006-06-07 17:21 ` PFC
2006-06-06 19:25 ` Hans Reiser
2006-06-07 0:13 ` Clay Barnes
2006-06-07 0:42 ` Hans Reiser
2006-06-08 0:55 ` Nate Diller
2006-06-08 14:18 ` Tom Vier [this message]
2006-06-08 14:06 ` Tom Vier
2006-06-09 8:05 ` Hans Reiser
2006-06-07 17:58 ` Tom Vier
2006-06-08 0:41 ` Nate Diller
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=20060608141802.GB5851@zero \
--to=tmv@comcast.net \
--cc=nate.diller@gmail.com \
--cc=reiserfs-list@namesys.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 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.