From: Radu Nicolau <radu.nicolau@intel.com>
To: Luca Boccassi <bluca@debian.org>, stable@dpdk.org
Cc: akhil.goyal@nxp.com, declan.doherty@intel.com,
pablo.de.lara.guarch@intel.com, roy.fan.zhang@intel.com
Subject: Re: [dpdk-stable] [PATCH] examples/ipsec-secgw: limit inflight packets count
Date: Mon, 30 Apr 2018 15:09:17 +0100 [thread overview]
Message-ID: <cf41b923-d6df-9ab3-30d3-076423066145@intel.com> (raw)
In-Reply-To: <1525095426.23337.15.camel@debian.org>
On 4/30/2018 2:37 PM, Luca Boccassi wrote:
> On Wed, 2018-04-04 at 13:18 +0100, Radu Nicolau wrote:
>> Revert previous patch that introduce a performance
>> degradation in certain scenarios and add a configurable
>> limit for number inflight packets.
>>
>> Revert
>> commit 84d4b5e4ec48 ("examples/ipsec-secgw: improve IPsec dequeue
>> logic")
>>
>> Signed-off-by: Radu Nicolau <radu.nicolau@intel.com>
>> ---
>> examples/ipsec-secgw/ipsec.c | 31 ++++++++++++++-----------------
>> examples/ipsec-secgw/ipsec.h | 1 +
>> 2 files changed, 15 insertions(+), 17 deletions(-)
> Has this, or a version of this, been committed in mainline? I cannot
> find it
>
I originally sent the patch for the master branch, but after feedback I
marked it as NA and resent the patch for the stable only; but the patch
in patchwork remains marked as NA.
https://dpdk.org/dev/patchwork/patch/36937/
The patch can be applied to the stable release, at least that was the
consensus at that time between Akhil and myself.
@Akhil: can we restart the discussion about having this in the master as
well, for this release?
next prev parent reply other threads:[~2018-04-30 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 12:18 Radu Nicolau
2018-04-30 13:37 ` Luca Boccassi
2018-04-30 14:09 ` Radu Nicolau [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-04-03 11:07 Radu Nicolau
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=cf41b923-d6df-9ab3-30d3-076423066145@intel.com \
--to=radu.nicolau@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=bluca@debian.org \
--cc=declan.doherty@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=roy.fan.zhang@intel.com \
--cc=stable@dpdk.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).