From: Andi Kleen <ak@suse.de>
To: Oleg Makarenko <omakarenko@cyberplat.ru>
Cc: linux-kernel@vger.kernel.org, ipv4@mail.ru,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: netif_wake_queue wrong was Re: [PATCH] NFS Server performance and 8139too
Date: Sun, 13 May 2001 12:53:29 +0200 [thread overview]
Message-ID: <20010513125329.B10250@gruyere.muc.suse.de> (raw)
In-Reply-To: <3AFE3870.3BB1B69@cyberplat.ru>
In-Reply-To: <3AFE3870.3BB1B69@cyberplat.ru>; from omakarenko@cyberplat.ru on Sun, May 13, 2001 at 11:32:00AM +0400
On Sun, May 13, 2001 at 11:32:00AM +0400, Oleg Makarenko wrote:
> 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 :)
The problem is that the netif_wake_queue() 2.4 compatibility macro that
was recently added to 2.2 was wrong. It should do a mark_bh(). 8139too
uses the 2.4 macros, and therefore the netbh was always scheduled for too
late and performance was bad.
This patch should fix all drivers that use the new framework.
--- linux/include/linux/kcomp.h Tue Dec 19 17:57:30 2000
+++ linux-work/include/linux/kcomp.h Sun May 13 13:01:11 2001
@@ -17,7 +17,7 @@
#define net_device device
#define dev_kfree_skb_irq(a) dev_kfree_skb(a)
-#define netif_wake_queue(dev) clear_bit(0, &dev->tbusy)
+#define netif_wake_queue(dev) do { clear_bit(0, &dev->tbusy); mark_bh(NET_BH); } while(0)
#define netif_stop_queue(dev) set_bit(0, &dev->tbusy)
#define netif_start_queue(dev) do { dev->tbusy = 0; dev->interrupt = 0; dev->start = 1; } while (0)
#define netif_queue_stopped(dev) dev->tbusy
-Andi
next prev parent reply other threads:[~2001-05-13 10:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-13 7:32 Oleg Makarenko
2001-05-13 10:53 ` Andi Kleen [this message]
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=20010513125329.B10250@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ipv4@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=omakarenko@cyberplat.ru \
/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®