From: Neil Horman <nhorman@tuxdriver.com>
To: "Veeraiyan, Ayyappan" <ayyappan.veeraiyan@intel.com>
Cc: Jeff Garzik <jeff@garzik.org>,
netdev@vger.kernel.org, "Kok,
Auke-jan H" <auke-jan.h.kok@intel.com>,
arjan@linux.intel.com, akpm@linux-foundation.org
Subject: Re: [PATCH] ixgbe: Introduce new 10GbE driver for Intel 82598 based PCI Express adapters...
Date: Mon, 9 Jul 2007 20:57:25 -0400 [thread overview]
Message-ID: <20070710005725.GA3639@localhost.localdomain> (raw)
In-Reply-To: <E35F4F4D7F6C9E4E826FEC1F86CEF58304209337@orsmsx412.amr.corp.intel.com>
On Mon, Jul 09, 2007 at 07:21:24AM -0700, Veeraiyan, Ayyappan wrote:
> >From: Neil Horman [mailto:nhorman@tuxdriver.com]
> >Replying to myself...
> > I've looked through the driver pretty throughly with regards to
> my
> >above
> >concern, and it appears the driver is reasonably free of netpoll issues
> at
> >the
> >moment, at least as far as what we found in e1000 was concerned. I do
>
> Thanks for reviewing the code..
>
> >however,
> >see a concern in the use of the in_netpoll flag within the driver.
> Given
> >that
> >the primary registered net_device, and all the dummy net_devices in the
> >rx_ring
> >point to the same ixgbe_adapter structure, there can be some level of
> >confusion
> >over weather a given rx queue is in netpoll_mode or not.
>
> The revised driver I am going to post today will not have fake
> netdevs...
>
> >adapter prforms a netpoll, all the individual rx queues will follow the
> >in_netpoll path in the receive path (assuming misx interrupts are
> used).
> >The
> >result I think is the potential for a large amount of packet reordering
> >during a
> >netpoll operation. Perhaps not a serious problem, but likely worth
> looking
>
> Multiple Rx queues are used in non-NAPI mode only, and all Rx queues use
> one netdev (which is associated with the adapter struct). Also, the RSS
> (receive side scaling or rx packet steering) feature is used in multiple
> rx queues mode. In this mode, HW will always select the same Rx queue
> (for a flow) and this should prevent any packet reordering issue.
>
>
> >Neil
>
> Ayyappan
Thank you, I think that satisfies all my concerns.
Regards
Neil
next prev parent reply other threads:[~2007-07-10 1:12 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 23:44 [ANNOUNCE] new driver ixgbe for Intel(R) 10GbE PCI Express adapters Ayyappan.Veeraiyan
2007-06-12 23:44 ` [PATCH] ixgbe: Introduce new 10GbE driver for Intel 82598 based " Ayyappan Veeraiyan
2007-07-02 12:52 ` Jeff Garzik
2007-07-02 14:05 ` Arjan van de Ven
2007-07-02 14:25 ` Jeff Garzik
2007-07-02 14:27 ` Arjan van de Ven
2007-07-02 14:41 ` Jeff Garzik
2007-07-02 14:41 ` Arjan van de Ven
2007-07-02 15:26 ` Kok, Auke
2007-07-02 15:32 ` Jeff Garzik
2007-07-02 15:52 ` Andrew Morton
2007-07-02 16:09 ` Jeff Garzik
2007-07-02 15:54 ` Kok, Auke
2007-07-06 8:46 ` Ingo Oeser
2007-07-02 14:31 ` Arjan van de Ven
2007-07-02 19:00 ` Veeraiyan, Ayyappan
2007-07-02 19:04 ` Ayyappan Veeraiyan
2007-07-02 20:16 ` Christoph Hellwig
2007-07-02 21:09 ` Stephen Hemminger
2007-07-02 21:42 ` Christoph Hellwig
2007-07-02 22:02 ` Kok, Auke
2007-07-02 22:08 ` Jeff Garzik
2007-07-02 22:10 ` Michael Buesch
2007-07-02 22:16 ` Jeff Garzik
2007-07-02 23:57 ` Kok, Auke
2007-07-03 0:11 ` Jeff Garzik
2007-07-03 0:16 ` Inaky Perez-Gonzalez
2007-07-03 13:19 ` Jeff Garzik
2007-07-03 18:24 ` Inaky Perez-Gonzalez
2007-07-05 23:29 ` Jeff Garzik
2007-07-03 0:08 ` Veeraiyan, Ayyappan
2007-07-03 22:01 ` Ayyappan Veeraiyan
2007-07-02 22:56 ` Veeraiyan, Ayyappan
2007-07-03 12:53 ` Neil Horman
2007-07-05 12:37 ` Neil Horman
2007-07-09 14:21 ` Veeraiyan, Ayyappan
2007-07-10 0:57 ` Neil Horman [this message]
2007-06-13 23:05 ` [ANNOUNCE] new driver ixgbe for Intel(R) 10GbE " Francois Romieu
2007-06-13 23:18 ` Kok, Auke
2007-06-14 0:06 ` Ayyappan Veeraiyan
2007-06-14 20:36 ` Francois Romieu
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=20070710005725.GA3639@localhost.localdomain \
--to=nhorman@tuxdriver.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=ayyappan.veeraiyan@intel.com \
--cc=jeff@garzik.org \
--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).