From: David Miller <davem@davemloft.net>
To: pshelar@ovn.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] openvswitch: avoid resetting flow key while installing new flow.
Date: Tue, 20 Sep 2016 22:54:52 -0400 (EDT) [thread overview]
Message-ID: <20160920.225452.1951319356915241128.davem@davemloft.net> (raw)
In-Reply-To: <1474318260-16988-2-git-send-email-pshelar@ovn.org>
From: Pravin B Shelar <pshelar@ovn.org>
Date: Mon, 19 Sep 2016 13:51:00 -0700
> since commit commit db74a3335e0f6 ("openvswitch: use percpu
> flow stats") flow alloc resets flow-key. So there is no need
> to reset the flow-key again if OVS is using newly allocated
> flow-key.
>
> Signed-off-by: Pravin B Shelar <pshelar@ovn.org>
Applied.
next prev parent reply other threads:[~2016-09-21 2:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 20:50 [PATCH net-next 1/2] openvswitch: Fix Frame-size larger than 1024 bytes warning Pravin B Shelar
2016-09-19 20:51 ` [PATCH net-next 2/2] openvswitch: avoid resetting flow key while installing new flow Pravin B Shelar
2016-09-21 2:54 ` David Miller [this message]
2016-09-21 2:54 ` [PATCH net-next 1/2] openvswitch: Fix Frame-size larger than 1024 bytes warning 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=20160920.225452.1951319356915241128.davem@davemloft.net \
--to=davem@davemloft.net \
--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).