From: Mike Fedyk <mfedyk@matchmail.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: linux-kernel@vger.kernel.org, Sam Vilain <sam@hydro.gen.nz>
Subject: Re: 2.6.0 NFS-server low to 0 performance
Date: Fri, 9 Jan 2004 10:00:54 -0800 [thread overview]
Message-ID: <20040109180054.GV1882@matchmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401091031010.18195-100000@poirot.grange>
On Fri, Jan 09, 2004 at 11:08:29AM +0100, Guennadi Liakhovetski wrote:
> On Wed, 7 Jan 2004, Mike Fedyk wrote:
>
> > Just post a few samples of the lines that differ. Any files should be sent
> > off-list.
>
> Ok, This is the problem:
>
> 10:38:30.867306 0:40:f4:23:ac:91 0:50:bf:a4:59:71 ip 590: tuxscreen.grange > poirot.grange: icmp: ip reassembly time exceeded [tos 0xc0]
>
> A similar effect was reported in 1999 with kernel 2.3.13, also between 2
> 100mbps cards. It also was occurring with UDP NFS:
>
> http://www.ussg.iu.edu/hypermail/linux/net/9908.2/0039.html
>
> But there were no answers, so, I am CC-ing Sam, hoping to hear, if he's
> found the reason and a cure for his problem. Apart from this message I
> didn't find any other relevant hits with Google.
>
> Is it some physical network problem, which somehow only becomes visible
> under 2.6 now, with UDP (NFS) with 100mbps?
Find out how many packets are being dropped on your two hosts with 2.4 and
2.6.
If they're not dropping packets, maybe the ordering with a large backlog has
chagned between 2.4 and 2.6 that would keep some of the fragments from being
sent in time...
next prev parent reply other threads:[~2004-01-09 18:01 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
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 [this message]
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=20040109180054.GV1882@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@hydro.gen.nz \
/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