Additional questions:
Is it possible to use MLNX_OFED-4.3 on Ubuntu 12.04?
Why is the driver related to OS version?
-Original Message-
From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Asaf Sinai
Sent: Monday, July 2, 2018 05:22 PM
To: Shahaf Shuler
Cc: dev@dpdk.org; Nitin Katiyar ; Né
On Mon, Jul 02, 2018 at 06:07:03PM -0700, Yongseok Koh wrote:
> On Wed, Jun 27, 2018 at 05:07:34PM +0200, Nelio Laranjeiro wrote:
> > Drop queues are essentially used in flows due to Verbs API, the
> > information if the fate of the flow is a drop or not is already present
> > in the flow. Due to
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Hari Kumar
> Sent: Friday, June 29, 2018 3:01 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo ; Pattan, Reshma
> ; Vemula, Hari KumarX
>
> Subject: [dpdk-dev] [PATCH v3] crypto/scheduler: add dynamic logging
>
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Jananee Parthasarathy
> Sent: Friday, June 29, 2018 1:29 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo ; Pattan, Reshma
> ; Poornima, PallantlaX
>
> Subject: [dpdk-dev] [PATCH v2] crypto/null: add dynamic loggi
> -Original Message-
> From: Somarowthu, Naga SureshX
> Sent: Friday, June 29, 2018 1:51 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo ; Pattan, Reshma
> ; Somarowthu, Naga SureshX
>
> Subject: [PATCH v2] crypto/openssl: add dynamic logging
>
> 1.added new logtype for openssl driver.
> -Original Message-
> From: Somarowthu, Naga SureshX
> Sent: Friday, June 29, 2018 10:55 AM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo ; Pattan, Reshma
> ; Somarowthu, Naga SureshX
>
> Subject: [PATCH v2] crypto/aesni_mb: add dynamic logging
>
> 1.added new logtype for aesni_mb drive
> -Original Message-
> From: Somarowthu, Naga SureshX
> Sent: Friday, June 29, 2018 10:48 AM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo ; Pattan, Reshma
> ; Somarowthu, Naga SureshX
>
> Subject: [PATCH v2] crypto/kasumi: add dynamic logging
>
> 1.added new logtype for kasumi driver.
>
> -Original Message-
> From: Parthasarathy, JananeeX M
> Sent: Thursday, June 28, 2018 4:00 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo ; Pattan, Reshma
> ; Babu Radhakrishnan, AgalyaX
>
> Subject: [PATCH v2] crypto/zuc: add dynamic logging
>
> From: Agalya Babu RadhaKrishnan
>
>
> -Original Message-
> From: Somarowthu, Naga SureshX
> Sent: Thursday, June 28, 2018 3:47 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo ; Pattan, Reshma
> ; Chaitanya Babu, TalluriX
>
> Subject: [PATCH v2] crypto/aesni_gcm: add dynamic logging
>
> From: Chaitanya Babu Talluri
>
> 1
> -Original Message-
> From: Parthasarathy, JananeeX M
> Sent: Thursday, June 28, 2018 4:00 PM
> To: dev@dpdk.org
> Cc: De Lara Guarch, Pablo ; Pattan, Reshma
> ; Babu Radhakrishnan, AgalyaX
>
> Subject: [PATCH v2] crypto/zuc: add dynamic logging
>
> From: Agalya Babu RadhaKrishnan
>
l2fwd_fork is not complied by default, this will make it compile
Fixes: 95e8005a56e8 ("examples/l2fwd_fork: new app")
Signed-off-by: Emma Kenny
---
examples/multi_process/Makefile | 2 --
1 file changed, 2 deletions(-)
diff --git a/examples/multi_process/Makefile b/examples/multi_process/Makef
Added Scatter-Gather test, which split input data
into multi-segment mbufs and compresses/decompresses
the data into also a multi-segment mbuf.
Signed-off-by: Pablo de Lara
---
test/test/test_compressdev.c | 390 ++-
1 file changed, 351 insertions(+), 39 d
On 02-Jul-18 6:26 PM, Alejandro Lucero wrote:
A device can suffer addressing limitations. This functions checks
memsegs have iovas within the supported range based on dma mask.
PMD should use this during initialization if supported devices
suffer addressing limitations, returning an error if thi
On 02-Jul-18 6:27 PM, Alejandro Lucero wrote:
Although VT-d emulation currently only supports 39 bits, it could
be iovas being within that supported range. This patch allows
IOVA mode in such a case.
Indeed, memory initialization code can be modified for using lower
virtual addresses than those
On 02-Jul-18 6:27 PM, Alejandro Lucero wrote:
Linux kernel uses a really high address as starting address for
serving mmaps calls. If there exists addressing limitations and
IOVA mode is VA, this starting address is likely too high for
those devices. However, it is possible to use a lower address
Hi,
02/07/2018 07:44, Qi Zhang:
> --- a/lib/librte_ethdev/rte_ethdev_driver.h
> +++ b/lib/librte_ethdev/rte_ethdev_driver.h
> @@ -70,6 +70,19 @@ int rte_eth_dev_release_port(struct rte_eth_dev *eth_dev);
>
> /**
> * @internal
> + * Release the specified ethdev port in local process, only set
Hi Qi,
Sorry I do not understand neither the commit log, nor the doxygen.
If it can help, consider your reader is in a bad mood
and needs a pleasant description.
02/07/2018 07:44, Qi Zhang:
> Introduce new API rte_eal_register_mp_init that help to register
> a callback function which will be invo
mantan,
On 7/1/2018 3:46 PM, Matan Azrad wrote:
Hi Jeff
A good advance, thank you, but as I said in previous version, this patch
inserts a bug and the next one fixes it.
Patch 9 should be before patch 8 while this patch just add 1 more option for
EAL hotplug.
i agree that patch 9 before pa
Hi,
02/07/2018 07:44, Qi Zhang:
> --- /dev/null
> +++ b/lib/librte_ethdev/ethdev_mp.h
> @@ -0,0 +1,41 @@
> +/* SPDX-License-Identifier: BSD-3-Clause
> + * Copyright(c) 2018 Intel Corporation
> + */
> +
> +#ifndef _RTE_ETHDEV_MP_H_
> +#define _RTE_ETHDEV_MP_H_
> +
> +#define MAX_DEV_ARGS_LEN 0x80
>
02/07/2018 07:44, Qi Zhang:
> Introduce API rte_eth_dev_lock and rte_eth_dev_unlock to let
> application lock or unlock on specific ethdev, a locked device
> can't be detached, this help applicaiton to prevent unexpected
> device detaching, especially in multi-process envrionment.
Trying to unders
On Tue, Jul 3, 2018 at 10:07 AM, Burakov, Anatoly wrote:
> On 02-Jul-18 6:26 PM, Alejandro Lucero wrote:
>
>> A device can suffer addressing limitations. This functions checks
>> memsegs have iovas within the supported range based on dma mask.
>>
>> PMD should use this during initialization if su
On Tue, Jul 03, 2018 at 12:47:18AM +0100, Ferruh Yigit wrote:
> On 6/8/2018 5:38 PM, Bruce Richardson wrote:
> > Rather than hard-coding the example app to be built only when a set of
> > conditions are met, we can simplify things by having the app built when
> > KNI library itself is available. Th
On Tue, Jul 3, 2018 at 10:10 AM, Burakov, Anatoly wrote:
> On 02-Jul-18 6:27 PM, Alejandro Lucero wrote:
>
>> Although VT-d emulation currently only supports 39 bits, it could
>> be iovas being within that supported range. This patch allows
>> IOVA mode in such a case.
>>
>> Indeed, memory initia
This patchset enables building DPDK on 32-bit systems, and has been tested
using debian 32-bit on x86 i.e. doing an "i686" build in the old build
system.
v2:
- fixed LIB_LIBRTE_KNI to RTE_LIBRTE_KNI in examples/kni patch [Ferruh]
- added patch to make same change in drivers/net/kni [Ferruh]
Bru
The JIT is only supported on x86_64 so disable for 32-bit builds.
Fixes: cc752e43e079 ("bpf: add JIT compilation for x86_64 ISA")
Signed-off-by: Bruce Richardson
Acked-by: Konstantin Ananyev
Series-acked-by: Hemant Agrawal
---
lib/librte_bpf/meson.build | 2 +-
1 file changed, 1 insertion(+),
The sfc driver is not supported on 32-bit so disable in meson in
those cases.
Signed-off-by: Bruce Richardson
Acked-by: Andrew Rybchenko
Series-acked-by: Hemant Agrawal
---
drivers/net/sfc/meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/sfc/meson.bui
Converting a 32-bit pointer to a 64-bit integer is generally safe, but
generates a lot of warnings when compiling 32-bit code with meson. The
warnings are not flagged when using make, so just disable them for
32-bit meson builds.
Signed-off-by: Bruce Richardson
Acked-by: Hemant Agrawal
Series-ac
The kni library is not supported on 32-bit so disable it for those
builds using meson.
Signed-off-by: Bruce Richardson
Acked-by: Ferruh Yigit
Series-acked-by: Hemant Agrawal
---
lib/librte_kni/meson.build | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/librte_kni/meson.
Rather than hard-coding the example app to be built only when a set of
conditions are met, we can simplify things by having the app built when
KNI library itself is available. That saves us duplicating the same set
of restrictions on both library and example app.
Fixes: 89f0711f9ddf ("examples: bu
When compiling with meson, extra warnings are enabled about casting from
integers to different size pointers. This triggers an error in AVP as the
addition of the offset to the pointer address causes the result to be a
64-bit integer which doesn't fit a 32-bit pointer. The fix here is to
explicitly
By default, the DPAA2_USE_PHYS_IOVA setting with the make build-system
is "y", which is overridden to "n" in the config file specifically for
the arm64-dpaa2-linuxapp-gcc builds. The lack of this setting in meson
builds causes issues for 32-bit build, as the alternative code paths
have compiler war
The configuration value indicating that KNI was build was incorrect,
causing the driver to never be built.
Fixes: 3479586fe636 ("net/kni: add to meson build")
Signed-off-by: Bruce Richardson
Series-acked-by: Hemant Agrawal
---
drivers/net/kni/meson.build | 2 +-
1 file changed, 1 insertion(+),
On 7/3/2018 2:36 AM, Liu, Yong wrote:
>
>
>> -Original Message-
>> From: Yigit, Ferruh
>> Sent: Tuesday, July 03, 2018 12:57 AM
>> To: Maxime Coquelin ; Liu, Yong
>> ; Bie, Tiwei
>> Cc: Wang, Zhihong ; dev@dpdk.org
>> Subject: Re: [dpdk-dev] [PATCH v5 7/9] net/virtio: support in-order Rx
On Tue, Jul 3, 2018 at 10:17 AM, Burakov, Anatoly wrote:
> On 02-Jul-18 6:27 PM, Alejandro Lucero wrote:
>
>> Linux kernel uses a really high address as starting address for
>> serving mmaps calls. If there exists addressing limitations and
>> IOVA mode is VA, this starting address is likely too
On 03-Jul-18 11:44 AM, Alejandro Lucero wrote:
+ addr = mmap(addr_hint,
(*size) + hugepage_sz, PROT_READ,
#ifdef RTE_ARCH_PPC_64
MAP_PRIVATE | MAP_ANONYMOUS |
MAP_HUGETLB,
Tuesday, July 3, 2018 10:01 AM, Asaf Sinai:
> Subject: Re: [dpdk-dev] Compilation of MLX5 driver
>
> Additional questions:
> Is it possible to use MLNX_OFED-4.3 on Ubuntu 12.04?
I am not sure if there is such build, the oldest OFED build I see is for
ubuntu14.10. ubuntu12.04 is really old.
> Wh
hi, gaetan and konstantin
answer both of your questions here as below.
On 6/29/2018 8:52 PM, Gaëtan Rivet wrote:
On Fri, Jun 29, 2018 at 12:21:39PM +, Ananyev, Konstantin wrote:
-Original Message-
From: Guo, Jia
Sent: Friday, June 29, 2018 12:23 PM
To: Ananyev, Konstantin ;
step
Tuesday, July 3, 2018 12:00 AM, Yongseok Koh:
> Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: add support for 32bit systems
>
>
> > On Jul 2, 2018, at 4:11 AM, Moti Haimovsky wrote:
> >
> > This patch adds support for building and running mlx5 PMD on 32bit
> > systems such as i686.
> >
> > The ma
NFP devices can not handle DMA addresses requiring more than
40 bits. This patch uses rte_dev_check_dma_mask with 40 bits
and avoids device initialization if memory out of NFP range.
Signed-off-by: Alejandro Lucero
---
drivers/net/nfp/nfp_net.c | 8
1 file changed, 8 insertions(+)
diff
Linux kernel uses a really high address as starting address for
serving mmaps calls. If there exists addressing limitations and
IOVA mode is VA, this starting address is likely too high for
those devices. However, it is possible to use a lower address in
the process virtual address space as with 64
A PMD should invoke this function for checking memsegs iovas are within
the supported range by the device.
Signed-off-by: Alejandro Lucero
---
lib/librte_ether/rte_ethdev.h | 13 +
1 file changed, 13 insertions(+)
diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_eth
This patchset adds, mainly, a check for ensuring IOVAs are within a
restricted range due to addressing limitations with some devices. There
are two known cases: NFP and IOMMU VT-d emulation.
With this check IOVAs out of range are detected and PMDs can abort
initialization. For the VT-d case, IOVA
On 7/3/2018 11:31 AM, Bruce Richardson wrote:
> Rather than hard-coding the example app to be built only when a set of
> conditions are met, we can simplify things by having the app built when
> KNI library itself is available. That saves us duplicating the same set
> of restrictions on both librar
A device can suffer addressing limitations. This functions checks
memsegs have iovas within the supported range based on dma mask.
PMD should use this during initialization if supported devices
suffer addressing limitations, returning an error if this function
returns memsegs out of range.
Anothe
Although VT-d emulation currently only supports 39 bits, it could
be iovas being within that supported range. This patch allows
IOVA mode in such a case.
Indeed, memory initialization code can be modified for using lower
virtual addresses than those used by the kernel for 64 bits processes
by defa
NFP can handle IOVA as VA. It requires to check those IOVAs
being in the supported range what is done during initialization.
Signed-off-by: Alejandro Lucero
---
drivers/net/nfp/nfp_net.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/net/nfp/nfp_net.c b/drivers
On 7/3/2018 11:31 AM, Bruce Richardson wrote:
> The configuration value indicating that KNI was build was incorrect,
> causing the driver to never be built.
>
> Fixes: 3479586fe636 ("net/kni: add to meson build")
>
> Signed-off-by: Bruce Richardson
> Series-acked-by: Hemant Agrawal
Acked-by: F
Monday, July 2, 2018 6:40 PM, Emma Kenny:
> Subject: [PATCH v1] examples/multi_process: fix build error
>
> Fix bug with undeclared variable name and calling a variable that is not
> member of struct.
>
> CC main.o
> l2fwd_fork/main.c: In function ‘main’: l2fwd_fork/main.c:1043:33:
> error: ‘de
On 6/29/2018 11:30 AM, Jeff Guo wrote:
> When hot unplug device, the kernel will release the device resource in the
> kernel side, such as the fd sys file will disappear, and the irq will be
> released. At this time, if igb uio driver still try to release this
> resource, it will cause kernel crash
Tuesday, July 3, 2018 12:28 AM, Thomas Monjalon:
> Subject: [PATCH v2 5/5] ethdev: remove old offload API
>
> From: Ferruh Yigit
>
> In DPDK 17.11, the ethdev offloads API has changed:
> commit cba7f53b717d ("ethdev: introduce Tx queue offloads API")
> commit ce17eddefc20 ("ethdev: i
> -Original Message-
> From: Fan Zhang [mailto:roy.fan.zh...@intel.com]
> Sent: Tuesday, June 26, 2018 10:11 AM
> To: dev@dpdk.org
> Cc: pablo.de.lara.gua...@intel.com; Zhoujian (jay) ;
> sta...@dpdk.org
> Subject: [PATCH v2] crypto/virtio: fix iv physical address
>
> The physical address
On 03-Jul-18 1:09 PM, Alejandro Lucero wrote:
This patchset adds, mainly, a check for ensuring IOVAs are within a
restricted range due to addressing limitations with some devices. There
are two known cases: NFP and IOMMU VT-d emulation.
With this check IOVAs out of range are detected and PMDs ca
Monday, July 2, 2018 9:58 PM, Yongseok Koh:
> Subject: Re: [dpdk-dev] [PATCH] net/mlx5: activate Verbs cleanup on
> removal
>
>
> > On Jul 1, 2018, at 10:13 PM, Matan Azrad wrote:
> >
> > Starting from rdma-core v19, Mellanox OFED 4.4, the Verbs resources
> > cleanup is properly activated in plu
On 03-Jul-18 1:09 PM, Alejandro Lucero wrote:
Linux kernel uses a really high address as starting address for
serving mmaps calls. If there exists addressing limitations and
IOVA mode is VA, this starting address is likely too high for
those devices. However, it is possible to use a lower address
On 03-Jul-18 1:09 PM, Alejandro Lucero wrote:
A device can suffer addressing limitations. This functions checks
memsegs have iovas within the supported range based on dma mask.
PMD should use this during initialization if supported devices
suffer addressing limitations, returning an error if thi
Registered new dynamic logtype for driver and
replaced SNOW3G_LOG_ERR and CDEV_LOG_ERR
with the new SNOW3G_LOG macro, which uses the new logtype.
Signed-off-by: Pablo de Lara
---
drivers/crypto/snow3g/rte_snow3g_pmd.c | 25 ++-
drivers/crypto/snow3g/rte_snow3g_pmd_ops
Hi Thomas:
<...>
> > +enum eth_dev_req_type {
> > + REQ_TYPE_ATTACH,
> > + REQ_TYPE_PRE_DETACH,
> > + REQ_TYPE_DETACH,
> > + REQ_TYPE_ATTACH_ROLLBACK,
> > +};
>
> These constants are missing an ethdev prefix.
OK, will fix.
>
> > +
> > +struct eth_dev_mp_req {
> > + enum eth_dev_req_t
From: Ilia Kurakin
The patch changes rx_burst profiling approach:
1. VTune's instrumentation is removed
2. empty hook callback for profiling is added
This way all VTune-specific logic moves to the VTune side. Hook is enabled
only when CONFIG_RTE_ETHDEV_PROFILE_WITH_VTUNE option is
Hi Sunil,
Please see inline.
Thanks,
Anoob
On 03-07-2018 11:57, Sunil Kumar Kori wrote:
External Email
Hello Anoob,
Regards
Sunil Kumar
-Original Message-
From: Joseph, Anoob [mailto:anoob.jos...@caviumnetworks.com]
Sent: Thursday, June 28, 2018 4:13 PM
To: Sunil Kumar Kori ; Bru
Hi,
Gentle reminder!
Thanks,
Anoob
On 19-06-2018 19:37, Anoob Joseph wrote:
External Email
Hi Bruce,
Thanks for the feedback. Please see inline.
+ Hemant, Nikhil, Sunil, Gage, Harry, Narender, Pavan, Thomas, Akhil
On 19/06/18 15:39, Bruce Richardson wrote:
On Tue, Jun 19, 2018 at 03:34
On Tuesday, July 07/03/18, 2018 at 07:57:55 +0530, Jack Min wrote:
> Hey Rahul,
>
> Thank you, those two are the ways to achieve that.
>
> Personally I prefer the option 1 but with a little bit difference, something
> like:
>
> struct rte_flow_action_of_set_nw_ipv4 {
> uint32_t ipv
Instead of having a static field for the buffer manager
MB_MGR in the queue pair structure, use the provided API
that allocates memory for it and store a pointer to it.
Signed-off-by: Pablo de Lara
---
drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 10 +-
drivers/crypto/aesni_mb/rt
03/07/2018 14:59, Zhang, Qi Z:
> > > +/**
> > > + * this is a synchronous wrapper for secondary process send
> > > + * request to primary process, this is invoked when an attach
> > > + * or detach request issued from primary.
> > > + */
> > > +int eth_dev_request_to_primary(struct eth_dev_mp_req *
Hi Shally,
> -Original Message-
> From: Shally Verma [mailto:shally.ve...@caviumnetworks.com]
> Sent: Wednesday, May 16, 2018 7:05 AM
> To: De Lara Guarch, Pablo
> Cc: Trahe, Fiona ; akhil.go...@nxp.com; dev@dpdk.org;
> pathr...@caviumnetworks.com; Sunila Sahu ;
> Ashish Gupta
>
> Subje
HI Fiona
Thanks for review. I was just about to send lib patch v4. So for now, I
couldn't consider all input but some of them.
But , in any case, this version is experimental so it is open for further
feedback after 1st version go in.
Rest, please see my feedback inline.
>-Original Messag
Hi Shally,
> -Original Message-
> From: Shally Verma [mailto:shally.ve...@caviumnetworks.com]
> Sent: Wednesday, May 16, 2018 7:05 AM
> To: De Lara Guarch, Pablo
> Cc: Trahe, Fiona ; akhil.go...@nxp.com; dev@dpdk.org;
> pathr...@caviumnetworks.com; Sunila Sahu ;
> Ashish Gupta
>
> Subje
>-Original Message-
>From: Trahe, Fiona [mailto:fiona.tr...@intel.com]
>Sent: 03 July 2018 20:21
>To: Verma, Shally ; De Lara Guarch, Pablo
>
>Cc: akhil.go...@nxp.com; dev@dpdk.org; Athreya, Narayana Prasad
>; Sahu, Sunila
>; Gupta, Ashish ; Trahe,
>Fiona
>Subject: RE: [PATCH v3 5/6]
> -Original Message-
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Tuesday, July 3, 2018 10:11 PM
> To: Zhang, Qi Z
> Cc: dev@dpdk.org; Burakov, Anatoly ; Ananyev,
> Konstantin ; Richardson, Bruce
> ; Yigit, Ferruh ; Shelton,
> Benjamin H ; Vangati, Narender
>
> Subject:
> -Original Message-
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Tuesday, July 3, 2018 5:56 PM
> To: Zhang, Qi Z
> Cc: dev@dpdk.org; Burakov, Anatoly ; Ananyev,
> Konstantin ; Richardson, Bruce
> ; Yigit, Ferruh ; Shelton,
> Benjamin H ; Vangati, Narender
>
> Subject:
> -Original Message-
> From: Verma, Shally [mailto:shally.ve...@cavium.com]
> Sent: Tuesday, July 3, 2018 4:00 PM
> To: Trahe, Fiona ; De Lara Guarch, Pablo
>
> Cc: akhil.go...@nxp.com; dev@dpdk.org; Athreya, Narayana Prasad
> ; Sahu, Sunila ;
> Gupta, Ashish
>
> Subject: RE: [PATCH
>-Original Message-
>From: Trahe, Fiona [mailto:fiona.tr...@intel.com]
>Sent: 03 July 2018 20:41
>To: Verma, Shally ; De Lara Guarch, Pablo
>
>Cc: akhil.go...@nxp.com; dev@dpdk.org; Athreya, Narayana Prasad
>; Sahu, Sunila
>; Gupta, Ashish
>Subject: RE: [PATCH v3 5/6] crypto/openssl:
> -Original Message-
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Tuesday, July 3, 2018 5:28 PM
> To: Zhang, Qi Z
> Cc: dev@dpdk.org; Burakov, Anatoly ; Ananyev,
> Konstantin ; Richardson, Bruce
> ; Yigit, Ferruh ; Shelton,
> Benjamin H ; Vangati, Narender
>
> Subject:
This patch series add support for asymmetric crypto in DPDK
librte_cryptodev framework along with documentation updates.
This patch series is divided in to following categories:
1. library patches with asymmetric API, xform and capability
definitions
2. Programmer Guide updates with asymmetric
Add rte_crypto_asym.h with supported xfrms
and associated op structures and APIs
API currently supports:
- RSA Encrypt, Decrypt, Sign and Verify
- Modular Exponentiation and Inversion
- DSA Sign and Verify
- Deffie-hellman private key exchange
- Deffie-hellman public key exchange
- Deffie-hellman
From: Ashish Gupta
Extend cryptodev with asymmetric capability APIs and
definitions.
Signed-off-by: Shally Verma
Signed-off-by: Sunila Sahu
Signed-off-by: Ashish Gupta
Signed-off-by: Umesh Kartha
---
lib/librte_cryptodev/rte_cryptodev.c | 76 ++
lib/librte_cryptod
From: Sunila Sahu
Update cryptodev programmer guide with description of
asymmetric crypto framework in lib cryptodev.
Signed-off-by: Shally Verma
Signed-off-by: Sunila Sahu
Signed-off-by: Ashish Gupta
Signed-off-by: Umesh Kartha
---
doc/guides/prog_guide/cryptodev_lib.rst | 290
From: Umesh Kartha
Extend DPDK librte_cryptodev to:
- define asym op type in rte_crypto_op_type and associated
op pool create/alloc APIs
- define asym session and associated session APIs
If PMD shows in its feature flag that it supports both sym and
asym then it must support those on all its q
ethdev layer introduced checks for application requested RSS hash
functions and returns error for ones unsupported by hardware
This check breaks some sample applications which blindly configures
RSS hash functions without checking underlying hardware support.
Updated examples to mask out unsuppor
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Ferruh Yigit
> Sent: Thursday, June 28, 2018 3:16 PM
> To: Thomas Monjalon
> Cc: dev@dpdk.org; Yigit, Ferruh ; David Marchand
> ; Olivier Matz ; Horton,
> Remy
> Subject: [dpdk-dev] [PATCH] ethdev: document xstats API assumption
>
> Document
l2fwd_fork is not complied by default, this will make it compile
Fixes: 95e8005a56e8 ("examples/l2fwd_fork: new app")
Signed-off-by: Emma Kenny
---
examples/multi_process/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/examples/multi_process/Makefile b/examples/multi_process/Makefi
Adds support for the v0.50 of the IPsec Multi-buffer lib.
The library now exposes its version, with the idea
of maintaining backwards compatibility in the future,
avoiding breaking the compilation of the PMD every time
there is a new version available.
Signed-off-by: Pablo de Lara
---
doc/guides
Adds support for the v0.50 of the IPsec Multi-buffer lib.
The library now exposes its version, with the idea
of maintaining backwards compatibility in the future,
avoiding breaking the compilation of the PMD every time
there is a new version available.
Signed-off-by: Pablo de Lara
---
doc/guides
On Tue, Jul 03, 2018 at 09:17:56AM +0200, Nélio Laranjeiro wrote:
> On Mon, Jul 02, 2018 at 06:07:03PM -0700, Yongseok Koh wrote:
> > On Wed, Jun 27, 2018 at 05:07:34PM +0200, Nelio Laranjeiro wrote:
[...]
> flow_drop_queue is also confusing as it is a drop hash rx queue, it can
> be used without a
ethdev layer introduced checks for application requested RSS hash
functions and returns error for ones unsupported by hardware
This check breaks some sample applications which blindly configures
RSS hash functions without checking underlying hardware support.
Updated examples to mask out unsuppor
If "--disable-crc-strip" testpmd parameter issued, it removes the
DEV_RX_OFFLOAD_CRC_STRIP flag.
With introduction of new DEV_RX_OFFLOAD_KEEP_CRC offload flag, this
flag also should be set when this parameter issued.
Fixes: 3d12dceed2df ("ethdev: add new offload flag to keep CRC")
Signed-off-by:
On 7/1/2018 12:05 PM, ido goshen wrote:
> From: ido g
>
> Support rx of in direction packets only
> Useful for apps that also tx to eth_pcap ports in order to not see them
> echoed back in as rx when out direction is also captured
>
> Example:
> In case using rx_iface and sending *single* packet
On 7/2/2018 10:27 PM, Thomas Monjalon wrote:
> A new offload API has been introduced in DPDK 17.11.
>
> This patchset resumes the work started by Ferruh (RFC)
> to definitely drop the old offload API.
>
> There are:
> - 3 patches to remove some useless code where the old API was found.
> - 1 patc
Replace the BSD license header with the SPDX tag.
Signed-off-by: Ed Czeck
---
drivers/net/ark/Makefile| 32 ++--
drivers/net/ark/ark_ddm.c | 33 ++---
drivers/net/ark/ark_ddm.h | 33 ++---
dri
03/07/2018 17:16, Zhang, Qi Z:
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> >
> > Hi Qi,
> >
> > Sorry I do not understand neither the commit log, nor the doxygen.
> > If it can help, consider your reader is in a bad mood and needs a pleasant
> > description.
>
> OK, I think is not a g
03/07/2018 17:03, Zhang, Qi Z:
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > 03/07/2018 14:59, Zhang, Qi Z:
> > > > > +do_eth_dev_attach(const char *devargs, uint16_t *port_id);
> > > >
> > > > So you are duplicating rte_eth_dev_attach which is flawed in its
> > > > design and should be
03/07/2018 17:08, Zhang, Qi Z:
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > 02/07/2018 07:44, Qi Zhang:
> > > Introduce API rte_eth_dev_lock and rte_eth_dev_unlock to let
> > > application lock or unlock on specific ethdev, a locked device can't
> > > be detached, this help applicaiton
This patchset introduces a new EAL API for querying devices,
filtered by arbitrary properties.
The following elements are introduced to this end:
* A new object, "rte_class", is used to describe
the device class abstraction layer (eth, crypto, ...).
* Both rte_bus and rte_class now offer a
rte_devargs_parse becomes non-variadic,
rte_devargs_parsef becomes the variadic version, to be used to compose
device strings.
Signed-off-by: Gaetan Rivet
---
drivers/net/failsafe/failsafe_args.c| 2 +-
drivers/net/failsafe/failsafe_eal.c | 2 +-
lib/librte_eal/common/eal_commo
Signed-off-by: Gaetan Rivet
---
lib/Makefile | 3 +--
lib/librte_kvargs/Makefile | 2 +-
2 files changed, 2 insertions(+), 3 deletions(-)
diff --git a/lib/Makefile b/lib/Makefile
index d82462ba2..e8e903c8f 100644
--- a/lib/Makefile
+++ b/lib/Makefile
@@ -4,6 +4,7 @@
include $(RTE_
This function permits defining additional terminating characters,
ending the parsing to arbitrary delimiters.
Signed-off-by: Gaetan Rivet
---
lib/Makefile | 1 +
lib/librte_kvargs/rte_kvargs.c | 25 +
lib/librte_kvargs/rte_kvargs.h
Error logs in kvargs parsing should be better handled in components
calling the library.
This library must be as lean as possible.
Signed-off-by: Gaetan Rivet
---
lib/librte_kvargs/rte_kvargs.c | 22 +-
1 file changed, 5 insertions(+), 17 deletions(-)
diff --git a/lib/librt
Signed-off-by: Gaetan Rivet
---
lib/librte_eal/bsdapp/eal/Makefile | 1 +
lib/librte_eal/common/Makefile | 2 +-
lib/librte_eal/common/eal_common_class.c | 62 +++
lib/librte_eal/common/include/rte_class.h | 121 +
lib/librte_eal
Signed-off-by: Gaetan Rivet
---
lib/librte_eal/common/include/rte_common.h | 23 +++
1 file changed, 23 insertions(+)
diff --git a/lib/librte_eal/common/include/rte_common.h
b/lib/librte_eal/common/include/rte_common.h
index 434adfd45..0dd832728 100644
--- a/lib/librte_eal/c
Signed-off-by: Gaetan Rivet
---
lib/librte_eal/common/include/rte_class.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/lib/librte_eal/common/include/rte_class.h
b/lib/librte_eal/common/include/rte_class.h
index b5e550a34..e8176f5e1 100644
--- a/lib/librte_eal/common/include/rte_class
This function is private to the EAL.
It is used to parse each layers in a device description string,
and store the result in an rte_devargs structure.
Signed-off-by: Gaetan Rivet
---
lib/librte_eal/common/eal_common_devargs.c | 144
lib/librte_eal/common/eal_private
1 - 100 of 150 matches
Mail list logo
