public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Henning Gerdes <mail@dirk-gerdes.de>
To: Jens Axboe <axboe@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/4] linux-2.6-block: deactivating pagecache for benchmarks
Date: Thu, 01 Dec 2005 14:17:31 +0100	[thread overview]
Message-ID: <1133443051.6110.32.camel@noti> (raw)

Hi Jens!

For doing benchmarks on the I/O-Schedulers, I thought it would be very
useful to disable the pagecache.

I didn't want to make it so complicated so I just mark pages as
not-uptodate, so they have to be read again. Another reason was, that I
wanted to keep the conditions as near to reality as possible.

Further I thought it would be useful, if you could turn the pagecache on
and off without rebooting the system.

I implemented a proc-fs entry "/proc/benchmark/pagecache" for this.

Probably this patch can be useful for anyone else, who wants to do  some
benchmarks on block-layer stuff.
And if not, I would appreciate if you could have a look on it.

Signed-off-by: Dirk Gerdes <mail@dirk-gerdes.de>




             reply	other threads:[~2005-12-01 13:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-01 13:17 Dirk Henning Gerdes [this message]
2005-12-01 13:29 ` [PATCH 0/4] linux-2.6-block: deactivating pagecache for benchmarks 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
     [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=1133443051.6110.32.camel@noti \
    --to=mail@dirk-gerdes.de \
    --cc=axboe@suse.de \
    --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