From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] example/ipsec-secgw: ipsec security gateway
Date: Wed, 9 Mar 2016 23:54:50 +0000 [thread overview]
Message-ID: <56E0B7CA.8010204@intel.com> (raw)
In-Reply-To: <20160201112646.GA10490@localhost.localdomain>
On 01/02/2016 11:26, Jerin Jacob wrote:
> On Mon, Feb 01, 2016 at 11:09:16AM +0000, Sergio Gonzalez Monroy wrote:
>> On 31/01/2016 14:39, Jerin Jacob wrote:
>>> On Fri, Jan 29, 2016 at 08:29:12PM +0000, Sergio Gonzalez Monroy wrote:
>>>
>>> IMO, an option for single SA based outbound processing would be useful
>>> measuring performance bottlenecks with SA lookup.
>>>
>> Hi Jerin,
>>
>> Are you suggesting to have an option so we basically encrypt all traffic
>> using
>> a single SA bypassing the SP/ACL ?
> Yes. Basicaly an option to bypass "rte_acl_classify" if its for single
> SA use case.
>
>
Hi Jerin,
After re-reading your comment regarding the single SA I just want to
double check
that I understood correctly what you were suggesting.
Basically an option that we can provide a single SA to use for outbound,
skipping rte_acl_classify in outbound path.
That same option would also skip rte_acl_classify in inbound path
without checking
that we accept specific traffic for an SA.
Is that correct?
Sergio
next prev parent reply other threads:[~2016-03-09 23:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-29 20:29 [PATCH] example/ipsec-secgw: ipsec security gateway Sergio Gonzalez Monroy
2016-01-31 14:39 ` Jerin Jacob
2016-02-01 11:09 ` Sergio Gonzalez Monroy
2016-02-01 11:26 ` Jerin Jacob
2016-02-01 14:09 ` Thomas Monjalon
2016-03-09 23:54 ` Sergio Gonzalez Monroy [this message]
2016-03-10 3:41 ` Jerin Jacob
2016-02-24 13:32 ` Thomas Monjalon
2016-02-24 14:49 ` Sergio Gonzalez Monroy
2016-03-11 1:38 ` [PATCH v2] " Sergio Gonzalez Monroy
2016-03-11 2:12 ` De Lara Guarch, Pablo
2016-03-11 2:12 ` [PATCH v3] " Sergio Gonzalez Monroy
2016-03-11 10:01 ` De Lara Guarch, Pablo
2016-03-11 10:07 ` Thomas Monjalon
2016-03-11 10:02 ` Thomas Monjalon
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=56E0B7CA.8010204@intel.com \
--to=sergio.gonzalez.monroy@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.