linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Theurer <habanero@us.ibm.com>
To: Roberto Nibali <ratz@tac.ch>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Journal Filesystem Comparison on Netbench
Date: Tue, 28 Aug 2001 10:28:21 -0500	[thread overview]
Message-ID: <3B8BB895.179331CE@us.ibm.com> (raw)
In-Reply-To: <3B8A6122.3C784F2D@us.ibm.com> <3B8B6CEF.17C616C0@tac.ch>

Roberto Nibali wrote:
> 
> Hello,
> 
> Thank you for those interesting tests.
> 
> > Some optimizations were used for linux, including zerocopy,
> > IRQ affinity, and interrupt delay for the gigabit cards,
> > and process affinity for the smbd processes.
> 
> Why is ext3 the only tested journaling filesystem that showed
> dropped packets [1] during the test and how do you explain it?
> 
> [1]: http://lse.sourceforge.net/benchmarks/netbench/results/\
>      august_2001/filesystems/raid1e/ext3/4p/droppped_packets.txt

Dropped packets are usually a side effect of the interrupt delay option
in the e1000 driver.  I choose 256 usec delay (default is 64) for all
these tests, and usually there is a very small % of dropped packets,
which usually shows up as 0.00%, since I only show 1/100's of a percent
in that output.  The other tests do have dropped packets, and I should
change that script to have more significant digits to show that.  I'm
not sure why ext3 shows more than the others.  Does ext3 have any spin
locks with interrupts disabled?

Andrew Theurer

  reply	other threads:[~2001-08-28 15:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 15:02 Journal Filesystem Comparison on Netbench Andrew Theurer
2001-08-27 18:24 ` Journal FS Comparison on IOzone (was Netbench) Randy.Dunlap
2001-08-27 18:59   ` Brian
2001-08-27 19:28   ` Andrew Theurer
2001-08-29 16:39     ` Randy.Dunlap
2001-08-30 15:08   ` YAFB: Yet Another Filesystem Bench Yves Rougy
2001-08-27 20:04 ` Journal Filesystem Comparison on Netbench Hans Reiser
2001-08-27 20:29   ` Andrew Theurer
2001-08-27 21:19   ` Randy.Dunlap
2001-08-27 21:41     ` [reiserfs-dev] " Hans Reiser
2001-08-28 10:05 ` Roberto Nibali
2001-08-28 15:28   ` Andrew Theurer [this message]
2001-08-28 18:38     ` Andrew Morton
     [not found] <3B8A6122.3C784F2D@us.ibm.com.suse.lists.linux.kernel>
     [not found] ` <3B8AA7B9.8EB836FF@namesys.com.suse.lists.linux.kernel>
2001-08-28  6:51   ` Andi Kleen
2001-08-28 10:41     ` Emmanuel Varagnat
2001-08-28 10:50       ` Andi Kleen
2001-08-28 11:35         ` Emmanuel Varagnat
2001-08-28 15:07         ` Andrew Theurer

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=3B8BB895.179331CE@us.ibm.com \
    --to=habanero@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ratz@tac.ch \
    /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).