All of lore.kernel.org
 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: Sun, 25 Jul 2004 20:07:21 -0400	[thread overview]
Message-ID: <87smbfr5qe.fsf@osu.edu> (raw)
In-Reply-To: 1090647090.8775.19.camel@kryten.internal.splhi.com

Tim Wright <timw@splhi.com> writes:

> Take a look at the code in hdparm tool that handles the '-f' option.
>
> Basically calling ioctl(fd, BLKFLSBUF, o) where fd is a file descriptor
> opened on the block device on which your filesystem resides should be
> enough to clear the cache.

Thanks, that looks pretty useful, at least to force the I/O to make it
outside the kernel.  I'm still getting cache hits for some read tests
though, no doubt due to cache near the physical disks and/or
controllers.  Correct me if I'm wrong, but this ioctl doesn't appear
to go out and tell disks to clear their caches.

I think I'll use the BLKFLSBUF in any case in my tests though, as it
doesn't seem to take very long to execute.  It can't hurt, and should
complement the act of reading through a large dummy file, which should
take care of the disk/controller caches.
-- 
Benjamin Rutt


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

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 22:54 clearing filesystem cache for I/O benchmarks Benjamin Rutt
2004-07-24  5:21 ` Chris Wedgwood
2004-07-24  5:31 ` Tim Wright
2004-07-26  0:07   ` Benjamin Rutt [this message]
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
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=87smbfr5qe.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 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.