mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Badari Pulavarty <pbadari@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>,
	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: Fri, 02 Dec 2005 11:19:21 -0800	[thread overview]
Message-ID: <1133551161.21429.84.camel@localhost.localdomain> (raw)
In-Reply-To: <20051202013408.GA4225@havoc.gtf.org>

On Thu, 2005-12-01 at 20:34 -0500, Jeff Garzik wrote:
> On Thu, Dec 01, 2005 at 05:25:20PM -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.
> > 
> > Caveats:
> > 
> > a) Holds inode_lock for exorbitant amounts of time.
> > 
> > b) Needs to be taught about NUMA nodes: propagate these all the way through
> >    so the discarding can be controlled on a per-node basis.
> > 
> > c) The pagecache shrinking and slab shrinking should probably have separate
> >    controls.
> > 
> > 
> > Signed-off-by: Andrew Morton <akpm@osdl.org>
> 
> ACK, I've wanted something like this for a while.
> 
> I really think it should be a config option, though, to discourage
> people from building with it :)

Why ? Since its controlled through /proc, if some one "echo" stuff into
it, they might get crappy performance (like other /proc tunables). 
Isn't it expected ?

Thanks,
Badari


  reply	other threads:[~2005-12-02 19:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01 13:17 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 [this message]
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
     [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=1133551161.21429.84.camel@localhost.localdomain \
    --to=pbadari@gmail.com \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=jgarzik@pobox.com \
    --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 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®