Linux NFS development
 help / color / mirror / Atom feed
From: Matthias Kittner <kittner@vrcom.de>
To: nfs@lists.sourceforge.net
Subject: Linux client network performance
Date: Wed, 25 Jun 2003 10:56:56 +0200	[thread overview]
Message-ID: <3EF963D8.9010204@vrcom.de> (raw)

[I am not a subscriber, please CC to my eMail!]

Hello,

we have the following problem:

- 2 linux clients:
	2.4.19-16mdk
	2.4.20
- Solaris NFS-Server (nfs.server 1.21)
	SunOS 5.7

If we compile on one of the linux machines sometimes in this compile 
process the whole network hangs resp. is so slow that one can wait 
between 10s or 2min to finish a "ls".

"snoop" at the nfs-server machine show very/very much "UDP continuation" 
traffic between the linux client and the solaris server. Killing the 
compile process stops this messages.

Can anyone help us? Is this a configuration problem or a bug?

Regards,
Matthias



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-06-25  8:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-25  8:56 Matthias Kittner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-25 14:29 Linux client network performance Lever, Charles
2003-06-25 14:58 Brasseur Valéry
2003-06-25 17:39 Lever, Charles
2003-06-25 18:09 s o f i a
2003-06-25 19:40 Lever, Charles
2003-06-26 16:50 ` s o f i a
2003-06-27  9:29 ` Matthias Kittner

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=3EF963D8.9010204@vrcom.de \
    --to=kittner@vrcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox