From: Tom McNeal <trmcneal@attbi.com>
To: NFS maillist <nfs@lists.sourceforge.net>
Subject: NFS utils package, and an fsx question
Date: Sun, 12 May 2002 19:27:06 -0700 [thread overview]
Message-ID: <3CDF247A.E7106AA4@attbi.com> (raw)
Hi -
I've created and tested a new NFS utils package, which can be
downloaded from
http://nfs.sourceforge.net/nfs-utils-1-0-1-pre7.tar.gz
The tests consist of the 4 2002 Connectathon tests suites
(basic, general, special, and lock), fsx, a duplicate request
cache exerciser, and bonnie++, all running simultaneously
overnight. I tested a 2.4.18 and 2.2.19 UP client against
2.4 and 2.2 UP servers. The failure rate was less than 1%,
primarily due to interaction between special and general tests
that I haven't quite figured out yet.
I see nothing in the utils package that tells me it isn't ready
for prime time. I'd really like to see someone with MP platforms
pick this up and test it, but other than that, I think its ready
to rename as release 1.0.1. BTW, I don't know the history of release
1.0.0; It was already 1.0.1-prex when I started working on it.
I have a couple of questions about fsx behavior:
- It appears that with memory mapping allowed, fsx doesn't
allow more than 12 operations running per test, regardless of
the kernel; is this fixed with a later version of fsx, or maybe
I just have my system misconfigured? My version of fsx is about
6 months old, and I didn't look at configuration at all.
- In 2.2 kernels, the failure rate climbs significantly
unless I cut the number of operations per test in half; once
I turned off memory mapping, I ran with 5000 ops in the 2.4
kernel, but had to run about 2500 ops in the 2.2 client kernel
to get the same failure rate (~1%). Is this a suprise?
Tom
--
------------------------------------------------------------
Tom McNeal trmcneal@attbi.com (650)906-0761 (cell)
------------------------------------------------------------
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth@sourceforge.net
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-05-13 2:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-13 2:27 Tom McNeal [this message]
2002-05-13 5:35 ` NFS utils package, and an fsx question Trond Myklebust
2002-05-13 15:23 ` Tom McNeal
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=3CDF247A.E7106AA4@attbi.com \
--to=trmcneal@attbi.com \
--cc=nfs@lists.sourceforge.net \
/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.