From: Francois Romieu <romieu@fr.zoreil.com>
To: Marcus Blomenkamp <Marcus.Blomenkamp@epost.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: r8169 GigE driver problem, locks up 2.4.23 NFS subsystem
Date: Thu, 18 Dec 2003 01:45:37 +0100 [thread overview]
Message-ID: <20031218014537.A8113@electric-eye.fr.zoreil.com> (raw)
In-Reply-To: <200312151124.15143.Marcus.Blomenkamp@epost.de>; from Marcus.Blomenkamp@epost.de on Mon, Dec 15, 2003 at 11:24:15AM +0100
Marcus Blomenkamp <Marcus.Blomenkamp@epost.de> :
[...]
> I tcpdump'ed both sides on transferring 1 Megabyte to the 8139 based machine
> for both low level transfers (UDP, TCP) and on filesystem level (NFS).
>
> NFS: dd 1M to remote file
> UDP/TCP: dd 1M trough netcat
> TCP: scp 1M file
>
> Very interestingly i could not reproduce the NFS lockup during this double
> monitoring setup. So i ran it twice - once for each machine in promiscious
> mode. And guess: If the 8169 NIC is in monitoring mode, NFS writes do not
> lock up. I can even recover the machine from stalling by explicitly entering
> promiscious mode and SIGINT'ing the writing process.
The dumps show that the server misses frames and/or sees generous amount
of garbage during UDP transfer. Which transfer rate can you achieve for big
writes between 8129 ?
Can you:
- retrieve the ifconfig output on the client/server just before and after the
write (8192 sized NFS from 8169 to 8139) ?
- send a dump of a 8192 bytes sized 1Mo write from 8139 to 8139 ?
--
Ueimor
next prev parent reply other threads:[~2003-12-18 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-13 13:01 Francois Romieu
2003-12-13 13:54 ` Marcus Blomenkamp
[not found] ` <20031214144055.A4664@electric-eye.fr.zoreil.com>
2003-12-15 10:24 ` Marcus Blomenkamp
2003-12-15 18:58 ` Francois Romieu
2003-12-18 0:45 ` Francois Romieu [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-13 12:00 Marcus Blomenkamp
2003-12-14 2:02 ` Jeff Garzik
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=20031218014537.A8113@electric-eye.fr.zoreil.com \
--to=romieu@fr.zoreil.com \
--cc=Marcus.Blomenkamp@epost.de \
--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
all inboxes | Powered by JetHome®