linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: lakshmi pathi <lakshmipathi.g@gmail.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: tytso@mit.edu, 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 18:49:19 +0530	[thread overview]
Message-ID: <ae2f51270912250519p22aebc0di4faec9e96e8c1707@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.01.0912241739160.3483@bogon.housecafe.de>

I'm a file system testing newbie, I have a  question/doubt,please let
me know if i'm wrong.

Do you think a tool, which uses output from "hdparm" command,to get
hard drives maximum  performance and compares it specific file system
(say for example,"ext4 provides xx throughput against max. device
throughput yy" ) would be more meaningful.

Does using hdparm (or other device throughput related tools) for
benchmarking will be useful?

Thanks.

-- 
Cheers,
Lakshmipathi.G
www.giis.co.in

  reply	other threads:[~2009-12-25 13:19 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-24 10:31 benchmark results Christian Kujau
2009-12-24 12:06 ` Ryusuke Konishi
2009-12-24 12:59 ` Teran McKinney
2009-12-24 20:01   ` Christian Kujau
2009-12-24 13:05 ` Peter Grandi
2009-12-24 21:27   ` [Jfs-discussion] " tytso
2009-12-24 23:46     ` Evgeniy Polyakov
2009-12-25 16:11       ` tytso
2010-01-04 16:27         ` Chris Mason
2010-01-04 18:57           ` Michael Rubin
2010-01-05  0:41           ` Dave Chinner
2010-01-05 15:31             ` Steven Pratt
2009-12-25  1:52     ` Christian Kujau
2009-12-25 13:19       ` lakshmi pathi [this message]
2009-12-25 16:14       ` tytso
2009-12-25 16:22         ` Larry McVoy
2009-12-25 16:33           ` tytso
2009-12-25 18:51           ` Christian Kujau
2009-12-26 16:00             ` jim owens
2009-12-26 19:06               ` Christian Kujau
2009-12-27 19:50                 ` jim owens
2009-12-27 21:55                   ` Christian Kujau
2009-12-27 22:33                     ` tytso
2009-12-28  1:24                       ` Christian Kujau
2009-12-28 14:08                       ` Larry McVoy
2010-01-15 21:42                         ` Edward Shishkin
2009-12-26 19:19               ` tytso
     [not found]           ` <20091225163341.GE32757@thunk.org>
2009-12-25 18:56             ` Christian Kujau
2009-12-25 19:32               ` Christian Kujau
2010-01-11  1:03           ` Casey Allen Shobe
2010-01-11  1:32             ` Larry McVoy
2009-12-25 18:42         ` Christian Kujau
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=ae2f51270912250519p22aebc0di4faec9e96e8c1707@mail.gmail.com \
    --to=lakshmipathi.g@gmail.com \
    --cc=ext3-users@redhat.com \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-nilfs@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    --cc=pg_jf2@jf2.for.sabi.co.uk \
    --cc=reiserfs-devel@vger.kernel.org \
    --cc=tytso@mit.edu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).