All of lore.kernel.org
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Dirk Henning Gerdes <mail@dirk-gerdes.de>,
	axboe@suse.de, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] linux-2.6-block: deactivating pagecache for benchmarks
Date: Mon, 05 Dec 2005 08:54:16 -0800	[thread overview]
Message-ID: <1133801656.21429.148.camel@localhost.localdomain> (raw)
In-Reply-To: <20051201172520.7095e524.akpm@osdl.org>

On Thu, 2005-12-01 at 17:25 -0800, Andrew Morton wrote:
> Dirk Henning Gerdes <mail@dirk-gerdes.de> wrote:
> >
> >  For doing benchmarks on the I/O-Schedulers, I thought it would be very
> >  useful to disable the pagecache.
> 
> That's an FAQ.   Something like this?
> 
> 
> From: Andrew Morton <akpm@osdl.org>
> 
> Add /proc/sys/vm/drop-pagecache.  When written to, this will cause the kernel
> to discard as much pagecache and reclaimable slab objects as it can.
> 
> It won't drop dirty data, so the user should run `sync' first.

BTW, (a while ago) I tried doing similar thing from user-space 
using POSIX_FADV_DONTNEED on a file. While it worked great to 
get rid of the pagecache pages for few files, since I had to 
run this on each and every file in the filesystem - it ended 
up bloating inode, dentry slabs :( I really wanted to find out 
what files are really cached in the pagecache to run this on.

Thanks,
Badari


  parent reply	other threads:[~2005-12-05 16:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01 13:17 [PATCH 0/4] linux-2.6-block: deactivating pagecache for benchmarks Dirk Henning Gerdes
2005-12-01 13:29 ` Arjan van de Ven
2005-12-01 13:43   ` Dirk Henning Gerdes
2005-12-01 14:36 ` Jens Axboe
2005-12-02  1:25 ` Andrew Morton
2005-12-02  1:34   ` Jeff Garzik
2005-12-02 19:19     ` Badari Pulavarty
2005-12-02 19:17   ` Badari Pulavarty
2005-12-02 21:24   ` Badari Pulavarty
2005-12-02 21:44     ` Andrew Morton
2005-12-02 22:33       ` Badari Pulavarty
2005-12-05  2:13   ` Rob Landley
2005-12-05 16:20     ` Lee Revell
2005-12-05 17:28       ` Rob Landley
2005-12-05 16:54   ` Badari Pulavarty [this message]
2005-12-05  2:03 ` [uml-devel] Fwd: " Rob Landley
2005-12-05 19:21   ` Jeff Dike
2005-12-05 20:18     ` Rob Landley
     [not found] <5f08L-Um-413@gated-at.bofh.it>
2005-12-01 22:48 ` Bodo Eggert
     [not found] ` <5f7UE-3FH-13@gated-at.bofh.it>
2005-12-03  2:05   ` Bodo Eggert

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=1133801656.21429.148.camel@localhost.localdomain \
    --to=pbadari@gmail.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@dirk-gerdes.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 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.