From: David Miller <davem@davemloft.net>
To: khc@pm.waw.pl
Cc: netdev@vger.kernel.org
Subject: Re: netdevice queueing / sendmsg issue?
Date: Sat, 28 Jul 2007 22:49:59 -0700 (PDT) [thread overview]
Message-ID: <20070728.224959.74562336.davem@davemloft.net> (raw)
In-Reply-To: <m3lkd0upx8.fsf@maximus.localdomain>
From: Krzysztof Halasa <khc@pm.waw.pl>
Date: Sun, 29 Jul 2007 00:25:07 +0200
> I wonder if it's dev_kfree_skb_irq() which should but fails to wake
> the thing up?
Software interrupts might be getting lost, dev_kfree_skb_irq() has to
queue the kfree_skb() to soft IRQ.
Therefore, dev_kfree_skb_irq() will only work properly from hardware
interrupt context, where we will return and thus run the scheduled
software interrupt.
So some things to check out are whether the driver is invoking
dev_kfree_skb_irq() in the right context, whether ARM might have some
software interrupt processing preculiarity, etc.
next prev parent reply other threads:[~2007-07-29 5:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 22:25 netdevice queueing / sendmsg issue? Krzysztof Halasa
2007-07-29 5:49 ` David Miller [this message]
2007-07-29 21:03 ` Krzysztof Halasa
2007-08-03 22:18 ` Krzysztof Halasa
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=20070728.224959.74562336.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=khc@pm.waw.pl \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).