From: Johannes Stezenbach <js@linuxtv.org>
To: Andrew Morton <akpm@osdl.org>
Cc: lkml@rtr.ca, dgc@sgi.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: dirty pages (Was: Re: [PATCH] Prevent large file writeback starvation)
Date: Tue, 14 Feb 2006 00:31:14 +0100 [thread overview]
Message-ID: <20060213233114.GA21971@linuxtv.org> (raw)
In-Reply-To: <20060213150457.547ddfb4.akpm@osdl.org>
On Mon, Feb 13, 2006 at 03:04:57PM -0800, Andrew Morton wrote:
> Johannes Stezenbach <js@linuxtv.org> wrote:
> >
> > On Mon, Feb 13, 2006, Andrew Morton wrote:
> > > Johannes Stezenbach <js@linuxtv.org> wrote:
> > > > Now copying a 700MB file makes "Dirty" go up to 350MB. It then
> > > > slowly decreases to 325MB and stays there.
> > >
> > > It shouldn't. Did you really leave it for long enough?
> > >
> > > If you did, then why does it happen there and not here?
> >
> > Good question. I just repeated the execise, rebooted and
> > copied a 700MB file. After ~30min "Dirty" is down to ~130MB, and
> > continues to decrease very slowly.
> >
> > On my Desktop machine (P4 HT, 1G RAM) "Dirty" goes down near
> > zero after ~30sec, as expected.
>
> Are you using any unusual mount options?
>
> Which filesystem types are online (not that this should affect it...)
$ cat /proc/mounts
rootfs / rootfs rw 0 0
/dev/root / ext3 rw,data=ordered 0 0
proc /proc proc rw,nodiratime 0 0
sysfs /sys sysfs rw 0 0
usbfs /proc/bus/usb usbfs rw 0 0
/dev/root /dev/.static/dev ext3 rw,data=ordered 0 0
tmpfs /dev tmpfs rw 0 0
tmpfs /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw 0 0
/dev/hda6 /home ext3 rw,data=ordered 0 0
nfsd /proc/fs/nfsd nfsd rw 0 0
$
I found that if I copy a large number of small files (e.g. the linux
source tree), "Dirty" drops back near zero after ~30sec. Only if
I copy large files it won't.
Johannes
next prev parent reply other threads:[~2006-02-13 23:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 4:00 [PATCH] Prevent large file writeback starvation David Chinner
2006-02-06 4:27 ` Andrew Morton
2006-02-06 5:48 ` David Chinner
2006-02-06 6:22 ` Andrew Morton
2006-02-06 6:36 ` Andrew Morton
2006-02-06 11:57 ` David Chinner
2006-02-06 11:55 ` David Chinner
2006-02-06 23:14 ` Andrew Morton
2006-02-07 0:34 ` David Chinner
2006-02-07 1:04 ` Andrew Morton
2006-02-07 1:31 ` David Chinner
2006-02-07 5:27 ` Andrew Morton
2006-02-07 7:42 ` David Chinner
2006-02-07 22:51 ` Andrew Morton
2006-02-07 7:49 ` David Chinner
2006-02-06 14:36 ` Mark Lord
2006-02-06 14:39 ` Mark Lord
2006-02-06 15:53 ` Several Hangs on diferent Hardwares and diferent kernels Pedro Alves
2006-02-06 20:11 ` [PATCH] Prevent large file writeback starvation Andrew Morton
2006-02-13 13:59 ` dirty pages (Was: Re: [PATCH] Prevent large file writeback starvation) Johannes Stezenbach
2006-02-13 20:08 ` Andrew Morton
2006-02-13 22:48 ` Johannes Stezenbach
2006-02-13 23:04 ` Andrew Morton
2006-02-13 23:31 ` Johannes Stezenbach [this message]
2006-02-13 23:52 ` Mark Lord
2006-02-14 0:50 ` Mark Lord
2006-02-14 16:32 ` Mark Lord
2006-04-11 12:42 ` Alexander Bergolth
2006-03-20 22:40 ` [PATCH] Prevent large file writeback starvation Alexander Bergolth
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=20060213233114.GA21971@linuxtv.org \
--to=js@linuxtv.org \
--cc=akpm@osdl.org \
--cc=dgc@sgi.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
/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.