mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Rutt <rutt.4+news@osu.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: clearing filesystem cache for I/O benchmarks
Date: Mon, 26 Jul 2004 09:02:45 -0400	[thread overview]
Message-ID: <87pt6iq5u2.fsf@osu.edu> (raw)
In-Reply-To: <20040726002524.2ade65c3.akpm@osdl.org>

Andrew Morton <akpm@osdl.org> writes:

> Benjamin Rutt <rutt.4+news@osu.edu> wrote:
>>
>>  How can I purge all of the kernel's filesystem caches, so I can trust
>>  that my I/O (read) requests I'm trying to benchmark bypass the kernel
>>  filesystem cache?
>
> Either delete the benchmark test files or

I'm not sure I follow.  If I delete the benchmark files, I'll only
need to create them again later in order to do a read test, and I'll
have the same problem then, of how to eliminate the just-written-data
from cache.  Unless you're suggesting I write using some special mode
that won't enter the written data into cache?  (e.g. O_DIRECT?)

> , in 2.6, use fsync+posix_fadvise(POSIX_FADV_DONTNEED);

Thanks for the reference, I wasn't aware of that one.  We are running
some 2.4 kernels in our storage cluster unfortunately so that won't be
usable for us everywhere.  I take it POSIX_FADV_DONTNEED is ignored
under 2.4.

A related question...if no posix_fadvise() advice has been given, does
reading sequentially every byte of an 8GB file on a machine with <=
8GB of RAM guarantee that any page cache data that existed on the
machine prior to the start of the 8GB read is now gone?
-- 
Benjamin Rutt


  reply	other threads:[~2004-07-26 13:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 22:54 Benjamin Rutt
2004-07-24  5:21 ` Chris Wedgwood
2004-07-24  5:31 ` Tim Wright
2004-07-26  0:07   ` Benjamin Rutt
2004-07-26  1:40     ` Bernd Eckenfels
2004-07-26 12:47       ` Benjamin Rutt
2004-07-25  8:11 ` Andreas Haumer
2004-07-26  7:25 ` Andrew Morton
2004-07-26 13:02   ` Benjamin Rutt [this message]
2004-07-27  6:40     ` Andrew Morton
2004-07-27  7:16       ` Hans Reiser
2004-07-27 17:31         ` Benjamin Rutt
2004-07-27 18:03           ` Hans Reiser
2004-07-28 12:38             ` Benjamin Rutt
2004-07-28 17:03               ` Hans Reiser
2004-07-28 18:19                 ` Benjamin Rutt
2004-07-27 17:25       ` Benjamin Rutt
2004-07-27 20:00         ` Timothy Miller
2004-07-28 12:51           ` Benjamin Rutt
2004-07-29  1:05       ` Nathan Scott

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=87pt6iq5u2.fsf@osu.edu \
    --to=rutt.4+news@osu.edu \
    --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 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®