From: Steve Wise <swise@opengridcomputing.com>
To: Mark Huth <mhuth@mvista.com>
Cc: netdev@vger.kernel.org
Subject: Re: netpoll question
Date: Wed, 28 Mar 2007 20:00:33 -0500 [thread overview]
Message-ID: <1175130033.28767.19.camel@stevo-laptop> (raw)
In-Reply-To: <460AFA3B.6090009@mvista.com>
On Wed, 2007-03-28 at 16:28 -0700, Mark Huth wrote:
> Steve Wise wrote:
> > Hey all,
> >
> > I have netpoll question. How does netpoll work with MSI/X, NAPI, and
> > nics that setup multiple RSS style receive queues for a single port?
> > >From what I can tell, if you're doing something like netdump using
> > netpoll for IO, then you might never process incoming packets that get
> > posted to the rx queues not associated with the main netdevice structure
> > because netpoll only calls the poll() function for the main netdev
> > struct. Not the dummy netdevs setup for multiple rx queues.
> >
> > Is this the case or am I confused?
> >
> > Thanks,
> >
> >
> > Steve
> You are correct. Netpoll needs a bit of work, especially on the receive
> side, for multi-queue and some other possible problems related to taking
> locks when the system is frozen. If I get some time soon, I'm going to
> propose an overhaul to address some of these issues that show up in the
> kgdboe and netdump cases.
>
> Mark Huth
Hey Mark,
What are your thoughts on how to implement this?
Scrub every softnet_data queue->poll_list for every cpu? Or perhaps its
better to have a new function ptr off the netdev that sez "poll all rx
queues"?
Steve.
next prev parent reply other threads:[~2007-03-29 1:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 22:03 netpoll question Steve Wise
2007-03-28 23:28 ` Mark Huth
2007-03-29 1:00 ` Steve Wise [this message]
2007-03-29 1:08 ` Stephen Hemminger
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=1175130033.28767.19.camel@stevo-laptop \
--to=swise@opengridcomputing.com \
--cc=mhuth@mvista.com \
--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