Hi Marcelo,
Sunday, February 11, 2018 9:31 PM, Marcelo Ricardo:
> On Thu, Feb 08, 2018 at 06:55:54AM +, Ophir Munk wrote:
> > From: Moti Haimovsky
> >
> > This patch updates mlx4 documentation with flow configuration
> > limitations imposed by NIC hardware and PMD implementation
> >
> > Signe
On 09/02/18 16:10, Radu Nicolau wrote:
When AES-256 was used aes-128 was printed in the console
Fixes: fa9088849e12 ("examples/ipsec-secgw: support AES 256")
Signed-off-by: Radu Nicolau
Acked-by: Anoob Joseph
---
examples/ipsec-secgw/sa.c | 3 ++-
1 file changed, 2 insertions(+), 1 dele
Hi Beilei,
I was looking at the patches and have few queries regarding
support-multi-driver.
1) With these patches, we have 2 different values for some of the global
registers depending upon whether single driver or multi-driver is using all
ports of the NIC. Does it impact any functionality/per
Since struct rte_eth_dev_data used in the fast path,
making it as cache aligned.
Fixes: af75078fece3 ("first public release")
Fixes: 5b7ba31148a8 ("ethdev: add port ownership")
Cc: Matan Azrad
Cc: Thomas Monjalon
Cc: Konstantin Ananyev
Signed-off-by: Jerin Jacob
Signed-off-by: Pavan Nikhiles
-Original Message-
> Date: Sat, 10 Feb 2018 18:23:42 +
> From: Matan Azrad
> To: Jerin Jacob , "dev@dpdk.org"
>
> CC: Thomas Monjalon , Konstantin Ananyev
> , Pavan Nikhilesh
>
> Subject: RE: [dpdk-dev] [PATCH] ethdev: fix a regression due to cache
> alignment issue
>
> Hi Jerin
Expose the deferred queue configuration capability and enhance
i40e_dev_[rx|tx]_queue_[setup|release] to handle the situation when
device already started.
Signed-off-by: Qi Zhang
---
drivers/net/i40e/i40e_ethdev.c | 6
drivers/net/i40e/i40e_rxtx.c | 62 +++
Add new command to setup queue:
queue setup (rx|tx) (port_id) (queue_idx) (ring_size)
rte_eth_[rx|tx]_queue_setup will be called corresponsively
Signed-off-by: Qi Zhang
---
app/test-pmd/cmdline.c | 136
doc/guides/testpmd_app_ug/testpmd_funcs.rs
The patch let etherdev driver expose the capability flag through
rte_eth_dev_info_get when it support deferred queue configuraiton,
then base on the flag rte_eth_[rx|tx]_queue_setup could decide
continue to setup the queue or just return fail when device already
started.
Signed-off-by: Qi Zhang
-
Add two parameters:
rxq-setup: set the number of RX queues be setup before device started
txq-setup: set the number of TX queues be setup before device started.
Signed-off-by: Qi Zhang
---
app/test-pmd/parameters.c | 29 +
app/test-pmd/testpmd.c
According to exist implementation,rte_eth_[rx|tx]_queue_setup will
always return fail if device is already started(rte_eth_dev_start).
This can't satisfied the usage when application want to deferred setup
part of the queues while keep traffic running on those queues already
be setup.
example:
rt
After reset owner in below patch, we failed to set owner before
sending further vhost messages. It is OK with vhost user implemented
DPDK/VPP/Contrail, but it sees "Operation not permitted" error when
used with vhost kernel.
We fix this by setting owner every time the device is started.
Fixes: 0d
intr_handle->fd was wrongly initialized as 0 (usually as the stdio fd)
when virtio-user is used with vhost-kernel. So the interrupt thread
might wrongly treat stdin events as LSC interrupts.
Fixes: 3d4fb6fd2505 ("net/virtio-user: support Rx interrupt")
Cc: sta...@dpdk.org
Signed-off-by: Jianfeng
The original words are not accurate. For example, as destroy_device
callback gets called, it does not necessarily mean that the connection
is closed.
Fixes: ee584e9710b9 ("vhost: add driver on top of the library")
Cc: sta...@dpdk.org
Cc: mtetsu...@gmail.com
Signed-off-by: Jianfeng Tan
---
driv
Patch 1: a trivial fix on reword a log message.
Patch 2: fix the rxq interrupt mode when virtio-user is used
with vhost kernel.
Patch 3: a trivial fix on LSC fd init when virtio-user is used
with vhost kernel.
Jianfeng Tan (3):
net/vhost: fix incorrect log info
net/virtio-use
On Thu, Feb 08, 2018 at 06:55:54AM +, Ophir Munk wrote:
> From: Moti Haimovsky
>
> This patch updates mlx4 documentation with flow
> configuration limitations imposed by NIC hardware and
> PMD implementation
>
> Signed-off-by: Ophir Munk
> ---
> doc/guides/nics/mlx4.rst | 77
> +++
Fail-safe PMD manages the states of its sub-devices gradually:
DEV_UNDEFINED, DEV_PARSED, DEV_PROBED, DEV_ACTIVE, DEV_STARTED.
When the sub-device arguments successfully was parsed, the state is
raised from DEV_UNDEFINED to DEV_PARSED.
When the sub-device successfully was probed, the state is rais
Fail-safe PMD uses per sub-device flag called "remove" to indicate the
scope where the sub-device was removed physically and its SW resources
should be released.
This flag is set when fail-safe gets RMV notification about the
physical removal of the sub-device and should be unset when all the
sub-
Fail-safe uses periodic alarm mechanism, running from the host thread,
to manage the hot-plug events of its sub-devices. This management
requires a lot of sub-devices PMDs operations (stop,close,start,etc).
While the hot-plug alarm runs in the host thread, the application may
call fail-safe operat
The hot-plug alarm mechanism of fail-safe PMD is responsible for
handling removed devices during a plug-out event and to restore them
back to activity following a plug-in event.
Fail-safe sets a flag called "pending_alarm" to validate that only one
alarm callback is pending at any time. While this
This series fixes failsafe race between control commands to the asynchronic
plug-out\in processes.
V6(matan):
Full lock based fix.
Change the remove flag scope until SW resources release.
v5(Matan):
Change defines names to failsafe convention (UNSAFE).
split a fix patch.
v4(Matan):
Rebase on t
Date: 31 Jan 2018
Attendees:
Bruce Richardson,
Ferruh Yigit,
Hemant Agrawal,
Jerin Jacob,
Konstantin Ananyev,
Olivier Matz,
Thomas Monjalon
Yuanhan Liu
Stephen Hemminger
Topic: Future plans for next-build tree and meson build system work in general
across 18.05 and 18.08 releases.
* Some work
Hi Adrien,
Small doc issues.
Thursday, February 8, 2018 6:37 PM, Adrien Mazarguil:
> Subject: [PATCH v1] net/mlx: control netdevices through ioctl only
>
> Several control operations implemented by these PMDs affect netdevices
> through sysfs, itself subject to file system permission checks enfo
Signed-off-by: Xiaohua Zhang
---
usertools/dpdk-devbind.py | 8
1 file changed, 8 insertions(+)
diff --git a/usertools/dpdk-devbind.py b/usertools/dpdk-devbind.py
index 18d9386..f488318 100755
--- a/usertools/dpdk-devbind.py
+++ b/usertools/dpdk-devbind.py
@@ -22,11 +22,14 @@
It is suggested to use PCI BDF to identify a port for port addition
in OVS-DPDK. While mlx5 has its own naming style: name it by ib dev
name. This breaks the typical OVS DPDK use case and brings more puzzle
to the end users.
To fix it, this patch changes it to use PCI BDF as the name, too.
Judging
> -Original Message-
> From: Maxime Coquelin [mailto:maxime.coque...@redhat.com]
> Sent: Friday, February 9, 2018 10:27 PM
> To: Bie, Tiwei ; y...@fridaylinux.org; Yigit, Ferruh
> ; vict...@redhat.com
> Cc: dev@dpdk.org; sta...@dpdk.org; Wang, Zhihong
> ; Xu, Qian Q ; Yao, Lei A
> ; Maxim
25 matches
Mail list logo
