From: Oleg Makarenko <omakarenko@cyberplat.ru>
To: linux-kernel@vger.kernel.org
Cc: ipv4@mail.ru
Subject: [PATCH] NFS Server performance and 8139too
Date: Sun, 13 May 2001 11:32:00 +0400 [thread overview]
Message-ID: <3AFE3870.3BB1B69@cyberplat.ru> (raw)
[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]
Since 2.2.19 I have a very poor NFS server performance on Linux
using 8139too driver (v0.9.14) while the driver v0.9.10 from 2.2.18
works fine (even with 2.2.19)
I have checked 2.2.20pre2 and 8139too project pages and found no patches
for the problem. Am I alone with that bad NFS performance here?
My setup:
PII-500, 196M, Linux 2.2.19. rh6.2, 8139too,
serves as NFS server and client for SCO OpenServer and file server and
client
for macintosh
the following command on SCO:
sco# cat /mnt/linux/one-megabyte-file > /dev/null
takes about 30 minutes with 2.2.19 kernel and about 0.3 secs on 2.2.18.
(I have never made the real benchmarks, numbers are just to show the
difference)
The following one line patch puts performance of 2.2.19 back to
2.2.18 for me and I use it for a week without any problems.
Beware that I am not a kernel hacker so the patch can be completely
wrong. But I hope it still can provide some useful information to
somebody who really knows what is going on here :)
oleg
[-- Attachment #2: linux-2.2.19-8139too.patch --]
[-- Type: application/octet-stream, Size: 265 bytes --]
--- linux-2.2.19/drivers/net/8139too.c Sun Mar 25 20:37:34 2001
+++ linux-mole/drivers/net/8139too.c Sat May 12 18:27:48 2001
@@ -1808,6 +1808,7 @@
tp->dirty_tx = dirty_tx;
if (netif_queue_stopped (dev))
netif_wake_queue (dev);
+ mark_bh(NET_BH);
}
}
next reply other threads:[~2001-05-13 7:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-13 7:32 Oleg Makarenko [this message]
2001-05-13 10:53 ` netif_wake_queue wrong was Re: [PATCH] NFS Server performance and 8139too Andi Kleen
2001-05-14 11:40 ` netif_wake_queue wrong was: " Oleg Makarenko
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=3AFE3870.3BB1B69@cyberplat.ru \
--to=omakarenko@cyberplat.ru \
--cc=ipv4@mail.ru \
--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