From: Stephen Hemminger <shemminger@vyatta.com>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>
Cc: "Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
David Miller <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>
Subject: Re: [PATCH 2/2] ixgbe: fix select_queue management
Date: Fri, 20 Mar 2009 09:24:34 -0700 [thread overview]
Message-ID: <20090320092434.7ac1baf3@nehalam> (raw)
In-Reply-To: <Pine.WNT.4.64.0903200019240.14460@ppwaskie-MOBL2.amr.corp.intel.com>
On Fri, 20 Mar 2009 00:23:39 -0700 (Pacific Daylight Time)
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com> wrote:
> On Thu, 19 Mar 2009, Stephen Hemminger wrote:
>
> > Convert ixgbe to use net_device_ops properly.
> > Rather than changing the select_queue function pointer
> > just check the flag.
> >
> > Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
>
> Thanks Stephen. I was looking at reassigning a DCB netdev_ops struct when
> DCB is enabled, and then having a default netdev_ops struct when it's not
> enabled. I agree the check is cleaner the way you have it below, but it's
> another conditional check in the Tx hotpath, which we have too many of in
> the first place.
Changing number of tx queues is actually the fastest, since then
indirection is not needed
> On a related side note, why is the netdev_ops member of net_device
> declared const?
The purpose of having an ops structure is two fold. First, the ops
can be in read-only section (if driver wants) to avoid cache issues.
More importantly only one instance is necessary when there are multiple
boards, or 1000's of vlans.
> Cheers,
> -PJ Waskiewicz
next prev parent reply other threads:[~2009-03-20 16:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 6:34 [PATCH 1/2] skb: expose and constify hash primitives Stephen Hemminger
2009-03-20 6:36 ` [PATCH 2/2] ixgbe: fix select_queue management Stephen Hemminger
2009-03-20 7:23 ` Waskiewicz Jr, Peter P
2009-03-20 16:24 ` Stephen Hemminger [this message]
2009-03-20 17:14 ` Waskiewicz Jr, Peter P
2009-03-21 0:24 ` Jeff Kirsher
2009-03-21 20:40 ` David Miller
2009-03-20 16:12 ` [PATCH 2/2] ixgbe: fix select_queue management (v2) Stephen Hemminger
2009-03-21 3:48 ` Waskiewicz Jr, Peter P
2009-03-21 4:45 ` Stephen Hemminger
2009-03-21 6:21 ` Waskiewicz Jr, Peter P
2009-03-21 7:33 ` David Miller
2009-03-21 7:43 ` Waskiewicz Jr, Peter P
2009-03-21 19:39 ` Stephen Hemminger
2009-03-22 1:48 ` Waskiewicz Jr, Peter P
2009-03-22 2:00 ` David Miller
2009-03-21 20:39 ` [PATCH 1/2] skb: expose and constify hash primitives David Miller
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=20090320092434.7ac1baf3@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.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