From: Mark Lord <lkml@rtr.ca>
To: Mark Lord <lkml@rtr.ca>
Cc: Badari Pulavarty <pbadari@gmail.com>,
Arjan van de Ven <arjan@infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.xx: dirty pages never being sync'd to disk?
Date: Mon, 14 Nov 2005 12:44:50 -0500 [thread overview]
Message-ID: <4378CD12.9010606@rtr.ca> (raw)
In-Reply-To: <4378C626.4030107@rtr.ca>
Another intriguing observation:
If I do my file copy test from files that are already cached,
then the data usually gets committed to disk more or less
right away.
If the copy is done from uncached files, then the data usually
does not get committed to disk until I "sync" or run the
posix_fadvise test program on it.
Anyone else seeing this? 2.6.15-rc1, x86, 2GB
next prev parent reply other threads:[~2005-11-14 17:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 15:30 2.6.xx: dirty pages never being sync'd to disk? Mark Lord
2005-11-14 15:35 ` Arjan van de Ven
2005-11-14 15:49 ` Mark Lord
2005-11-14 15:54 ` Mark Lord
2005-11-14 16:56 ` Badari Pulavarty
2005-11-14 17:15 ` Mark Lord
2005-11-14 17:38 ` Mark Lord
2005-11-14 17:44 ` Mark Lord [this message]
2005-11-14 17:51 ` Mark Lord
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=4378CD12.9010606@rtr.ca \
--to=lkml@rtr.ca \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbadari@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox