All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] example/ipsec-secgw: ipsec security gateway
Date: Wed, 24 Feb 2016 14:49:48 +0000	[thread overview]
Message-ID: <56CDC30C.5090205@intel.com> (raw)
In-Reply-To: <6273951.Zn9uhshjDu@xps13>

On 24/02/2016 13:32, Thomas Monjalon wrote:
> Hi,
>
> 2016-01-29 20:29, Sergio Gonzalez Monroy:
>> Sample app implementing an IPsec Security Geteway.
>> The main goal of this app is to show the use of cryptodev framework
>> in a real world application.
>>
>> Currently only supported static IPv4 IPsec tunnels using AES-CBC
>> and HMAC-SHA1.
>>
>> Also, currently not supported:
>> - SA auto negotiation (No IKE support)
>> - chained mbufs
> Is 32-bit arch supported?

It's meant to.

I'll fix it in next version.

Sergio
> I see this error:
> error: left shift count >= width of type [-Werror=shift-count-overflow]
>     (ethhdr[1] & (0xffffUL << 48));
>
>

  reply	other threads:[~2016-02-24 14:49 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
2016-03-10  3:41         ` Jerin Jacob
2016-02-24 13:32 ` Thomas Monjalon
2016-02-24 14:49   ` Sergio Gonzalez Monroy [this message]
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=56CDC30C.5090205@intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.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.