public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: davidsen@tmr.com (bill davidsen)
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0 NFS-server low to 0 performance
Date: 7 Jan 2004 22:30:05 GMT	[thread overview]
Message-ID: <bti19d$7fn$1@gatekeeper.tmr.com> (raw)
In-Reply-To: Pine.LNX.4.44.0401071431520.479-100000@poirot.grange

In article <Pine.LNX.4.44.0401071431520.479-100000@poirot.grange>,
Guennadi Liakhovetski  <g.liakhovetski@gmx.de> wrote:
| On Tue, 6 Jan 2004, Guennadi Liakhovetski wrote:
| 
| > server with 2.6.0 kernel:
| >
| > fast:2.6.0-test11	2m21s (*)
| > fast:2.4.20		16.5s
| > SA1100:2.4		never finishes (*)
| > PXA:2.4.21-rmk1-pxa1	as above
| > PXA:2.6.0-rmk1-pxa	as above
| >
| > server: 2.4.21
| >
| > fast:2.6.0-test11	6s
| > fast:2.4.20		5s
| > SA1100:2.4.19-rmk7	3.22s
| > PXA:2.4.21-rmk1-pxa1	7s
| > PXA:2.6.0-rmk2-pxa	1) 50s (**)
| > (***)			2) 27s (**)
| 
| s/fast/PC2/
| 
| Further, I tried the old 3c59x card - same problems persist. Also tried
| PC2 as the server - same. nfs-utils version 1.0.6 (Debian Sarge). I sent a
| copy of the yesterday's email + new details to nfs@lists.sourceforge.net,
| netdev@oss.sgi.com, linux-net@vger.kernel.org.
| 
| Strange, that nobody is seeing this problem, but it looks pretty bad here.
| Unless I missed some necessary update somewhere? The only one that seemed
| relevant - nfs-utils on the server(s) from Documentation/Changes I
| checked.

I'm sure you checked this, but does mii-tool show that you have
negotiated the proper connection to the hub or switch? I found that my
3cXXX and eepro100 cards were negotiating half duplex with the switches
and cable modems, causing the throughput to go forth and conjugate the
verb "to suck" until I fixed it.
-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.

  reply	other threads:[~2004-01-07 22:42 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-06  0:46 2.6.0 NFS-server low to 0 performance Guennadi Liakhovetski
2004-01-07 13:36 ` Guennadi Liakhovetski
2004-01-07 22:30   ` bill davidsen [this message]
2004-01-08 12:48     ` Guennadi Liakhovetski
2004-01-07 17:49 ` Mike Fedyk
2004-01-07 18:13   ` Guennadi Liakhovetski
2004-01-07 18:19     ` Mike Fedyk
2004-01-07 19:06       ` Guennadi Liakhovetski
2004-01-09 10:08         ` Guennadi Liakhovetski
2004-01-09 18:00           ` Mike Fedyk
2004-01-10  0:38             ` Guennadi Liakhovetski
2004-01-10  1:38               ` Mike Fedyk
2004-01-10 11:10                 ` Guennadi Liakhovetski
2004-01-10 14:30                   ` Trond Myklebust
2004-01-10 20:04                     ` Guennadi Liakhovetski
2004-01-10 21:57                       ` Trond Myklebust
2004-01-10 22:14                         ` Mike Fedyk
2004-01-10 22:47                           ` Trond Myklebust
2004-01-10 22:42                         ` Guennadi Liakhovetski
2004-01-10 22:51                           ` Jesper Juhl
2004-01-11 13:18                           ` Helge Hafting
2004-01-11 13:53                             ` Russell King
2004-01-11 14:24                               ` Guennadi Liakhovetski
2004-01-15 11:38                               ` Pavel Machek
2004-01-12  5:06                     ` Bill Davidsen
2004-01-12 14:27                       ` Trond Myklebust
2004-01-12 15:12                         ` Trond Myklebust
2004-01-16  5:44                           ` Mike Fedyk
2004-01-16  6:05                             ` Trond Myklebust
2004-01-16  6:53                               ` Mike Fedyk
2004-01-10 22:34                   ` Mike Fedyk
2004-01-10 22:52                     ` Guennadi Liakhovetski
2004-01-10 22:57                       ` Mike Fedyk
2004-01-10 23:00                         ` Guennadi Liakhovetski
2004-01-08 21:42     ` Pavel Machek
2004-01-12 23:18       ` Guennadi Liakhovetski
2004-01-12 23:28         ` Jesper Juhl
2004-01-13  0:39         ` Pavel Machek
2004-01-14  3:00           ` Daniel Roesen
2004-01-14 18:16           ` Guennadi Liakhovetski
2004-01-13  1:55 ` Slow NFS performance over wireless! Roman Gaufman
2004-01-13  2:15   ` Trond Myklebust
2004-01-13 20:25   ` Joshua M. Thompson
2004-01-13 20:45     ` Trond Myklebust
2004-01-15  1:12       ` Miquel van Smoorenburg
     [not found]         ` <20040115013312.GO1594@srv-lnx2600.matchmail.com>
2004-01-15  2:04           ` Miquel van Smoorenburg
2004-01-15  2:35         ` Trond Myklebust
2004-01-15 19:00           ` Slowwwwwwwwwwww NFS read performance Trond Myklebust
2004-01-15 19:53             ` Ram Pai
2004-01-15 20:16               ` Trond Myklebust
2004-01-15 20:54                 ` Trond Myklebust
2004-01-18  6:04             ` Greg Fitzgerald
2004-01-18 17:55               ` Mike Fedyk
2004-01-16  0:52           ` Slow NFS performance [was: over wireless!] Miquel van Smoorenburg
     [not found] <1cpDr-5az-11@gated-at.bofh.it>
     [not found] ` <1csrv-Er-9@gated-at.bofh.it>
2004-01-10 16:08   ` 2.6.0 NFS-server low to 0 performance Andi Kleen
2004-01-10 16:19     ` Trond Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2004-01-12 14:40 James Pearson
2004-01-12 15:22 ` Trond Myklebust
2004-01-13 11:08   ` Muli Ben-Yehuda

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='bti19d$7fn$1@gatekeeper.tmr.com' \
    --to=davidsen@tmr.com \
    --cc=linux-kernel@vger.kernel.org \
    /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