From: Ben Hutchings <bhutchings@solarflare.com>
To: Tom Herbert <therbert@google.com>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>
Subject: Re: [PATCH 15/17] net: sfc calls skb_get_rxhash
Date: Tue, 26 Nov 2013 19:59:17 +0000 [thread overview]
Message-ID: <1385495957.1586.54.camel@bwh-desktop.uk.level5networks.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1311252156170.23058@tomh.mtv.corp.google.com>
On Mon, 2013-11-25 at 21:57 -0800, Tom Herbert wrote:
> Drivers should call skb_get_rxhash to set the rxhash and its type
> in an skbuff.
>
> Signed-off-by: Tom Herbert <therbert@google.com>
> ---
> drivers/net/ethernet/sfc/rx.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/sfc/rx.c b/drivers/net/ethernet/sfc/rx.c
> index 8f09e68..b51466e 100644
> --- a/drivers/net/ethernet/sfc/rx.c
> +++ b/drivers/net/ethernet/sfc/rx.c
> @@ -439,7 +439,8 @@ efx_rx_packet_gro(struct efx_channel *channel, struct efx_rx_buffer *rx_buf,
> }
>
> if (efx->net_dev->features & NETIF_F_RXHASH)
> - skb->rxhash = efx_rx_buf_hash(efx, eh);
> + skb_set_rxhash(skb, efx_rx_buf_hash(efx, eh),
> + RXHASH_TYPE_L3);
This is equivalent to what we do now. But efx_rx_packet_gro() is only
ever called for TCP packets (checked in __efx_rx_packet()) and their
hashes include port numbers, so the hash type could be RXHASH_TYPE_L4.
Ben.
> skb->ip_summed = ((rx_buf->flags & EFX_RX_PKT_CSUMMED) ?
> CHECKSUM_UNNECESSARY : CHECKSUM_NONE);
>
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2013-11-26 19:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 5:57 [PATCH 15/17] net: sfc calls skb_get_rxhash Tom Herbert
2013-11-26 19:59 ` Ben Hutchings [this message]
2013-11-26 23:35 ` Tom Herbert
2013-11-27 0:05 ` Ben Hutchings
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=1385495957.1586.54.camel@bwh-desktop.uk.level5networks.com \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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