> -Original Message-
> From: Stephen Hemminger [mailto:step...@networkplumber.org]
> Sent: Wednesday, August 28, 2019 1:43 AM
> To: Nitin Katiyar
> Cc: dev@dpdk.org; Venkatesan Pradeep
>
> Subject: Re: [dpdk-dev] [PATCH 1/2] bus/pci: Fail rte_pci_probe if prob
rte_bus_probe() doesn't return error. As a result rte_eal_init()
doesn't catch this error and thus making dpdk initialization
successful despite probe failing for devices.
This patch returns error if probe fails for any of device.
Signed-off-by: Nitin Katiyar
---
lib/librte_
when devices are actually
probed.
Signed-off-by: Nitin Katiyar
Signed-off-by: Venkatesan Pradeep
---
drivers/bus/pci/pci_common.c | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/drivers/bus/pci/pci_common.c b/drivers/bus/pci/pci_common.c
index 6b46b4f..25d1002 100644
iterations.
With this patch, PMD RCU synchronization will be performed after fixed
interval instead after a fixed number of iterations. This will ensure
that even if the packet processing load is high the RCU synchronization
will not be delayed long.
Signed-off-by: Anju Thomas
Signed-off-by: Nitin
g.com]
Sent: Friday, August 17, 2018 7:36 PM
To: Nitin Katiyar ; dev@dpdk.org
Cc: Maxime Coquelin ; Bie, Tiwei
; Zhihong Wang
Subject: Re: vhost: initializing iotlb memory only when IOMMU feature is
enabled.
On 17.08.2018 23:19, Nitin Katiyar wrote:
> DPDK 17.11 introduced the IOMMU feature whic
breaks the backward compatibility for applications like OVS
due to increase in the DPDK memory footprint and causes upgrade
failures.
This patch is to do iotlb_init only if IOMMU feature is
enabled on device.
Signed-off-by: Nitin Katiyar
---
lib/librte_vhost/iotlb.c | 7 +++
lib
breaks the backward compatibility for applications like OVS due to increase
in the DPDK memory footprint and causes upgrade failures.
This patch is to do iotlb_init only if IOMMU feature is enabled on device.
Signed-off-by: Nitin Katiyar
---
lib/librte_vhost/iotlb.c | 7 +++
lib
This patch is to do iotlb_init only if IOMMU feature is enabled on device.
Signed-off-by: Nitin Katiyar
---
lib/librte_vhost/iotlb.c | 7 +++
lib/librte_vhost/vhost_user.c | 7 +++
2 files changed, 14 insertions(+)
diff --git a/lib/librte_vhost/iotlb.c b/lib/librte_vhost/iotlb.c
Thanks Shahaf, it worked after removing the options you specified.
Regards,
Nitin
-Original Message-
From: Nélio Laranjeiro [mailto:nelio.laranje...@6wind.com]
Sent: Thursday, May 31, 2018 3:23 PM
To: Nitin Katiyar
Cc: Shahaf Shuler ; dev@dpdk.org
Subject: Re: [dpdk-dev] Compilation of
Yes,I installed it using --dpdk --upstream-libs. What is the way forward now?
Regards,
Nitin
-Original Message-
From: Nélio Laranjeiro [mailto:nelio.laranje...@6wind.com]
Sent: Thursday, May 31, 2018 1:36 PM
To: Nitin Katiyar
Cc: Shahaf Shuler ; dev@dpdk.org
Subject: Re: [dpdk-dev
...@mellanox.com]
Sent: Thursday, May 31, 2018 10:51 AM
To: Nitin Katiyar ; Nélio Laranjeiro
Cc: dev@dpdk.org
Subject: RE: [dpdk-dev] Compilation of MLX5 driver
Wednesday, May 30, 2018 7:45 PM, Nitin Katiyar:
>
> Hi,
> I was compiling 17.05.02.
> Regards,
> Nitin
>
> -Origina
Hi,
I was compiling 17.05.02.
Regards,
Nitin
-Original Message-
From: Nélio Laranjeiro [mailto:nelio.laranje...@6wind.com]
Sent: Wednesday, May 30, 2018 6:42 PM
To: Nitin Katiyar
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Compilation of MLX5 driver
Hi,
On Wed, May 30, 2018 at 11:54:31AM
Hi,
I am trying to compile MLX5 PMD driver by setting
"CONFIG_RTE_LIBRTE_MLX5_PMD=y" and hitting following compilation error.
fatal error: infiniband/mlx5_hw.h: No such file or directory
I have installed MLNX_OFED _LINUX-4.2-1.2.0 on my Ubuntu 14.04 machine but
still hitting the same error. Am
merged in dpdk branch? If not, where can I find
latest patches?
Regards,
Nitin
-Original Message-
From: Xing, Beilei [mailto:beilei.x...@intel.com]
Sent: Wednesday, February 14, 2018 6:50 AM
To: Nitin Katiyar ; dev@dpdk.org
Cc: Venkatesan Pradeep
Subject: RE: Multi-driver support for
update for kernel driver also?
Regards,
Nitin
-Original Message-----
From: Nitin Katiyar
Sent: Monday, February 12, 2018 11:32 AM
To: dev@dpdk.org
Cc: Venkatesan Pradeep
Subject: RE: dev Digest, Vol 180, Issue 152
Hi Beilei,
I was looking at the patches and have few queries regarding
support-mu
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
Hi,
Does anyone have any inputs/suggestion on this issue?
Regards,
Nitin
-Original Message-
From: Nitin Katiyar
Sent: Wednesday, October 25, 2017 11:57 AM
To: 'Stephen Hemminger'
Cc: dev@dpdk.org
Subject: RE: [dpdk-dev] Issue with MTU/max_rx_pkt_len handling by different
Frame Size. This should be addressed by drivers not the
application.
Regards,
Nitin
-Original Message-
From: Stephen Hemminger [mailto:step...@networkplumber.org]
Sent: Tuesday, October 24, 2017 6:31 PM
To: Nitin Katiyar
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Issue with MTU/max_
ing same application on different NICs and PMD drivers need to be
fixed to have consistent behavior with MTU/Max Frame Size settings.
Regards,
Nitin Katiyar
Hi,
We are using OVS-DPDK (2.6 version) with Fortville NIC (configured in 25G mode)
being used as dpdk port. The setup involves 2 VMs running on 2 different
computes (destination VM in compute with 10G NIC while originating VM is in
compute with Fortville NIC). All the interfaces in the path ar
20 matches
Mail list logo
