[dpdk-users] query on m_src buffer in crypto_op buffer

[dpdk-users] query on m_src buffer in crypto_op buffer

[rajesh kumar]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 6240 bytes --]

Hi All,
As part of our development crypto frame work we want to make use of AES-NI instruction set from Intel i7 boxes for crypto operations. Want to know whether m_src under crypto_op buffer which is op->sym->m_src has to be pointed to ethernet header or any other header. This is to do cryptographic operations on the packet received. From the l2fwd sample application i could see this is pointed to ethernet header. Can i copy the data from the ipheader and do the crypto operations since ESP data will start after this only.Please provide your valuable inputs. 
Thanks,Rajesh
From kfir@drivenets.com  Mon Jan  9 16:24:09 2017
Return-Path: <kfir@drivenets.com>
Received: from EUR01-DB5-obe.outbound.protection.outlook.com
 (mail-db5eur01on0113.outbound.protection.outlook.com [104.47.2.113])
 by dpdk.org (Postfix) with ESMTP id 02C1FD59A
 for <users@dpdk.org>; Mon,  9 Jan 2017 16:24:08 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=drivenets.onmicrosoft.com; s=selector1-drivenets-com;
 h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;
 bhëA5jd/4Y+2bhIb8C5fhmBPOhJeaGZCxNzvYB2RA3zs=;
 b=RDzwMUkD/9FzbNxsBP29tBQLCW4/1PofVP0XC24BhxKSTdDK7WzvSeIDyrZ++JgK2A6zpBR8hb5/FxE6TpAF+u6DPXTZKYI855nihELcxabAcHCMrbxOTc1RiJ5UAwoE+jL8OyzfAQ4JaKH2OslLxaiycg1ZdID8NRyXVc6hp60Received: from HE1PR04MB1178.eurprd04.prod.outlook.com (10.162.249.140) by
 HE1PR04MB1180.eurprd04.prod.outlook.com (10.162.249.142) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
 15.1.817.10; Mon, 9 Jan 2017 15:24:07 +0000
Received: from HE1PR04MB1178.eurprd04.prod.outlook.com ([10.162.249.140]) by
 HE1PR04MB1178.eurprd04.prod.outlook.com ([10.162.249.140]) with mapi id
 15.01.0817.015; Mon, 9 Jan 2017 15:24:07 +0000
From: Kfir gollan <kfir@drivenets.com>
To: "users@dpdk.org" <users@dpdk.org>
Thread-Topic: Updating rte_sched configuration.
Thread-Index: AQHSaoxrOHyIQ0JWpkWwMwmFTdKqbg=Date: Mon, 9 Jan 2017 15:24:07 +0000
Message-ID: <6A038519-4653-45EB-9ABB-DE8A27A3CD14@drivenets.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is )
 smtp.mailfrom=kfir@drivenets.com;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [82.81.67.219]
x-ms-office365-filtering-correlation-id: d7d19015-881b-4e53-4633-08d438a38df5
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001);SRVR:HE1PR04MB1180;
x-microsoft-exchange-diagnostics: 1; HE1PR04MB1180;
 7:1XEAfDy88gr/AilIYTRHgp6SDtzcumqUf6h2v2Z5SdTotYGSG6CYUbSiGK+ZoiltL1JmB+lwQ+jA37ACwYofHqRc0LTbRmj3HW8/8domw4e7kB616jI+8G1IJTLbE0NSBzUloYu2dt62t92Vn4Pmqk7paMg9687l885TRe9i98bW+4WzVFohqQmC4LlyGUmQdoB1uql9AYu7Tgk2uEus5ZFxqmNHabSaLa3xxGP0apvIfJHv/yFoQipj3HPpE+na424sbI1wE0FBjAmBOXcaJgUfVEXMlIsfzA5nHq6JR8uEFOw56mSxmtCM3UOb+dTQ8iRA64PfvJrvlKBIBoWrt/wVk8dVLenvLcqhttp5HPTsec2MImQ7yEELouT0r4yq8atPmfeciBjJjerILGQVXvbcdfKpl2bTKhI1XXF6LpgyefF9WCFqRU886kFlOc7BDdVFppjJzdbxm0CANQw4xw=x-microsoft-antispam-prvs: <HE1PR04MB1180AF289A28E882079979E6C3640@HE1PR04MB1180.eurprd04.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(788757137089);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0;
 RULEID:(6040375)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(6041248)(20161123562025)(20161123555025)(20161123564025)(20161123560025)(2016111802025)(6072148)(6047074)(6043046);
 SRVR:HE1PR04MB1180; BCL:0; PCL:0; RULEID:; SRVR:HE1PR04MB1180;
x-forefront-prvs: 0182DBBB05
x-forefront-antispam-report: SFV:NSPM;
 SFS:(10019020)(6009001)(7916002)(39830400002)(39410400002)(39450400003)(199003)(189002)(51874003)(6486002)(77096006)(587384001)(66066001)(5660300001)(105586002)(106356001)(38730400001)(2900100001)(106116001)(6916009)(6512007)(7116003)(2501003)(7736002)(110136003)(54896002)(82746002)(83716003)(81166006)(68736007)(50986999)(2906002)(6506006)(2351001)(54356999)(3660700001)(8676002)(3280700002)(8936002)(86362001)(107886002)(189998001)(1730700003)(36756003)(81156014)(97736004)(122556002)(25786008)(5640700003)(99286003)(3846002)(102836003)(92566002)(33656002)(6116002)(450100001)(6436002)(101416001)(104396002);
 DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR04MB1180;
 H:HE1PR04MB1178.eurprd04.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;
 A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: drivenets.com does not designate
 permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
MIME-Version: 1.0
X-OriginatorOrg: drivenets.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jan 2017 15:24:07.5185 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 662f82da-cf45-4bdf-b295-33b083f5d229
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR04MB1180
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-users] Updating rte_sched configuration.
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 09 Jan 2017 15:24:09 -0000

SGVsbG8sDQpJIHdhcyB3b25kZXJpbmcgaWYgaXQgaXMgcG9zc2libGUgdG8gdXBkYXRlIHRoZSBj
b25maWd1cmF0aW9uIG9mIHJ0ZV9zY2hlZF9wb3J0Lg0KRm9yIGV4YW1wbGUgY2FuIEkgdXNlIHJ0
ZV9zY2hlZF9waXBlX2NvbmZpZyBhbmQgY2hhbmdlIHRoZSBwcm9maWxlIG9mIGEgc3BlY2lmaWMg
cGlwZSBhZnRlciBzb21lIHBhY2tldHMgaGF2ZSBiZWVuIGVucXVldWVkIGludG8gdGhlIHBvcnQu
DQoNCk15IGN1cnJlbnQgc29sdXRpb24gaXMgdG8gYWxsb2NhdGUgYSBuZXcgcG9ydCwgY29uZmln
dXJlIGFsbCB0aGUgcnVsZXMgcGx1cyBteSB1cGRhdGUgYW5kIHJlcGxhY2UgdGhlIG9sZCBwb3J0
IHdpdGggdGhlIG5ldyBvbmUuDQoNCkkgZGlkbuKAmXQgZmluZCBhbnkgaW5mb3JtYXRpb24gcmVn
YXJkaW5nIHVwZGF0ZXMgdG8gdGhlIGNvbmZpZ3VyYXRpb24gaW4gdGhlIGRvY3VtZW50YXRpb24g
c28gSSBmaWd1cmVkIHRoYXQgSSBqdXN0IG1pZ2h0IGFzay4NCg0KVGhhbmtzIGluIGFkdmFuY2Us
DQpLZmlyLg0K

Re: [dpdk-users] query on m_src buffer in crypto_op buffer

[De Lara Guarch, Pablo]

Hi Rajesh,

> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of rajesh kumar
> Sent: Monday, January 09, 2017 7:00 AM
> To: users@dpdk.org
> Subject: [dpdk-users] query on m_src buffer in crypto_op buffer
> 
> Hi All,
> As part of our development crypto frame work we want to make use of
> AES-NI instruction set from Intel i7 boxes for crypto operations. Want to
> know whether m_src under crypto_op buffer which is op->sym->m_src has
> to be pointed to ethernet header or any other header. This is to do
> cryptographic operations on the packet received. From the l2fwd sample
> application i could see this is pointed to ethernet header. Can i copy the
> data from the ipheader and do the crypto operations since ESP data will
> start after this only.Please provide your valuable inputs.

m_src has to point at a mbuf, and then internally, it gets the address of the
start of the packet with rte_pktmbuf_mtod.

Since, L2fwd-crypto app handles IP packets, the start of the packet is the
Ethernet header, but only the payload is intended to be encrypted.
Therefore, op->sym->cipher.data.offset = ipdata_offset, where ipdata_offset
is the length of the Ethernet and IP headers.

So, all you need to do is adjust this offset (and length) for ciphering 
and authentication.

Thanks,
Pablo

> Thanks,Rajesh

Re: [dpdk-users] query on m_src buffer in crypto_op buffer

[rajesh kumar]

Hi Pablo,
Thank you for the clarification. So as i understood from you mail we can update either from ethernet header or from ip_header. If included with ethernet header ipdata_offset will be length of ethernet + ip header. if i include only from ip_header then ipdata_offset will be length of ip header alone.  DPDK crypto api will not be touching anything on the ethernet and ip headers.Since in my application code i will getting packet after processing the ethernet header so i want to copy from ipheader.Also after processing from the crypto device we will receive the packet in the same m_src buffer depending on how we updated.Please clarify me of my understanding is correct.
thanks,
Rajesh 

    On Tuesday, January 10, 2017 9:49 PM, "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com> wrote:
 

 Hi Rajesh,

> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of rajesh kumar
> Sent: Monday, January 09, 2017 7:00 AM
> To: users@dpdk.org
> Subject: [dpdk-users] query on m_src buffer in crypto_op buffer
> 
> Hi All,
> As part of our development crypto frame work we want to make use of
> AES-NI instruction set from Intel i7 boxes for crypto operations. Want to
> know whether m_src under crypto_op buffer which is op->sym->m_src has
> to be pointed to ethernet header or any other header. This is to do
> cryptographic operations on the packet received. From the l2fwd sample
> application i could see this is pointed to ethernet header. Can i copy the
> data from the ipheader and do the crypto operations since ESP data will
> start after this only.Please provide your valuable inputs.

m_src has to point at a mbuf, and then internally, it gets the address of the
start of the packet with rte_pktmbuf_mtod.

Since, L2fwd-crypto app handles IP packets, the start of the packet is the
Ethernet header, but only the payload is intended to be encrypted.
Therefore, op->sym->cipher.data.offset = ipdata_offset, where ipdata_offset
is the length of the Ethernet and IP headers.

So, all you need to do is adjust this offset (and length) for ciphering 
and authentication.

Thanks,
Pablo

> Thanks,Rajesh


   
From sakthivelpvs@gmail.com  Wed Jan 11 04:55:25 2017
Return-Path: <sakthivelpvs@gmail.com>
Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54])
 by dpdk.org (Postfix) with ESMTP id 9BAB3592C
 for <users@dpdk.org>; Wed, 11 Jan 2017 04:55:25 +0100 (CET)
Received: by mail-wm0-f54.google.com with SMTP id c85so146588892wmi.1
 for <users@dpdk.org>; Tue, 10 Jan 2017 19:55:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s 161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=muPQCPmQH/sSxP/vPjmwzRaZ79v0+ituKlP5e7AOu9M=;
 b=bIKtB77uJOyBqA49Zkv1BauFVXavwIyB4PDdK511awzGewhay3TABZRSpfj5cvBvR9
 2P7SwuNsuzPnVAQhYCyJO7CtievG80PAVMNT20ulKnWkreoV6x/0dj4lbJck58FujOXJ
 cw9AWP+1qNjvI6htP4CWfp5bbY2QzEUOPsYs+yRLWvqXOE0TW92XR+nBwdV3ZXdVLbAn
 wWDzULCstbN7+ndeyoDVIdJvFCpe2CGoq4ACn9FRyIBQ32g0R9FbPuRLtKQbzpKLcDUe
 /dzihRsBRG7CFEwiHb2iigNQZTjxbLWsakn9wwKcCAXRpWH94WmYC7lNwQp2W1WJFhCe
 JYmw=X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d\x1e100.net; s 161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=muPQCPmQH/sSxP/vPjmwzRaZ79v0+ituKlP5e7AOu9M=;
 b=PeISNvm7RKe9VuF1U9ysBBJ/TwW7xFaUkkoKrBLKlQQSWXsyx2hVd4deDMF2PVN0xm
 xG7MQSFkLYTUjM/g1P7VJzyA5BrxXu2yefOMSajWi4LZ8r9O1Qvk9EqQv2Y4Y4X1tFWY
 dwdYbfkyyRn4kKKMFtEKasfIapoltej3xrcALywJHeXFZtFx4+YE1TeK/uDKYy1KL2ut
 EFHSRMwMuWD/VjuA66QWE75xdCUh5lFgAmwE8yBBS/mVTbZFO7jJieOzBSolCCpHMkPe
 zHGMDDRLpVYlXPbDPK6y4+jwKO6on6REmC1gJ/qbYrWXY4c467iI1yp2G5YA3yn9T4kq
 w6Rg=X-Gm-Message-State: AIkVDXJCWK6w+jk9N7FsMgWQIs5VdEgxP/ktJ5Q8pK4l6+KU3X/OvVpG8TT7IT8DX5FOZOIDbPJgTm23x4bssA=X-Received: by 10.28.21.206 with SMTP id 197mr1105460wmv.128.1484106925120;
 Tue, 10 Jan 2017 19:55:25 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.182.124 with HTTP; Tue, 10 Jan 2017 19:55:24 -0800 (PST)
From: Sakthivel Subramaniam <sakthivelpvs@gmail.com>
Date: Wed, 11 Jan 2017 09:25:24 +0530
Message-ID: <CANrG1jXW_wPypSECZx3NBrg3ARBqfrE583+mBqbZL+K36C8dOw@mail.gmail.com>
To: users@dpdk.org
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-users] Regarding Receiving packets from outer world (internet)
X-BeenThere: users@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK usage discussions <users.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/users>,
 <mailto:users-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/users/>
List-Post: <mailto:users@dpdk.org>
List-Help: <mailto:users-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/users>,
 <mailto:users-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jan 2017 03:55:25 -0000

Hi,
I'm new to DPDK and want to use dpdk for my project.
I have basic question about receiving packets using dpdk bound interface
from internet.

Please provide clarity for following questions.
1. How can we receive packets from internet and process the same using DPDK?
2. How to assign IP address for the DPDK ethernet interface ?
3. Is it possible to receive specific protocol packets (ex:MQTT) without IP
address using DPDK?
4. Is it necessary to add TCP/IP stack to dpdk?


--
Thanks & Regards
Sakthivel S