From: tytso@mit.edu
To: Larry McVoy <lm@bitmover.com>,
Christian Kujau <lists@nerdbynature.de>,
jfs-discussion@lists.sourceforge.net,
linux-nilfs@vger.kernel.org, xfs@oss.sgi.com,
reiserfs-devel@vger.kernel.
Subject: Re: [Jfs-discussion] benchmark results
Date: Fri, 25 Dec 2009 11:33:41 -0500 [thread overview]
Message-ID: <20091225163341.GE32757@thunk.org> (raw)
In-Reply-To: <20091225162238.GB19303@bitmover.com>
On Fri, Dec 25, 2009 at 08:22:38AM -0800, Larry McVoy wrote:
>
> Dudes, sync() doesn't flush the fs cache, you have to unmount for that.
> Once upon a time Linux had an ioctl() to flush the fs buffers, I used
> it in lmbench.
>
> ioctl(fd, BLKFLSBUF, 0);
>
> No idea if that is still supported, but sync() is a joke for benchmarking.
Depends on what you are trying to do (flush has multiple meanings, so
using can be ambiguous). BLKFLSBUF will write out any dirty buffers,
*and* empty the buffer cache. I use it when benchmarking e2fsck
optimization. It doesn't do anything for the page cache. If you are
measuring the time to write a file, using fsync() or sync() will
include the time to actually write the data to disk. It won't empty
caches, though; if you are going to measure read as well as writes,
then you'll probably want to do something like "echo 3 >
/proc/sys/vm/drop-caches".
- Ted
WARNING: multiple messages have this Message-ID (diff)
From: tytso@mit.edu
To: Larry McVoy <lm@bitmover.com>,
Christian Kujau <lists@nerdbynature.de>,
jfs-discussion@lists.sourceforge.net,
linux-nilfs@vger.kernel.org, xfs@oss.sgi.com,
reiserfs-devel@vger.kernel.org,
Peter Grandi <pg_jf2@jf2.for.sabi.co.UK>,
ext-users <ext3-users@redhat.com>,
linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [Jfs-discussion] benchmark results
Date: Fri, 25 Dec 2009 11:33:41 -0500 [thread overview]
Message-ID: <20091225163341.GE32757@thunk.org> (raw)
In-Reply-To: <20091225162238.GB19303@bitmover.com>
On Fri, Dec 25, 2009 at 08:22:38AM -0800, Larry McVoy wrote:
>
> Dudes, sync() doesn't flush the fs cache, you have to unmount for that.
> Once upon a time Linux had an ioctl() to flush the fs buffers, I used
> it in lmbench.
>
> ioctl(fd, BLKFLSBUF, 0);
>
> No idea if that is still supported, but sync() is a joke for benchmarking.
Depends on what you are trying to do (flush has multiple meanings, so
using can be ambiguous). BLKFLSBUF will write out any dirty buffers,
*and* empty the buffer cache. I use it when benchmarking e2fsck
optimization. It doesn't do anything for the page cache. If you are
measuring the time to write a file, using fsync() or sync() will
include the time to actually write the data to disk. It won't empty
caches, though; if you are going to measure read as well as writes,
then you'll probably want to do something like "echo 3 >
/proc/sys/vm/drop-caches".
- Ted
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-25 16:33 UTC|newest]
Thread overview: 73+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 10:31 benchmark results Christian Kujau
2009-12-24 10:31 ` Christian Kujau
2009-12-24 12:06 ` Ryusuke Konishi
2009-12-24 12:06 ` Ryusuke Konishi
[not found] ` <alpine.DEB.2.01.0912240415450.3483@bogon.housecafe.de>
[not found] ` <4B336289.3010608@nerdbynature.de>
[not found] ` <4B336289.3010608-AanptEQQ3TL9uQeqpI+JUg@public.gmane.org>
2009-12-24 15:35 ` Ryusuke Konishi
2009-12-24 12:59 ` Teran McKinney
2009-12-24 12:59 ` Teran McKinney
2009-12-24 12:59 ` Teran McKinney
2009-12-24 20:01 ` Christian Kujau
2009-12-24 13:05 ` Peter Grandi
2009-12-24 13:05 ` [Jfs-discussion] " Peter Grandi
2009-12-24 21:27 ` tytso
2009-12-24 21:27 ` tytso
2009-12-24 23:46 ` Evgeniy Polyakov
2009-12-24 23:46 ` Evgeniy Polyakov
2009-12-25 16:11 ` tytso
2009-12-25 16:11 ` tytso
2010-01-04 16:27 ` Chris Mason
2010-01-04 16:27 ` Chris Mason
2010-01-04 18:57 ` Michael Rubin
2010-01-04 18:57 ` Michael Rubin
2010-01-04 18:57 ` Michael Rubin
2010-01-04 18:57 ` Michael Rubin
2010-01-05 0:41 ` Dave Chinner
2010-01-05 0:41 ` Dave Chinner
2010-01-05 15:31 ` Steven Pratt
2010-01-05 15:31 ` Steven Pratt
2010-01-05 0:41 ` Dave Chinner
2009-12-25 1:52 ` Christian Kujau
2009-12-25 1:52 ` Christian Kujau
2009-12-25 13:19 ` lakshmi pathi
2009-12-25 13:19 ` lakshmi pathi
2009-12-25 16:14 ` tytso
2009-12-25 16:14 ` tytso
2009-12-25 16:22 ` Larry McVoy
2009-12-25 16:33 ` tytso
2009-12-25 16:33 ` tytso [this message]
2009-12-25 16:33 ` tytso
2009-12-25 18:56 ` Christian Kujau
2009-12-25 18:56 ` Christian Kujau
2009-12-25 19:32 ` Christian Kujau
2009-12-25 19:32 ` Christian Kujau
2009-12-25 16:33 ` tytso
2009-12-25 18:51 ` Christian Kujau
2009-12-25 18:51 ` Christian Kujau
2009-12-26 16:00 ` jim owens
2009-12-26 16:00 ` jim owens
2009-12-26 19:06 ` Christian Kujau
2009-12-26 19:06 ` Christian Kujau
2009-12-27 19:50 ` jim owens
2009-12-27 19:50 ` jim owens
2009-12-27 21:55 ` Christian Kujau
2009-12-27 21:55 ` Christian Kujau
2009-12-27 22:33 ` tytso
2009-12-27 22:33 ` tytso
2009-12-28 1:24 ` Christian Kujau
2009-12-28 1:24 ` Christian Kujau
2009-12-28 14:08 ` Larry McVoy
2009-12-28 14:08 ` Larry McVoy
2010-01-15 21:42 ` Edward Shishkin
2010-01-15 21:42 ` Edward Shishkin
2010-01-15 21:42 ` Edward Shishkin
2010-01-15 21:42 ` Edward Shishkin
2009-12-26 19:19 ` tytso
2009-12-26 19:19 ` tytso
2010-01-11 1:03 ` Casey Allen Shobe
2010-01-11 1:32 ` Larry McVoy
2010-01-11 1:32 ` Larry McVoy
2009-12-25 18:42 ` Christian Kujau
2009-12-25 18:42 ` Christian Kujau
2009-12-29 11:27 ` Emmanuel Florac
2009-12-29 11:27 ` Emmanuel Florac
2009-12-29 11:27 ` Emmanuel Florac
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=20091225163341.GE32757@thunk.org \
--to=tytso@mit.edu \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-nilfs@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=lm@bitmover.com \
--cc=reiserfs-devel@vger.kernel. \
--cc=xfs@oss.sgi.com \
/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.