From: Paolo Abeni <pabeni@redhat.com>
To: Eelco Chaudron <echaudro@redhat.com>, netdev@vger.kernel.org
Cc: davem@davemloft.net, dev@openvswitch.org, kuba@kernel.org,
pshelar@ovn.org
Subject: Re: [PATCH net-next] net: openvswitch: reorder masks array based on usage
Date: Wed, 15 Jul 2020 16:37:41 +0200 [thread overview]
Message-ID: <b9274778380debaacd8f31d7720df5c48457c0c7.camel@redhat.com> (raw)
In-Reply-To: <159481496860.37198.8385493040681064040.stgit@ebuild>
On Wed, 2020-07-15 at 14:09 +0200, Eelco Chaudron wrote:
> This patch reorders the masks array every 4 seconds based on their
> usage count. This greatly reduces the masks per packet hit, and
> hence the overall performance. Especially in the OVS/OVN case for
> OpenShift.
>
> Here are some results from the OVS/OVN OpenShift test, which use
> 8 pods, each pod having 512 uperf connections, each connection
> sends a 64-byte request and gets a 1024-byte response (TCP).
> All uperf clients are on 1 worker node while all uperf servers are
> on the other worker node.
>
> Kernel without this patch : 7.71 Gbps
> Kernel with this patch applied: 14.52 Gbps
>
> We also run some tests to verify the rebalance activity does not
> lower the flow insertion rate, which does not.
>
> Signed-off-by: Eelco Chaudron <echaudro@redhat.com>
> Tested-by: Andrew Theurer <atheurer@redhat.com>
Reviewed-by: Paolo Abeni <pabeni@redhat.com>
/P
next prev parent reply other threads:[~2020-07-15 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 12:09 [PATCH net-next] net: openvswitch: reorder masks array based on usage Eelco Chaudron
2020-07-15 14:37 ` Paolo Abeni [this message]
2020-07-17 17:37 ` 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=b9274778380debaacd8f31d7720df5c48457c0c7.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).