public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dirk Henning Gerdes <mail@dirk-gerdes.de>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Jens Axboe <axboe@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] linux-2.6-block: deactivating pagecache for benchmarks
Date: Thu, 01 Dec 2005 14:43:43 +0100	[thread overview]
Message-ID: <1133444623.6110.57.camel@noti> (raw)
In-Reply-To: <1133443765.2853.39.camel@laptopd505.fenrus.org>

Probably I should have mentioned, how my benchmark should look like:

I have written a little c-program opening several files for reading and
writing. 
The dentry-cache would only play a role the first time, the files are
opened. I'm not quite sure about the inode-cache. 
I check if the page has buffer, and mark them as not uptodate, too. So
the buffer-cache is disabled, too.

I'm using ext2/ext3. I don't think, they use any additional caches.

But anyway: Could you explain your fake-umount idea a little more ?

Am Donnerstag, den 01.12.2005, 14:29 +0100 schrieb Arjan van de Ven:
> On Thu, 2005-12-01 at 14:17 +0100, Dirk Henning Gerdes wrote:
> > Hi Jens!
> > 
> > For doing benchmarks on the I/O-Schedulers, I thought it would be very
> > useful to disable the pagecache.
> 
> 
> for benchmarks this is not enough though, you also need to clean the
> inode and dentry caches, as well as any filesystem specific caches
> (might be buffer cache)..... 
> at which point it's probably nicer to just fake a limited umount since
> that has to do all of that anyway
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 
-- 
Dirk Henning Gerdes
Bönnersdyk 47
47803 Krefeld

Tel:  02151-755745
      0174-7776640
Mail: mail@dirk-gerdes.de


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

Thread overview: 17+ 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 [this message]
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=1133444623.6110.57.camel@noti \
    --to=mail@dirk-gerdes.de \
    --cc=arjan@infradead.org \
    --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