All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: nfs performance: read only/gigE/nolock/1Tb per day
Date: 23 Apr 2002 18:36:28 +0200	[thread overview]
Message-ID: <shsznzubcdv.fsf@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0204231502320.31993-100000@kenzo.iwr.uni-heidelberg.de>

>>>>> " " == Bogdan Costescu <bogdan.costescu@iwr.uni-heidelberg.de> writes:

     > How big are the datagrams compared with the MTU ? With 32K
     > datagrams over Ethernet, you're talking about roughly a full Rx
     > ring worth of packets (32 is common for the Rx ring size)...

It has been a while ago (I've since mothballed the machine) but I saw
it on a Pentium 90 with only 8k write sizes. 4k was fine, 8k gave
avalanches.

    >> IOW: the client is just sitting there sending off ICMP
    >> messages, and never reading the reply.

     > Does the other side sees these messages ? If so, are there any
     > response messages sent out (but which don't make it back to the
     > client) ?

IIRC, yes, and the server was resending the datagrams. From the code,
it looks as if there is no attempt to stop loopback situations
occurring when this goes on:
i.e. resending an ICMP when the server resends a datagram which times
out again appears to be possible. This might be what was happening...

     > Down/up was on the sending or receiving/reassembling side ?

Down/up on the receiving/reassembling side.

Cheers,
  Trond

_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2002-04-23 16:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-22 14:49 nfs performance: read only/gigE/nolock/1Tb per day Lever, Charles
2002-04-22 15:32 ` Trond Myklebust
2002-04-22 18:52   ` Bogdan Costescu
2002-04-23 10:39     ` Trond Myklebust
2002-04-23 15:14       ` Bogdan Costescu
2002-04-23 16:36         ` Trond Myklebust [this message]
2002-04-23 18:16           ` Bogdan Costescu
2002-04-23 18:16           ` [NFS] " Bogdan Costescu
  -- strict thread matches above, loose matches on Subject: below --
2002-04-22 21:45 Heflin, Roger A.
2002-04-22 16:23 Andrew Ryan
2002-04-22 18:06 ` Pedro M. Rodrigues
2002-04-21 13:08 Gavin Woodhatch
2002-04-21  3:27 jason andrade

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=shsznzubcdv.fsf@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=bogdan.costescu@iwr.uni-heidelberg.de \
    --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.