-Original Message-
> Date: Thu, 5 Apr 2018 08:12:28 -0700
> From: Stephen Hemminger
> To: jerin.ja...@caviumnetworks.com
> Cc: dev@dpdk.org, Stephen Hemminger
> Subject: [PATCH] net/octeneontx: fix warnings
> X-Mailer: git-send-email 2.16.3
>
> This is fix for Coverity Devect 268319 abo
-Original Message-
> Date: Thu, 5 Apr 2018 14:15:46 +0100
> From: Harry van Haaren
> To: dev@dpdk.org
> CC: Harry van Haaren
> Subject: [dpdk-dev] [PATCH] eal/service: remove experimental tags
> X-Mailer: git-send-email 2.7.4
>
> This commit removes the experimental tags from the
> servi
> -Original Message-
> From: Adrien Mazarguil [mailto:adrien.mazarg...@6wind.com]
> Sent: Thursday, April 5, 2018 10:39 PM
> To: Zhang, Qi Z
> Cc: Thomas Monjalon ; Yigit, Ferruh
> ; dev@dpdk.org; Lu, Wenzhuo
> ; Wu, Jingjing ; Ajit Khaparde
> ; Somnath Kotur
> ; John Daley ; Hyong
> You
Add new interrupt handle type of RTE_INTR_HANDLE_DEV_EVENT, for
device event interrupt monitor.
Signed-off-by: Jeff Guo
Reviewed-by: Jianfeng Tan
---
v21->v20:
no change
---
lib/librte_eal/common/include/rte_eal_interrupts.h | 1 +
lib/librte_eal/linuxapp/eal/eal_interrupts.c | 11 +-
This patch aims to add a general device event monitor framework at
EAL device layer, for device hotplug awareness and actions adopted
accordingly. It could also expand for all other types of device event
monitor, but not in this scope at the stage.
To get started, users firstly call below new adde
Use testpmd for example, to show how an application uses device event
APIs to monitor the hotplug events, including both hot removal event
and hot insertion event.
The process is that, testpmd first enable hotplug by below commands,
E.g. ./build/app/testpmd -c 0x3 --n 4 -- -i --hot-plug
then tes
In order to handle the uevent which has been detected from the kernel
side, add uevent parse and process function to translate the uevent into
device event, which user has subscribed to monitor.
Signed-off-by: Jeff Guo
Reviewed-by: Jianfeng Tan
---
v21->v20:
refine release note and some code cle
About hot plug in dpdk, We already have proactive way to add/remove devices
through APIs (rte_eal_hotplug_add/remove), and also have fail-safe driver
to offload the fail-safe work from the app user. But there are still lack
of a general mechanism to monitor hotplug event for all driver, now the
hot
On 4/6/2018 5:58 AM, Thomas Monjalon wrote:
05/04/2018 18:10, Jeff Guo:
In order to handle the uevent which has been detected from the kernel
side, add uevent parse and process function to translate the uevent into
device event, which user has subscribed to monitor.
Signed-off-by: Jeff Guo
-
On 4/6/2018 5:54 AM, Thomas Monjalon wrote:
05/04/2018 18:10, Jeff Guo:
--- a/lib/librte_eal/rte_eal_version.map
+++ b/lib/librte_eal/rte_eal_version.map
@@ -260,3 +260,13 @@ EXPERIMENTAL {
rte_socket_id_by_idx;
} DPDK_18.02;
+
+EXPERIMENTAL {
+ global:
+
+ rte_dev_e
On 4/6/2018 5:48 AM, Thomas Monjalon wrote:
05/04/2018 18:10, Jeff Guo:
Use testpmd for example, to show how an application uses device event
APIs to monitor the hotplug events, including both hot removal event
and hot insertion event.
The process is that, testpmd first enable hotplug by belo
thanks.
On 4/6/2018 12:22 AM, Tan, Jianfeng wrote:
On 4/6/2018 12:10 AM, Jeff Guo wrote:
In order to handle the uevent which has been detected from the kernel
side, add uevent parse and process function to translate the uevent into
device event, which user has subscribed to monitor.
Signed-
Shocking and very sad...Venky's contributions, and his persona, as you
outlined are significant and will be remembered.
Robert (Bob) Monkman
Director, Networking Software Strategy & Ecosystem Programs
Arm
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490
Skype: robert.monkman
From: gov
-Original Message-
Hi Konstantin,
>
> > -Original Message-
> > From: Jerin Jacob [mailto:jerin.ja...@caviumnetworks.com]
> > Sent: Thursday, April 5, 2018 9:02 AM
> > To: Ananyev, Konstantin
> > Cc: Olivier Matz ; dev@dpdk.org; Richardson, Bruce
> >
> > Subject: Re: [dpdk-dev]
On Thu, 5 Apr 2018 23:57:47 +
"Ananyev, Konstantin" wrote:
> > -Original Message-
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> > Sent: Thursday, April 5, 2018 10:11 PM
> > To: Richardson, Bruce
> > Cc: Stephen Hemminger ; dev@dpdk.org; Stephen
> > Hemmi
Update bnxt PMD to new ethdev offloads API.
Signed-off-by: Ajit Khaparde
--
v1->v2: return an error if requested offload flags do not
match supported offload capabilities.
v2->v3: modify the code based on review comments.
v3->v4: fix compilation for i686 configuration.
---
drivers/net/bnxt/bnxt_
If Rx descriptors are not available, pkts are dropped by default.
Fix rx_drop_en setting in bnxt_dev_info_get_op to reflect it.
Signed-off-by: Ajit Khaparde
---
drivers/net/bnxt/bnxt_ethdev.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/net/bnxt/bnxt_ethdev.c b/d
> -Original Message-
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Thomas Monjalon
> Sent: Thursday, April 5, 2018 10:11 PM
> To: Richardson, Bruce
> Cc: Stephen Hemminger ; dev@dpdk.org; Stephen
> Hemminger
> Subject: Re: [dpdk-dev] [PATCH 2/3] usertools: add hv_uio_setup scr
On Thu, 05 Apr 2018 23:10:33 +0200
Thomas Monjalon wrote:
> 05/04/2018 23:07, Bruce Richardson:
> > On Thu, Apr 05, 2018 at 10:43:39PM +0200, Thomas Monjalon wrote:
> > > 05/04/2018 21:13, Stephen Hemminger:
> > > > Small script to rebind netvsc kernel device to Hyper-V
> > > > networking PMD
On Thu, 05 Apr 2018 23:13:54 +0200
Thomas Monjalon wrote:
> 05/04/2018 23:03, Stephen Hemminger:
> > On Thu, 05 Apr 2018 22:43:39 +0200
> > Thomas Monjalon wrote:
> >
> > > 05/04/2018 21:13, Stephen Hemminger:
> > > > Small script to rebind netvsc kernel device to Hyper-V
> > > > networking
05/04/2018 18:10, Jeff Guo:
> In order to handle the uevent which has been detected from the kernel
> side, add uevent parse and process function to translate the uevent into
> device event, which user has subscribed to monitor.
>
> Signed-off-by: Jeff Guo
> ---
> lib/librte_eal/linuxapp/eal/eal
05/04/2018 18:10, Jeff Guo:
> --- a/lib/librte_eal/rte_eal_version.map
> +++ b/lib/librte_eal/rte_eal_version.map
> @@ -260,3 +260,13 @@ EXPERIMENTAL {
> rte_socket_id_by_idx;
>
> } DPDK_18.02;
> +
> +EXPERIMENTAL {
> + global:
> +
> + rte_dev_event_monitor_start;
> + r
Hi Thomas,
OK, I'll take a fresh look at these.
Thanks,
Erik
> -Original Message-
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Wednesday, April 4, 2018 5:43 PM
> To: Carrillo, Erik G
> Cc: dev@dpdk.org; rsanf...@akamai.com; Mcnamara, John
>
> Subject: Re: [dpdk-dev] [PA
05/04/2018 18:10, Jeff Guo:
> Use testpmd for example, to show how an application uses device event
> APIs to monitor the hotplug events, including both hot removal event
> and hot insertion event.
>
> The process is that, testpmd first enable hotplug by below commands,
>
> E.g. ./build/app/testp
On Thu, 05 Apr 2018 23:13:54 +0200
Thomas Monjalon wrote:
> 05/04/2018 23:03, Stephen Hemminger:
> > On Thu, 05 Apr 2018 22:43:39 +0200
> > Thomas Monjalon wrote:
> >
> > > 05/04/2018 21:13, Stephen Hemminger:
> > > > Small script to rebind netvsc kernel device to Hyper-V
> > > > networking
On Thu, 05 Apr 2018 23:07:45 +0200
Thomas Monjalon wrote:
> 05/04/2018 22:59, Stephen Hemminger:
> > On Thu, 05 Apr 2018 22:52:31 +0200
> > Thomas Monjalon wrote:
> >
> > > Hi Stephen,
> > >
> > > Good to see there is a good progress.
> > >
> > > This patch should add an entry in the releas
On Thu, 05 Apr 2018 23:13:54 +0200
Thomas Monjalon wrote:
> 05/04/2018 23:03, Stephen Hemminger:
> > On Thu, 05 Apr 2018 22:43:39 +0200
> > Thomas Monjalon wrote:
> >
> > > 05/04/2018 21:13, Stephen Hemminger:
> > > > Small script to rebind netvsc kernel device to Hyper-V
> > > > networking
Use RFC standard values address and ports for Tx only test as defaults.
But let the user override those values on command line.
Signed-off-by: Stephen Hemminger
---
app/test-pmd/parameters.c | 49 +++
app/test-pmd/testpmd.h| 6 +
a
05/04/2018 23:03, Stephen Hemminger:
> On Thu, 05 Apr 2018 22:43:39 +0200
> Thomas Monjalon wrote:
>
> > 05/04/2018 21:13, Stephen Hemminger:
> > > Small script to rebind netvsc kernel device to Hyper-V
> > > networking PMD. It could be integrated in dpdk-bind, but dpdk-bind
> > > is focused on P
05/04/2018 23:07, Bruce Richardson:
> On Thu, Apr 05, 2018 at 10:43:39PM +0200, Thomas Monjalon wrote:
> > 05/04/2018 21:13, Stephen Hemminger:
> > > Small script to rebind netvsc kernel device to Hyper-V
> > > networking PMD. It could be integrated in dpdk-bind, but dpdk-bind
> > > is focused on P
On Thu, Apr 05, 2018 at 10:43:39PM +0200, Thomas Monjalon wrote:
> 05/04/2018 21:13, Stephen Hemminger:
> > Small script to rebind netvsc kernel device to Hyper-V
> > networking PMD. It could be integrated in dpdk-bind, but dpdk-bind
> > is focused on PCI, and that would get messy.
> >
> > Eventua
05/04/2018 22:59, Stephen Hemminger:
> On Thu, 05 Apr 2018 22:52:31 +0200
> Thomas Monjalon wrote:
>
> > Hi Stephen,
> >
> > Good to see there is a good progress.
> >
> > This patch should add an entry in the release notes.
> > But I guess it is not ready for 18.05?
[...]
> > > +The following
On Thu, 05 Apr 2018 22:43:39 +0200
Thomas Monjalon wrote:
> 05/04/2018 21:13, Stephen Hemminger:
> > Small script to rebind netvsc kernel device to Hyper-V
> > networking PMD. It could be integrated in dpdk-bind, but dpdk-bind
> > is focused on PCI, and that would get messy.
> >
> > Eventually,
On Thu, 05 Apr 2018 22:52:31 +0200
Thomas Monjalon wrote:
> Hi Stephen,
>
> Good to see there is a good progress.
>
> This patch should add an entry in the release notes.
> But I guess it is not ready for 18.05?
>
>
> 05/04/2018 21:13, Stephen Hemminger:
> > +#
> > +# Compile native PMD for H
Hi Stephen,
Good to see there is a good progress.
This patch should add an entry in the release notes.
But I guess it is not ready for 18.05?
05/04/2018 21:13, Stephen Hemminger:
> +#
> +# Compile native PMD for Hyper-V/Azure
> +#
> +CONFIG_RTE_LIBRTE_NETVSC_PMD=n
> +CONFIG_RTE_LIBRTE_NETVSC_DE
05/04/2018 21:13, Stephen Hemminger:
> Small script to rebind netvsc kernel device to Hyper-V
> networking PMD. It could be integrated in dpdk-bind, but dpdk-bind
> is focused on PCI, and that would get messy.
>
> Eventually, this functionality will be built into netvsc driver
> (see vdev_netvsc a
On 04/05/2018 10:08 AM, Tomasz Duszynski wrote:
This patch addresses following meson build issues:
1) Since rte_vdpa.h includes rte_pci.h it introduces pci
dependency thus deps array should be updated accordingly.
2) Since vhost.h includes rte_vdpa.h vdpa.c should be added to
the sour
On 04/05/2018 10:08 AM, Tomasz Duszynski wrote:
This patch addresses following meson build issues:
1) Since rte_vdpa.h includes rte_pci.h it introduces pci
dependency thus deps array should be updated accordingly.
2) Since vhost.h includes rte_vdpa.h vdpa.c should be added to
the sour
On 04/05/2018 06:01 PM, Fan Zhang wrote:
This patchset depends on the following patch and must be applied first:
"lib/librte_vhost: add virtio_crypto.h header file"
(https://dpdk.org/dev/patchwork/patch/37308/)
This patchset adds crypto backend suppport to vhost library
including a proof-of-c
On 04/05/2018 04:37 PM, Jay Zhou wrote:
Since the linux kernel header file virtio_crypto.h has been merged
in 4.9, if we include this header file directly, compilation will be
failed in the old kernels' environment, e.g. the vhost crypto backend
series.
Adding virtio_crypto.h in librte_vhost to
On 04/05/2018 06:01 PM, Fan Zhang wrote:
This patchset depends on the following patch and must be applied first:
"lib/librte_vhost: add virtio_crypto.h header file"
(https://dpdk.org/dev/patchwork/patch/37308/)
This patchset adds crypto backend suppport to vhost library
including a proof-of-c
On 04/05/2018 04:37 PM, Jay Zhou wrote:
Since the linux kernel header file virtio_crypto.h has been merged
in 4.9, if we include this header file directly, compilation will be
failed in the old kernels' environment, e.g. the vhost crypto backend
series.
Adding virtio_crypto.h in librte_vhost to
From: Stephen Hemminger
Add VMBUS network device PMD. This code is based off
of the FreeBSD driver. The file and variable names are
kept the same to help with understanding (with most of
the BSD style warts removed).
Signed-off-by: Stephen Hemminger
---
MAINTAINERS
From: Stephen Hemminger
This patch adds support for an additional bus type Virtual Machine BUS
(VMBUS)is used on Microsoft Hyper-V in Windows 10, Windows Server 2016
and Azure. Most of this code was extracted from FreeBSD and some of
this is from earlier code donated by Brocade.
Only Linux is s
Small script to rebind netvsc kernel device to Hyper-V
networking PMD. It could be integrated in dpdk-bind, but dpdk-bind
is focused on PCI, and that would get messy.
Eventually, this functionality will be built into netvsc driver
(see vdev_netvsc as an example).
Signed-off-by: Stephen Hemminger
This is an experimental driver originally developed by Vyatta/Brocade/ATT
to support DPDK on Hyper-V. It is a native DPDK driver (unlike the TAP
solution) for VMBus. The driver relies on the version UIO for Hyper-V
(uio_hv_generic) which is in upstream kernel next tree (char-misc-next).
It is not
Hi Anatoly,
On Wednesday 04 April 2018 04:51 AM, Anatoly Burakov wrote:
> This patchset introduces dynamic memory allocation for DPDK (aka memory
> hotplug). Based upon RFC submitted in December [1].
>
> Dependencies (to be applied in specified order):
> - IPC asynchronous request API patch [2]
>
Several of you have already heard the very sad news of the passing of our dear
friend and colleague Venky. He was "Mr. DPDK" to many, a nod to his invention
and creation of DPDK about ten years ago (before it was called DPDK.) Of
course his footprints across the industry and literally across t
On 4/6/2018 8:18 AM, zhiyong.y...@intel.com wrote:
In a container environment if the vhost-user backend restarts, there's
no way for it to reconnect to virtio-user. To address this, support for
server mode is added. In this mode the socket file is created by virtio-
user, which the backend then
Pascal, Moti, Ophir,
please comment.
22/03/2018 19:28, Ferruh Yigit:
> It is not clear if tap PMD supports queue specific offloads, removing
> the related code.
>
> Fixes: 95ae196ae10b ("net/tap: use new Rx offloads API")
> Fixes: 818fe14a9891 ("net/tap: use new Tx offloads API")
> Cc: mo...@mell
dpdk-procinfo, as a secondary process, cannot fetch stats for vdev.
This patch enables that by attaching the port from the shared data.
We also fill the eth dev ops, with only some ops works in secondary
process, for example, stats_get().
Note that, we still cannot Rx/Tx packets on the ports whic
We introduced private rte_eth_dev_data to allow vdev to be created
both in primary process and secondary process(es). This is not
friendly to multi-process model, for example, it leads to port id
contention issue if two processes both find the data entry is free.
And to get stats of primary vdev i
v2:
- Add spinlock for vdev device list as suggested by Anatoly.
- Add ring, cxgbe and remove the free in each PMDs as suggested by Matan.
- Rebase on master.
As we know, we have below limitations in vdev:
- dpdk-procinfo cannot get the stats of (most) vdev in primary process;
- dpdk-pdu
As we could add virtual devices from different threads now, we
add a spin lock to protect the vdev device list.
Suggested-by: Anatoly Burakov
Signed-off-by: Jianfeng Tan
---
drivers/bus/vdev/vdev.c | 61 +
1 file changed, 47 insertions(+), 14 dele
To scan the vdevs in primary, we send request to primary process
to obtain the names for vdevs.
Only the name is shared from the primary. In probe(), the device
driver is supposed to locate (or request more) the detail
information from the primary.
Signed-off-by: Jianfeng Tan
---
drivers/bus/vd
Adjust the init sequence: put mp channel init before bus scan
so that we can init the vdev bus through mp channel in the
secondary process before the bus scan.
Signed-off-by: Jianfeng Tan
---
lib/librte_eal/bsdapp/eal/eal.c | 23 +--
lib/librte_eal/linuxapp/eal/eal.c | 23 +
On 4/3/2018 10:06 AM, David Marchand wrote:
> On Mon, Apr 2, 2018 at 6:05 PM, Santosh Shukla
> wrote:
>> Cc: sta...@dpdk.org
>>
>> Signed-off-by: Santosh Shukla
> Reviewed-by: David Marchand
Applied to dpdk-next-net/master, thanks.
On 3/23/2018 9:46 PM, Bruce Richardson wrote:
> On Tue, Mar 20, 2018 at 11:26:26AM +, Andrew Rybchenko wrote:
>> Fixes: 701ac75666b9 ("ethdev: remove versioning of ethdev filter control
>> function")
>>
>> Signed-off-by: Andrew Rybchenko
>> ---
>> lib/librte_ether/meson.build | 2 +-
>> 1 fi
On 4/4/2018 4:53 AM, Rahul Lakkireddy wrote:
> Patch 1 updates document for CXGBEVF PMD.
>
> Patch 2 adds runtime devargs option to CXGBE PMD to keep/strip
> outer vlan in Q-in-Q packets.
>
> Patch 3 updates CXGBE PMD to use the new Rx/TX Offload API.
>
> Thanks,
> Rahul
>
> Kumar Sanghvi (1):
On 4/3/2018 4:06 PM, Matej Vido wrote:
> Offload API is currently used only to setup correct receive function
> for scattered packets.
> Use offloads member instead of bitfield and advertise correct
> capabilities.
>
> Signed-off-by: Matej Vido
Applied to dpdk-next-net/master, thanks.
05/04/2018 15:51, Declan Doherty:
> +struct rte_flow_item_metadata {
> + uint32_t id;/**< field identifier */
> + uint32_t size; /**< field size */
> + uint8_t bytes[];/**< field value */
> +};
Spotted C99 syntax of flexible array.
Are we OK with all
On 4/5/2018 4:36 PM, Stephen Hemminger wrote:
> I noticed Coverity defect in DPDK number 124563 was assigned to me.
>
> It looks like vmxnet3 driver code doesn't handle case where host incorrectly
> sends a frame with out setting SOP bit in first segment. This would lead to
> rxq->start_seq being
05/04/2018 15:51, Declan Doherty:
> +/**
> + * RTE_FLOW_ACTION_TYPE_VTEP_ENCAP
> + *
> + * Virtual tunnel end-point encapsulation action data.
> + *
> + * Non-terminating action by default.
> + */
> +struct rte_flow_action_vtep_encap {
> + struct rte_flow_action_item {
> + enum rte_
In a container environment if the vhost-user backend restarts, there's
no way for it to reconnect to virtio-user. To address this, support for
server mode is added. In this mode the socket file is created by virtio-
user, which the backend then connects to. This means that if the backend
restarts,
Public struct rte_eth_dev_info has a "struct rte_pci_device" field in it
although it is common for all ethdev in all buses.
Replacing pci specific struct with generic device struct and updating
places that are using pci device in a way to get this information from
generic device.
Signed-off-by: F
05/04/2018 15:51, Declan Doherty:
> +Group Count Query
> +~
> +
> +Query group counter which can be associated with multiple flows on a
> specified
> +port.
> +
> +This function allows retrieving of group counters. Data
> +is gathered by special actions which must be present in the
On 4/6/2018 12:10 AM, Jeff Guo wrote:
In order to handle the uevent which has been detected from the kernel
side, add uevent parse and process function to translate the uevent into
device event, which user has subscribed to monitor.
Signed-off-by: Jeff Guo
Other than two nits below,
Reviewe
About hot plug in dpdk, We already have proactive way to add/remove devices
through APIs (rte_eal_hotplug_add/remove), and also have fail-safe driver
to offload the fail-safe work from the app user. But there are still lack
of a general mechanism to monitor hotplug event for all driver, now the
hot
In order to handle the uevent which has been detected from the kernel
side, add uevent parse and process function to translate the uevent into
device event, which user has subscribed to monitor.
Signed-off-by: Jeff Guo
---
v20->v19:
add socket error handler
---
lib/librte_eal/linuxapp/eal/eal_de
Use testpmd for example, to show how an application uses device event
APIs to monitor the hotplug events, including both hot removal event
and hot insertion event.
The process is that, testpmd first enable hotplug by below commands,
E.g. ./build/app/testpmd -c 0x3 --n 4 -- -i --hot-plug
then tes
Add new interrupt handle type of RTE_INTR_HANDLE_DEV_EVENT, for
device event interrupt monitor.
Signed-off-by: Jeff Guo
Reviewed-by: Jianfeng Tan
---
v20->19:
no change
---
lib/librte_eal/common/include/rte_eal_interrupts.h | 1 +
lib/librte_eal/linuxapp/eal/eal_interrupts.c | 11 +-
This patch aims to add a general device event monitor framework at
EAL device layer, for device hotplug awareness and actions adopted
accordingly. It could also expand for all other types of device event
monitor, but not in this scope at the stage.
To get started, users firstly call below new adde
Signed-off-by: Fan Zhang
---
doc/guides/prog_guide/vhost_lib.rst | 25 ++
doc/guides/rel_notes/release_18_05.rst| 5 ++
doc/guides/sample_app_ug/index.rst| 1 +
doc/guides/sample_app_ug/vhost_crypto.rst | 82 +++
4 files changed, 113 inserti
This patch updates the Makefile of vhost library to enable vhost crypto
compiling.
Signed-off-by: Fan Zhang
---
lib/librte_vhost/Makefile| 5 +++--
lib/librte_vhost/meson.build | 8
2 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/lib/librte_vhost/Makefile b/lib/librte
This patch adds public API implementation to vhost crypto.
Signed-off-by: Fan Zhang
---
lib/librte_vhost/rte_vhost_crypto.h| 97 -
lib/librte_vhost/rte_vhost_version.map | 6 +
lib/librte_vhost/vhost_crypto.c| 255 +
3 files changed, 357
This patch adds vhost_crypto sample application to DPDK.
Signed-off-by: Fan Zhang
---
examples/vhost_crypto/Makefile| 32 +++
examples/vhost_crypto/main.c | 541 ++
examples/vhost_crypto/meson.build | 14 +
3 files changed, 587 insertions(+)
create
This patch adds session message handler to vhost crypto.
Signed-off-by: Fan Zhang
---
lib/librte_vhost/vhost_crypto.c | 434
lib/librte_vhost/vhost_user.c | 2 +
2 files changed, 436 insertions(+)
create mode 100644 lib/librte_vhost/vhost_crypto.c
d
This patch adds the implementation that parses virtio crypto request
to dpdk crypto operation.
Signed-off-by: Fan Zhang
---
lib/librte_vhost/rte_vhost_crypto.h | 14 +
lib/librte_vhost/vhost_crypto.c | 622
2 files changed, 636 insertions(+)
create mode
Previously, vhost library lacks the support to the vhost backend
other than net such as adding private data or registering vhost-user
message handlers. This patch fills the gap by adding data pointer and
vhost-user pre and post message handlers to vhost library.
Signed-off-by: Fan Zhang
---
lib/
This patchset depends on the following patch and must be applied first:
"lib/librte_vhost: add virtio_crypto.h header file"
(https://dpdk.org/dev/patchwork/patch/37308/)
This patchset adds crypto backend suppport to vhost library
including a proof-of-concept sample application. The implementation
This patch adds virtio-crypto spec user message structure to
vhost_user.
Signed-off-by: Fan Zhang
---
lib/librte_vhost/rte_vhost.h | 4
lib/librte_vhost/vhost_user.h | 34 +++---
2 files changed, 35 insertions(+), 3 deletions(-)
diff --git a/lib/librte_vhost/r
For completeness:
Fixes: 78c7406b7b5a ("net/mlx5: add Rx HW timestamp")
Cc: sta...@dpdk.org
On Mon, Apr 02, 2018 at 10:01:22AM -0700, Yongseok Koh wrote:
> Signed-off-by: Yongseok Koh
Acked-by: Adrien Mazarguil
> ---
> doc/guides/nics/features/mlx5.ini | 1 +
> 1 file changed, 1 insertion(+)
I noticed Coverity defect in DPDK number 124563 was assigned to me.
It looks like vmxnet3 driver code doesn't handle case where host incorrectly
sends a frame with out setting SOP bit in first segment. This would lead to
rxq->start_seq being NULL.
Maybe something like this would fix it. I don't
Some DPDK applications wrongly assume these requirements:
- no hotplug, i.e. ports are never detached
- all allocated ports are available to the application
Such application iterates over ports by its own mean.
The most common pattern is to request the port count and
assume ports with inde
Some DPDK applications wrongly assume these requirements:
- no hotplug, i.e. ports are never detached
- all allocated ports are available to the application
Such application iterates over ports by its own mean.
The most common pattern is to request the port count and
assume ports with inde
Some DPDK applications wrongly assume these requirements:
- no hotplug, i.e. ports are never detached
- all allocated ports are available to the application
Such application assume a valid port index is in the range [0..count[.
There are three consequences when using such wrong design:
Some DPDK applications wrongly assume these requirements:
- no hotplug, i.e. ports are never detached
- all allocated ports are available to the application
Such application iterates over ports by its own mean.
The most common pattern is to request the port count and
assume ports with index in
On Thu, Apr 05, 2018 at 10:22:28PM +0800, Tiwei Bie wrote:
On Thu, Apr 05, 2018 at 12:10:12PM +0200, Jens Freimann wrote:
Add and initialize descriptor data structures.
Signed-off-by: Jens Freimann
---
[...]
diff --git a/drivers/net/virtio/virtio_ring.h b/drivers/net/virtio/virtio_ring.h
ind
On Thu, Apr 05, 2018 at 10:40:29PM +0800, Tiwei Bie wrote:
On Thu, Apr 05, 2018 at 04:27:51PM +0200, Maxime Coquelin wrote:
On 04/05/2018 12:10 PM, Jens Freimann wrote:
> Add helper functions to set/clear and check descriptor flags.
>
> Signed-off-by: Jens Freimann
> ---
> drivers/net/virtio/
This is fix for Coverity Devect 268319 about uninitialized speed
in an error case. Also drop unnecessary assignment.
Signed-off-by: Stephen Hemminger
---
drivers/net/octeontx/octeontx_ethdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/octeontx/octeontx_ethde
Hi Adrien,
On 04/04/2018 07:08 PM, Adrien Mazarguil wrote:
Hi Andrew,
On Wed, Apr 04, 2018 at 06:30:24PM +0300, Andrew Rybchenko wrote:
Adrien,
On 04/04/2018 05:57 PM, Adrien Mazarguil wrote:
These conversions do not use the adequate function.
Fixes: a9825ccf5bb8 ("net/sfc: support flow API
VF devices are not able to receive promisc or allmulti traffic unless it
fully requests it though Netlink. This will cause the request to be
processed by the PF which will handle the request and enable it.
This requires the VF to be trusted by the PF.
Signed-off-by: Nelio Laranjeiro
Acked-by: A
All Netlink request the PMD will do can also be done by a iproute2 command
line interface, enabling VF behavior configuration without having to modify
the application nor reaching PMD limits (e.g. MAC address number limit).
Signed-off-by: Nelio Laranjeiro
Acked-by: Adrien Mazarguil
---
doc/guid
When MLX5 behaves in VF mode and the hypervisor have **trusted** this VF, to
be able to receive specific traffic some requests must be done to configure
the NIC. There is no API currently available to do it though Verbs, but there
is in Linux side using Netlink.
The specific cases are:
- Enable/d
VF devices are not able to receive traffic unless it fully requests it
though Netlink. This will cause the request to be processed by the PF
which will add/remove the MAC address to the VF table if the VF is trusted.
Signed-off-by: Nelio Laranjeiro
Acked-by: Adrien Mazarguil
---
doc/guides/nic
On Thu, Apr 5, 2018 at 6:03 AM, Thomas Monjalon wrote:
> 20/03/2018 15:12, Ferruh Yigit:
>> On 3/18/2018 1:45 AM, Chas Williams wrote:
>> > From: Chas Williams
>> >
>> > The vmxnet3 never attempts link speed negotiation. As a virtual device
>> > the link speed is vague at best. However, it is i
PF PMD support was based on NSPU interface. This patch changes the
PMD for using the new CPP user space interface which gives more
flexibility for adding new functionalities.
This change just affects initialization with the datapath being the
same than before.
Signed-off-by: Alejandro Lucero
---
New CPP interface makes NSPU interface obsolete. These files are
not needed anymore.
Signed-off-by: Alejandro Lucero
---
drivers/net/nfp/nfp_net_eth.h | 82 --
drivers/net/nfp/nfp_nfpu.c| 108 ---
drivers/net/nfp/nfp_nfpu.h| 55
drivers/net/nfp/nfp_nspu.c| 642
New CPP interface changes the way firmware upload is managed by
the PMD. It also supports different firmware file names for
having specific firmware aplications per card.
Signed-off-by: Alejandro Lucero
---
doc/guides/nics/nfp.rst | 34 ++
1 file changed, 26 inser
NFP PMD PF support requires to access the NFP chip for initialization.
Current NFP PMD PF support was added based on the NSPU interface. This
implies to do initialization through the NSP, a embedded ARM processor
which does initialization tasks on demand. The main problem with this
approach is it r
1 - 100 of 256 matches
Mail list logo
