From: David Miller <davem@davemloft.net>
To: bhutchings@solarflare.com
Cc: shemminger@vyatta.com, netdev@vger.kernel.org,
linux-net-drivers@solarflare.com
Subject: Re: [RFC] [PATCH] net: Add support for ndo_select_queue() functions to cache the queue mapping
Date: Wed, 03 Feb 2010 17:47:35 -0800 (PST) [thread overview]
Message-ID: <20100203.174735.50359131.davem@davemloft.net> (raw)
In-Reply-To: <1264703676.2783.44.camel@achroite.uk.solarflarecom.com>
From: Ben Hutchings <bhutchings@solarflare.com>
Date: Thu, 28 Jan 2010 18:34:34 +0000
> On Thu, 2010-01-28 at 10:00 -0800, Stephen Hemminger wrote:
>> Therefore the transmit hash and receiver hash will be different.
>
> The intent here is to make it worthwhile to calculate that expensive
> hash on the TX side.
I would rather something like this be implemented in a way
which is device hash agnostic.
And I believe it is possible to do this.
Anyways, why can't you just propagate the RX queue used by the flow to
the socket TX hash? We already store the RX queue in the SKB on
receive, the socket packet receive handling can simply propagate that
to the TX queue selector.
This would avoid having to do anything special in the driver's select
queue method. In any event, overriding the queue selection method,
while not absolutely forbidden, is very much discouraged. And if
this new scheme of yours creates another reason drivers will start
to override it, that's another negative in my book.
But most importantly, the last thing we want to do is calculate
something insane like Toeplitz, even if it's just once per connection.
next prev parent reply other threads:[~2010-02-04 1:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-28 17:38 [RFC] [PATCH] net: Add support for ndo_select_queue() functions to cache the queue mapping Ben Hutchings
2010-01-28 18:00 ` Stephen Hemminger
2010-01-28 18:34 ` Ben Hutchings
2010-02-04 1:47 ` David Miller [this message]
2010-01-28 18:09 ` Krishna Kumar2
2010-01-28 18:10 ` Ben Hutchings
2010-01-28 18:41 ` Krishna Kumar2
2010-01-28 18:40 ` Ben Hutchings
2010-01-28 19:04 ` Krishna Kumar2
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=20100203.174735.50359131.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).