netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Graf <tgraf@redhat.com>
To: David Miller <davem@davemloft.net>, jesse@nicira.com
Cc: ffusco@redhat.com, netdev@vger.kernel.org, dev@openvswitch.org,
	dborkman@redhat.com
Subject: Re: [PATCH net-next] net: ovs: use CRC32 accelerated flow hash if available
Date: Tue, 10 Dec 2013 21:47:48 +0100	[thread overview]
Message-ID: <52A77DF4.5070302@redhat.com> (raw)
In-Reply-To: <20131210.143652.1279430126319061689.davem@davemloft.net>

On 12/10/2013 08:36 PM, David Miller wrote:
> From: Jesse Gross <jesse@nicira.com>
> Date: Tue, 10 Dec 2013 11:28:08 -0800
>
>> I think this is definitely a good optimization to do given that so
>> much of the work that OVS does is hashing. However, isn't there a
>> library where there would be a more appropriate place to put this?
>
> I also honestly don't see why we want to special case OVS at all
> here.  This faster hashing would be useful for socket demux and
> other locations in the kernel.
>
> When I see changes like this my only reaction is "sad face".

We discussed this heavily and decided to go with the minimal approach
first to collect some feedback. We were not sure whether the runtime
check, function pointer and hardware dependencies are something other
subsystems that are less x86_64 centric would want to live with.

That said, we are _very_ willing to do the work and move it to lib/
to make it available to other consumers but one should be aware that
crc32 based hashes are not as generally usable as jhash.

  reply	other threads:[~2013-12-10 20:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10  9:52 [PATCH net-next] net: ovs: use CRC32 accelerated flow hash if available Francesco Fusco
2013-12-10 10:20 ` David Laight
2013-12-10 19:28 ` Jesse Gross
2013-12-10 19:36   ` David Miller
2013-12-10 20:47     ` Thomas Graf [this message]
2013-12-10 21:36       ` Jesse Gross
2013-12-10 22:38       ` David Miller
2013-12-10 21:27     ` Tom Herbert
2013-12-10 21:40       ` Jesse Gross

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=52A77DF4.5070302@redhat.com \
    --to=tgraf@redhat.com \
    --cc=davem@davemloft.net \
    --cc=dborkman@redhat.com \
    --cc=dev@openvswitch.org \
    --cc=ffusco@redhat.com \
    --cc=jesse@nicira.com \
    --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;
as well as URLs for NNTP newsgroup(s).