From: Hariprasad Nellitheertha <hari@in.ibm.com>
To: linux-net@vger.kernel.org, linux-kernel@vger.kernel.org,
mpm@selenic.com, mingo@elte.hu, suparna@in.ibm.com
Subject: Problem with Netpoll based netdumping and NAPI
Date: Mon, 19 Apr 2004 18:21:48 +0530 [thread overview]
Message-ID: <20040419125148.GA4495@in.ibm.com> (raw)
Hi All,
I am facing a problem while trying to network dump using LKCD. My
debugging so far indicates that this is due to both NAPI and NETPOLL
being enabled.
I am using LKCD on the 2.6.5 kernel and both the client and server are
i386 boxes. The dumping machine has an e100 card. I have built the kernel
with both CONFIG_E100_NAPI and CONFIG_NET_POLL_CONTROLLER (and the other
netpoll related options) selected.
LKCD uses netpoll for its network dump implementation. The problem we see
is that the network dump driver does not receive any packet from the
card driver and hence dumping fails. In e100_intr(), we call
netif_rx_schedule() if we are using the NAPI feature. netif_rx_schedule,
in turn, ends up adding the processing of this packet to the NET_RX_SOFTIRQ
softirq.
When we do netdump, all the other cpus are halted and interrupts disabled.
So, we never get around to scheduling the ksoftirqd thread and these packets
are never processed. I think any one using netpoll with NAPI logic turned on
will face this problem.
One way I worked around this was to avoid the NAPI logic when we end up
in e100_intr() due to netpoll. But I think a better solution would be to
let the NAPI code handle this.
Request all to comment and suggest an effective way to fix this problem.
Thanks in advance.
Regards, Hari
--
Hariprasad Nellitheertha
Linux Technology Center
India Software Labs
IBM India, Bangalore
next reply other threads:[~2004-04-19 12:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 12:51 Hariprasad Nellitheertha [this message]
2004-04-19 17:42 ` Matt Mackall
2004-04-21 6:00 ` Hariprasad Nellitheertha
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=20040419125148.GA4495@in.ibm.com \
--to=hari@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mpm@selenic.com \
--cc=suparna@in.ibm.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®