netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Tom Herbert <therbert@google.com>,
	davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next] net: Reflect RX hash for transmit
Date: Sun, 15 Feb 2015 20:59:29 +0100	[thread overview]
Message-ID: <54E0FAA1.7000900@iogearbox.net> (raw)
In-Reply-To: <1424025438-1659-1-git-send-email-therbert@google.com>

On 02/15/2015 07:37 PM, Tom Herbert wrote:
> This patch allows a driver to request that the receive hash it provides
> to the stack is reflected back in skb->hash for packets transmitted
> on the associated connection.
[...]
> +	if (unlikely(skb->reflect_hash && sk->sk_txhash != skb->hash))
> +		sk->sk_txhash = skb->hash;

Is there also an initial user setting this somewhere?

  reply	other threads:[~2015-02-15 19:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-15 18:37 [PATCH net-next] net: Reflect RX hash for transmit Tom Herbert
2015-02-15 19:59 ` Daniel Borkmann [this message]
2015-02-15 20:19   ` Tom Herbert
2015-02-15 20:27     ` Daniel Borkmann
2015-02-16 12:29 ` Eric Dumazet
2015-02-19 20:54 ` 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=54E0FAA1.7000900@iogearbox.net \
    --to=daniel@iogearbox.net \
    --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;
as well as URLs for NNTP newsgroup(s).