From: Jeff Moyer <jmoyer@redhat.com>
To: mpm@selenic.com
Cc: linux-kernel@vger.kernel.org
Subject: netpoll trapped question
Date: Tue, 31 Aug 2004 13:10:43 -0400 [thread overview]
Message-ID: <16692.45331.968648.262910@segfault.boston.redhat.com> (raw)
Hi, Matt,
This part of the netpoll trapped logic seems suspect to me, from
include/linux/netdevice.h:
static inline void netif_wake_queue(struct net_device *dev)
{
#ifdef CONFIG_NETPOLL_TRAP
if (netpoll_trap())
return;
#endif
if (test_and_clear_bit(__LINK_STATE_XOFF, &dev->state))
__netif_schedule(dev);
}
static inline void netif_stop_queue(struct net_device *dev)
{
#ifdef CONFIG_NETPOLL_TRAP
if (netpoll_trap())
return;
#endif
set_bit(__LINK_STATE_XOFF, &dev->state);
}
This looks buggy. Network drivers are now not able to stop the queue when
they run out of Tx descriptors. I think the __netif_schedule is okay to do
in the context of netpoll, and certainly a set_bit is okay. Why are these
hooks in place? I've tested alt-sysrq-t over netconsole and also netdump
with these #ifdef's removed, and things work correctly. Compare this with
alt-sysrq-t hanging the system with these tests in place. If I run netdump
with this logic still in place, I get the following messages from the tg3
driver:
eth0: BUG! Tx Ring full when queue awake!
Shall I send a patch, or have I missed something?
-Jeff
next reply other threads:[~2004-08-31 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 17:10 Jeff Moyer [this message]
2004-09-06 21:35 ` Matt Mackall
2004-09-07 16:33 ` Jeff Moyer
2004-09-07 16:50 ` Matt Mackall
2004-09-07 16:53 ` Jeff Moyer
2004-09-07 16:59 ` Matt Mackall
2004-09-07 17:10 ` Jeff Moyer
2004-09-07 17:22 ` Matt Mackall
2004-09-08 8:22 ` Herbert Xu
2004-09-08 8:34 ` Herbert Xu
2004-09-08 11:54 ` Jeff Moyer
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=16692.45331.968648.262910@segfault.boston.redhat.com \
--to=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
/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®