From: Brice Goglin <brice@myri.com>
To: David Miller <davem@davemloft.net>
Cc: jeff@garzik.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [git patches] net driver updates for .28
Date: Sat, 20 Sep 2008 09:28:24 +0200 [thread overview]
Message-ID: <48D4A618.5080403@myri.com> (raw)
In-Reply-To: <20080920.000914.219711773.davem@davemloft.net>
David Miller wrote:
> No, that is crap. I didn't create the ->select_tx_queue() callback so
> that each and every damn multiqueue driver will override the generic
> TX hash function in order to try and make the TX hashing match the RX
> hashing.
>
> That's not what it's for.
>
> The callback exists for things like wireless where the queues have
> a meaning other than flow seperation.
>
> We (specifically Herbert Xu and myself) know that for routing and
> firewalling applications matching the TX queue to the same hashing
> namespace of the RX multiqueueing is desirable for best performance.
>
> But we will do that generically by allowing the driver on the receive
> side to record the RX hash used (or alternatively, if the exact RSS
> hash isn't obtainable, the RX queue index itself) and on TX we will
> use this information to select the TX queue properly.
>
Ok, I'll resend without the select_queue stuff. But you should really
document the above explanation. The only documentation we found was
"Devices or device layers can set this to control the queue selection
performed by dev_pick_tx()." in the git-log...
Brice
next prev parent reply other threads:[~2008-09-20 7:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-14 2:22 [git patches] net driver updates for .28 Jeff Garzik
2008-09-20 7:09 ` David Miller
2008-09-20 7:28 ` Brice Goglin [this message]
2008-09-20 10:33 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-09-24 23:07 Jeff Garzik
2008-09-24 23:21 ` David Miller
2008-09-25 6:55 ` Sebastien Dugue
2008-09-25 17:38 ` Jeff Garzik
2008-09-25 20:07 ` David Miller
2008-09-03 14:37 Jeff Garzik
2008-09-03 22:08 ` 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=48D4A618.5080403@myri.com \
--to=brice@myri.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.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).