mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Doug McNaught <doug@wireboard.com>
To: Matthias Andree <matthias.andree@stud.uni-dortmund.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.x has finally made it!
Date: 13 Nov 2001 12:15:12 -0500	[thread overview]
Message-ID: <m3vggeiodb.fsf@belphigor.mcnaught.org> (raw)
In-Reply-To: <Pine.GSO.4.33.0111131002200.14971-100000@gurney> <20011113171836.A14967@emma1.emma.line.org> <m34rnyk511.fsf@belphigor.mcnaught.org> <20011113174250.A15774@emma1.emma.line.org>
In-Reply-To: Matthias Andree's message of "Tue, 13 Nov 2001 17:42:50 +0100"

Matthias Andree <matthias.andree@stud.uni-dortmund.de> writes:

> On Tue, 13 Nov 2001, Doug McNaught wrote:
> 
> > It's a benchmark, lighten up!  ;)
> 
> Well, he wanted to benchmark everyday use, and disk latency is also an
> issue for everyday use, of course;

But it's more a measure of your disk subsystem than your VM efficiency 
(unless something is badly wrong). 

>                                   so that's kind of pointless getting
> rid of I/O and benchmarking the cache. fsync() efficiency comes into
> play and wants to be benchmarked as well. How do you know if your
> fsync() syncs what's needed, the whole partition, the partition's meta
> data (softupdates!) or the world (all blocks)?

A very good point that I hadn't considered. 

-Doug
-- 
Let us cross over the river, and rest under the shade of the trees.
   --T. J. Jackson, 1863

  reply	other threads:[~2001-11-13 17:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-13 10:12 Alastair Stevens
2001-11-13 16:18 ` Matthias Andree
2001-11-13 16:26   ` Christoph Hellwig
2001-11-13 16:30   ` Doug McNaught
2001-11-13 16:42     ` Matthias Andree
2001-11-13 17:15       ` Doug McNaught [this message]
2001-11-14 15:30         ` Matthias Andree
2001-11-13 17:05   ` Kai Henningsen
2001-11-13 19:49     ` Kevin Wooten
2001-11-14  6:18   ` Albert D. Cahalan
2001-11-14 11:22     ` Matthias Andree

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=m3vggeiodb.fsf@belphigor.mcnaught.org \
    --to=doug@wireboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.andree@stud.uni-dortmund.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®