Netdev List
 help / color / mirror / Atom feed
From: Antoine Tenart <atenart@kernel.org>
To: Dumitru Ceara <dceara@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	Ilya Maximets <i.maximets@ovn.org>
Cc: i.maximets@ovn.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 4/4] net: skbuff: fix l4_hash comment
Date: Tue, 23 May 2023 17:25:54 +0200	[thread overview]
Message-ID: <168485555448.4954.15925446882328637898@kwain> (raw)
In-Reply-To: <5f1ef3e1-be8f-4bbc-a877-ec13cdc9254a@ovn.org>

Quoting Ilya Maximets (2023-05-18 01:00:40)
> On 5/17/23 14:05, Antoine Tenart wrote:
> > 
> > Even l4_hash w/o taking the rnd case into account does not guarantee a
> > stable hash for the lifetime of a flow; what happens if packets from the
> > same flow are received on two NICs using different keys and/or algs?
> 
> Following the same logic we can't really say that it "provides a uniform
> distribution over L4 flows" either.  The fact that L4 fields were used
> to calculate the hash, doesn't mean the hash function is any good.

Well drivers need to either trust the h/w in some ways or not use what
is provided if it's broken; or we can't be sure of anything. It's not
the same as an example where a valid setup can't guarantee a property by
design.

> > Now, I'll let some time to give a chance for others to chime in.
> 
> Sure.

I don't think we'll get more guidance and we failed to come to an
agreement so let's keep this as-is for now; I'll send a v2 w/o this
documentation change.

As for a way forward and the stability need, IMHO the hash needs to be
computed where it is used (with potential cache, not reusing skb->hash)
but if you feel this should be addressed at this level a patch doing so
might at least get others to comment (both ways).

Thanks,
Antoine

  reply	other threads:[~2023-05-23 15:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11  9:34 [PATCH net-next 0/4] net: tcp: make txhash use consistent for IPv4 Antoine Tenart
2023-05-11  9:34 ` [PATCH net-next 1/4] net: tcp: make the txhash available in TIME_WAIT sockets for IPv4 too Antoine Tenart
2023-05-11  9:34 ` [PATCH net-next 2/4] net: ipv4: use consistent txhash in TIME_WAIT and SYN_RECV Antoine Tenart
2023-05-11  9:34 ` [PATCH net-next 3/4] Documentation: net: net.core.txrehash is not specific to listening sockets Antoine Tenart
2023-05-11  9:34 ` [PATCH net-next 4/4] net: skbuff: fix l4_hash comment Antoine Tenart
2023-05-11 12:10   ` Dumitru Ceara
2023-05-11 12:33     ` Eric Dumazet
2023-05-11 13:00       ` Dumitru Ceara
2023-05-11 17:54         ` Ilya Maximets
2023-05-11 20:50           ` Dumitru Ceara
2023-05-15  8:12             ` Antoine Tenart
2023-05-15 18:23               ` Ilya Maximets
2023-05-16  7:36                 ` Antoine Tenart
2023-05-16 21:25                   ` Ilya Maximets
2023-05-17 12:05                     ` Antoine Tenart
2023-05-17 23:00                       ` Ilya Maximets
2023-05-23 15:25                         ` Antoine Tenart [this message]
2023-05-11 10:24 ` [PATCH net-next 0/4] net: tcp: make txhash use consistent for IPv4 Eric Dumazet
2023-05-11 11:55   ` Antoine Tenart
2023-05-11 11:59 ` Ilya Maximets
  -- strict thread matches above, loose matches on Subject: below --
2023-04-27 13:45 Antoine Tenart
2023-04-27 13:45 ` [PATCH net-next 4/4] net: skbuff: fix l4_hash comment Antoine Tenart

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=168485555448.4954.15925446882328637898@kwain \
    --to=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dceara@redhat.com \
    --cc=edumazet@google.com \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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