From: Tom Herbert <therbert@google.com>
To: netdev@vger.kernel.org, davem@davemloft.net
Subject: [PATCH 0/17 v2] net: Add rxhash utility hash functions
Date: Tue, 26 Nov 2013 09:22:14 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1311260913490.21031@tomh.mtv.corp.google.com> (raw)
v2: Change occurences of 'get' to be 'set' in commit logs.
This patch series introduce skb_set_rxhash and skb_clear_rxhash
which are called to set the rxhash (from network drivers) and
to clear the rxhash. This API should be used instead of updating
fields in the skbuff directly.
Verified that the drivers compiled with the changes (verified
bnx2x is operational).
By my count 15 NIC drivers set the rxhash, but only two of them
mark the hash as L4. It looks like several of those have capability
do determine an L4 hash was done.
reply other threads:[~2013-11-26 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.DEB.2.02.1311260913490.21031@tomh.mtv.corp.google.com \
--to=therbert@google.com \
--cc=davem@davemloft.net \
--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