All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Steve Dickson <SteveD@RedHat.com>
Cc: NFS maillist <nfs@lists.sourceforge.net>
Subject: Re: NFS/UDP slow read, lost fragments
Date: Tue, 14 Oct 2003 23:27:14 -0400	[thread overview]
Message-ID: <16268.48786.711440.214276@charged.uio.no> (raw)
In-Reply-To: <3F8CBC39.3020002@RedHat.com>

>>>>> " " == Steve Dickson <SteveD@RedHat.com> writes:

     > Trond Myklebust wrote:

    >> Could you try using the slight variation in
    >>
    >>
     > It didn't seem to help much... here the numbers...

Oh well, a 1.5% retransmission rate is in any case not a major
problem. It is more than we should see given that we are setting a
timeout of > 4 standard deviations, but it is consistent with what I
see in my own tests...

Cheers,
  Trond


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2003-10-15  3:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25 17:59 NFS/UDP slow read, lost fragments Robert L. Millner
2003-09-25 20:22 ` Brian Mancuso
2003-09-25 20:33 ` brianm
2003-09-25 21:44 ` Brian Mancuso
2003-09-25 23:31   ` Trond Myklebust
2003-09-26 21:07     ` Brian Mancuso
2003-09-27  5:02       ` Robert L. Millner
2003-10-14  1:20       ` Steve Dickson
2003-10-14 14:52         ` Trond Myklebust
2003-10-15  3:17           ` Steve Dickson
2003-10-15  3:27             ` Trond Myklebust [this message]
2003-09-25 20:11 Lever, Charles

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=16268.48786.711440.214276@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=SteveD@RedHat.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.