From: dwight@supercomputer.org
To: nfs@lists.sourceforge.net
Subject: Re: RE: Linux client on Solaris 7 NFS server
Date: Mon, 05 Jan 2004 23:38:17 -0800 [thread overview]
Message-ID: <200401060738.i067cHF16900@supercomputer.org> (raw)
In-Reply-To: Message from "Lever, Charles" <Charles.Lever@netapp.com> of "Mon, 05 Jan 2004 10:21:59 PST." <482A3FA0050D21419C269D13989C6113020AC981@lavender-fe.eng.netapp.com>
Hi Charles,
I actually have lots of data on this, since I ran tcpdump on every major
run when I was gathering data. Each tcpdump output file is about 20 MB.
That's the good news. =
The bad news is I don't know if I can release that specific data. My =
guess is that I'll have to cut over to a totally isolated subnet and =
rerun things. =
However, if such data can be released, and if there's enough interest in
looking the tcpdump output, I'd be willing to go to the efforts of doing =
so for those who'd be interested in looking at the tcpdump data.
So I'll investigate further. =
Best Regards,
-dwight-
From: "Lever, Charles" <Charles.Lever@netapp.com>
Date: Mon, 5 Jan 2004 10:21:59 -0800
> hi dwight-
> =
> please capture some network traces of both a fast run and
> a slow run (using UDP for both, preferrably). the traces
> don't need to be large (in the neighborhood of 10MB), but
> they do need to be raw format, and be sure you capture
> at least 256 bytes of each frame (-s256).
> =
> the v2/v3 performance delta is usually a red herring; it
> is almost always the result of some other problem.
> =
-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills. Sign up for IBM's
Free Linux Tutorials. Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-01-06 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Charles.Lever@netapp.com>
2004-01-05 18:21 ` RE: Linux client on Solaris 7 NFS server Lever, Charles
2004-01-06 7:38 ` dwight [this message]
2003-12-30 17:58 Lever, Charles
2004-01-05 17:11 ` dwight
2004-01-06 4:57 ` Ian Kent
-- strict thread matches above, loose matches on Subject: below --
2003-12-30 15:50 Lever, Charles
2003-12-30 17:44 ` dwight
2003-12-31 1:55 ` Ian Kent
2004-01-05 17:31 ` dwight
2004-01-05 19:46 ` Wade Hampton
2004-01-05 22:34 ` Wade Hampton
2004-01-06 4:59 ` Ian Kent
2004-01-06 7:41 ` dwight
2004-01-06 4:42 ` Ian Kent
2004-01-07 18:17 ` dwight
2004-01-08 0:32 ` Ian Kent
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=200401060738.i067cHF16900@supercomputer.org \
--to=dwight@supercomputer.org \
--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.