From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Tom McNeal <trmcneal@attbi.com>
Cc: NFS maillist <nfs@lists.sourceforge.net>
Subject: Re: Utils package testing
Date: 12 Jun 2002 14:21:39 +0200 [thread overview]
Message-ID: <shsy9dkwuuk.fsf@charged.uio.no> (raw)
In-Reply-To: <3D062664.C93B7399@attbi.com>
>>>>> " " == Tom McNeal <trmcneal@attbi.com> writes:
> - Does locking take a much longer time in ext3 file systems,
> or in the patched environment? In the patched kernel,
> exporting ext3, the connectathon lock tests seemed to take
> up to 10x as long, but that was over many hours, with a big
> load. When run just once with the other connectathon tests,
> it didn't seem so different.
Flushing to disk would be slower with ext3. As this is done every time
somebody takes or releases a lock...
> - The client net statistics in /proc/net/rpc/nfs seems to remain
> at 0 regardless of the activity and regardless of the
> kernel. I'm going to start browsing through the kernel code
> to see if there is something obvious, but maybe someone
> knows about this already. I didn't see anything in the
> mailing list.
I've never touched the 'net statistics' field, and I've no idea what
it purports to measure. As far as I'm concerned it can be removed
entirely...
Cheers,
Trond
_______________________________________________________________
Sponsored by:
ThinkGeek at http://www.ThinkGeek.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-06-12 12:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 16:33 Utils package testing Tom McNeal
2002-06-12 12:21 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-12 15:22 Bruce Allan
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=shsy9dkwuuk.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=nfs@lists.sourceforge.net \
--cc=trmcneal@attbi.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.