public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Aaron Conole <aconole@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	dev@openvswitch.org, pshelar@ovn.org, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	echaudro@redhat.com, dceara@redhat.com, i.maximets@ovn.org
Subject: Re: [PATCH net-next] net: openvswitch: add support for l4 symmetric hashing
Date: Mon, 12 Jun 2023 08:50:40 +0000	[thread overview]
Message-ID: <168655984053.8602.1349154560216964511.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230609135955.3024931-1-aconole@redhat.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Fri,  9 Jun 2023 09:59:55 -0400 you wrote:
> Since its introduction, the ovs module execute_hash action allowed
> hash algorithms other than the skb->l4_hash to be used.  However,
> additional hash algorithms were not implemented.  This means flows
> requiring different hash distributions weren't able to use the
> kernel datapath.
> 
> Now, introduce support for symmetric hashing algorithm as an
> alternative hash supported by the ovs module using the flow
> dissector.
> 
> [...]

Here is the summary with links:
  - [net-next] net: openvswitch: add support for l4 symmetric hashing
    https://git.kernel.org/netdev/net-next/c/e069ba07e6c7

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2023-06-12  8:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 13:59 [PATCH net-next] net: openvswitch: add support for l4 symmetric hashing Aaron Conole
2023-06-12  8:50 ` patchwork-bot+netdevbpf [this message]

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=168655984053.8602.1349154560216964511.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=aconole@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dceara@redhat.com \
    --cc=dev@openvswitch.org \
    --cc=echaudro@redhat.com \
    --cc=edumazet@google.com \
    --cc=i.maximets@ovn.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pshelar@ovn.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