From: Bill Davidsen <davidsen@tmr.com>
To: Thomas Schlichter <schlicht@rumms.uni-mannheim.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.5.60-mm2
Date: Mon, 17 Feb 2003 13:32:21 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.1030217132545.32676A-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <1045485310.3e50d6fe94f1e@rumms.uni-mannheim.de>
On Mon, 17 Feb 2003, Thomas Schlichter wrote:
> Quoting Bill Davidsen <davidsen@tmr.com>:
> > > I was looking for network issues when I started timing pings, and didn't
> > > see any. I thought it was bad timing, like not raining when you have a
> > > coat, but maybe I was curing it.
> >
> > Since it's possible that pings will actually change the problem rather
> > than measure it, I'll tcpdump for a while and see if that tells me
> > anything. I suspected network problems, since tcp has priority over udp in
> > some places.
> >
> > I looked at the code last night, but I don't see anything explaining a
> > ping making things better. Something getting flushed?
>
> I'm sorry, I don't exactly know what you want me to do... I'm not involved in
> the linux net code and I did not even try to understand it yet...
Thanks, you've already done it! I assumed that when I didn't see any
problems while the ping was running that it was just bad timing, and the
problem didn't happen while I was looking. Your note that the pinging
actually prevents the problem gives me something new to investigate.
> I just have a small environment with a FreeBSD 4.6 box using my Linux box as a
> NFS file server. This worked fine with my 2.4 kernel but with the 2.5.x test
> kernels I've got the problem the FreeBSD box says 'NFS server not responding'
> until I do simple pings (ICMP echo request, ICMP echo respond) to the linux box
> (the NFS server)...
>
> Letting the ping run all the time NFS works so stable I even can do lots of
> compilations over it without any problems.
>
> So I don't have any answer WHY this helps, but it does... Perhaps it really is
> just a timing issue, I just don't know... If you can tell me what to measure and
> which values would be interesting I'll do these tests and send you the
> results...
I someone can suggest "what to do" I'll do it as well. At the moment I'm
building a table of 2.5.59 client against 2.4.19, AIX, BSD, etc, and vice
versa. I am looking for hangs with and without the ping running, in hopes
that the results will be useful, possibly to me but more likely to someone
who can see what's happening.
For the record, I see severe hangs with 2.4.19 server and 2.5.59 client,
I'll know what effect the ping has in a few minutes.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-02-17 18:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 9:31 2.5.60-mm2 Andrew Morton
2003-02-14 9:38 ` 2.5.60-mm2 Dave Jones
2003-02-14 9:58 ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:13 ` 2.5.60-mm2 Dave Jones
2003-02-14 10:22 ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:10 ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 1:59 ` 2.5.60-mm2 Bill Davidsen
2003-02-17 12:08 ` 2.5.60-mm2 Bill Davidsen
2003-02-17 12:35 ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 18:32 ` Bill Davidsen [this message]
2003-02-14 20:59 ` compile fail: 2.5.60-mm2 Core
2003-02-14 22:06 ` Andrew Morton
2003-02-15 20:27 ` 2.5.60-mm2 Arador
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=Pine.LNX.3.96.1030217132545.32676A-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=schlicht@rumms.uni-mannheim.de \
/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