From: David Miller <davem@davemloft.net>
To: tgraf@redhat.com
Cc: jesse@nicira.com, 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 17:38:32 -0500 (EST) [thread overview]
Message-ID: <20131210.173832.401837941212576450.davem@davemloft.net> (raw)
In-Reply-To: <52A77DF4.5070302@redhat.com>
From: Thomas Graf <tgraf@redhat.com>
Date: Tue, 10 Dec 2013 21:47:48 +0100
> 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.
The things you are listing as implicit overhead can be eliminated
almost entirely using static branches.
next prev parent reply other threads:[~2013-12-10 22:38 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
2013-12-10 21:36 ` Jesse Gross
2013-12-10 22:38 ` David Miller [this message]
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=20131210.173832.401837941212576450.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dborkman@redhat.com \
--cc=dev@openvswitch.org \
--cc=ffusco@redhat.com \
--cc=jesse@nicira.com \
--cc=netdev@vger.kernel.org \
--cc=tgraf@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;
as well as URLs for NNTP newsgroup(s).