From: Nikita Danilov <nikita@clusterfs.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: [PATCH] per-task-predictive-write-throttling-1
Date: Thu, 15 Sep 2005 10:04:38 +0400 [thread overview]
Message-ID: <17193.3830.498682.626783@gargle.gargle.HOWL> (raw)
In-Reply-To: <20050914220334.GF4966@opteron.random>
Andrea Arcangeli writes:
> Hello,
>
> I wrote a patch to try avoiding making dirty about half the ram of the
> computer when a single task is writing to disk (like during untarring or
Why is that useful? Don't we want (in general) to cache as many dirty
pages as possible in the hope that some of them will be re-dirtied (thus
avoiding additional write) or truncated (avoiding write altogether)?
Nikita.
next prev parent reply other threads:[~2005-09-16 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 22:03 Andrea Arcangeli
2005-09-15 0:44 ` Con Kolivas
2005-09-15 17:14 ` Andrea Arcangeli
2005-09-16 10:42 ` Anton Blanchard
2005-09-16 15:12 ` Andrea Arcangeli
2005-09-15 6:04 ` Nikita Danilov [this message]
2005-09-16 15:34 ` Andrea Arcangeli
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=17193.3830.498682.626783@gargle.gargle.HOWL \
--to=nikita@clusterfs.com \
--cc=Linux-Kernel@vger.kernel.org \
--cc=andrea@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®