The pci_id_ixgbe_map table has only PCI_ANY_ID for .subvend and .subdev in all
entries.
Using of IXGBE_SUBDEV_ID_82599_SFP for 'dev' is not correct.
It generates the wrong PMD_INFO_STRING. The output of the program
"dpdk-pmdinfo.py" is confusing.
---
drivers/net/ixgbe/ixgbe_ethdev.c | 5 -
1
Hi Santosh,
On 07/18/2017 07:59 AM, Santosh Shukla wrote:
v4:
Introducing RTE_PCI_DRV_IOVA_AS_VA flag for autodetection of iova va mapping.
If a PCI driver demand for IOVA as VA scheme then the driver can add it in the
PCI driver registration function.
Algorithm to select IOVA as VA for PCI bus
The pci_id_ixgbe_map table has only PCI_ANY_ID for
.subvend and .subdev in all entries. Using of IXGBE_SUBDEV_ID_82599_SFP
for 'dev' is not correct. It generates the wrong PMD_INFO_STRING.
The output of the program "dpdk-pmdinfo.py" is confusing.
---
drivers/net/ixgbe/ixgbe_ethdev.c | 5 -
1 f
The pci_id_ixgbe_map table has only PCI_ANY_ID for
.subvend and .subdev in all entries. Using of IXGBE_SUBDEV_ID_82599_SFP
for 'dev' is not correct. It generates the wrong PMD_INFO_STRING.
The output of the program "dpdk-pmdinfo.py" is confusing.
Signed-off-by: Leonid Myravjev
---
drivers/net/ix
On 7/21/2017 4:07 AM, Jeff Guo wrote:
> Enable the functions set link down and set link up in i40e by check
> phy_type, and fix the issue of auto negotiation failed in XXV710 when
> bind kernel driver after unbind from dpdk driver by modify the speed
> setting distinguish from set link up and down.
Commit 8a04cb612589 ("pci: set default numa node for broken systems")
added logic to default to NUMA node 0 when sysfs numa_node information
was wrong or not available.
Unfortunately there are many devices with wrong NUMA node information
that DPDK does not care about but still show warnings for t
On 7/21/2017 4:22 AM, Ajit Khaparde wrote:
> This patch set fixes some of the issues found during testing.
> Please apply.
>
> v1->v2: incorporate review feedback
>
> net/bnxt: fix log levels for non error conditions.
> net/bnxt: fix to avoid a segfault
> net/bnxt: fix vnic cleanup
> net/
On 7/21/2017 9:56 AM, Qi Zhang wrote:
> Mirror rule id should not exceed the boundary defined by
> IXGBE_MAX_MIRROR_RULES.
>
> Fixes: fe3a45fd4104 ("ixgbe: add VMDq support")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Qi Zhang
Applied to dpdk-next-net/master, thanks.
On 7/21/2017 9:56 AM, Qi Zhang wrote:
> Mirror rule id should not exceed the boundary defined by
> IXGBE_MAX_MIRROR_RULES.
>
> Fixes: fe3a45fd4104 ("ixgbe: add VMDq support")
> Cc: sta...@dpdk.org
>
> Signed-off-by: Qi Zhang
Applied to dpdk-next-net/master, thanks.
On 7/20/2017 8:25 AM, Wei Zhao wrote:
> add support for ipv4-other type in ntuple filter.
>
> Signed-off-by: Wei Zhao
Applied to dpdk-next-net/master, thanks.
On 7/21/2017 12:25 PM, Leonid Myravjev wrote:
> The pci_id_ixgbe_map table has only PCI_ANY_ID for
> .subvend and .subdev in all entries. Using of IXGBE_SUBDEV_ID_82599_SFP
> for 'dev' is not correct. It generates the wrong PMD_INFO_STRING.
> The output of the program "dpdk-pmdinfo.py" is confusing
- Original Message -
From: "cristian dumitrescu"
To: vuon...@viettel.com.vn
Cc: us...@dpdk.org, dev@dpdk.org
Sent: Thursday, July 20, 2017 1:43:37 AM
Subject: RE: [dpdk-dev] Rx Can't receive anymore packet after received 1.5
billion packet.
> -Original Message-
> From: vuon..
On 7/21/2017 11:29 AM, Ferruh Yigit wrote:
> On 7/21/2017 12:25 PM, Leonid Myravjev wrote:
>> The pci_id_ixgbe_map table has only PCI_ANY_ID for
>> .subvend and .subdev in all entries. Using of IXGBE_SUBDEV_ID_82599_SFP
>> for 'dev' is not correct. It generates the wrong PMD_INFO_STRING.
>> The out
On 7/21/2017 11:31 AM, Thomas Monjalon wrote:
13/07/2017 13:28, Hemant Agrawal:
Disabling NUMA warnings on non-NUMA systems.
"EAL: eal_parse_sysfs_value(): cannot open sysfs value
/sys/bus/pci/devices/:00:00.0/numa_node
EAL: numa_node is invalid or not present. Set it 0 as default
E
Hi
I am having 2 VMs on my host. VM1 is running my application with dpdk2.2.0
without any issues and i am using VM2 for dpdk17.05 for the same
application. But newer version of dpdk (dpdk 17.05 ) needs NIC's firmware
upgrade for SR-IOV Nics.
If i upgrade firmware, will it create any trouble for VM
19/07/2017 11:19, Hemant Agrawal:
> load_balancer app can also work for lower number of cores.
> Limit the cores Worker and IO cores to 16 as defined in original
> App. Otherwise use the actual number of lcores as MAX.
>
> Signed-off-by: Hemant Agrawal
> ---
> v2: Revert back the condition check
19/07/2017 11:13, Hemant Agrawal:
> APP_MAX_LCORES is hardcoded as 64.
> This will cause build err when RTE_MAX_LCORE is less then 64.
>
> "args.c:127:22: error: iteration 8 invokes undefined behavior
> [-Werror=aggressive-loop-optimizations]
>if (cfg->lcore_role[i] == ROLE_RTE)
>
Some phy's take longer than others to come up. Add a retry to give
more phy's a chance to come up before returning an error.
Signed-off-by: David Hunt
---
drivers/net/i40e/i40e_ethdev.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/drivers/net/i40e/i40e_ethdev.
The title and the text below should explain that you move
the warning log from scan to probe, thanks to a temporary
negative value.
21/07/2017 12:11, Sergio Gonzalez Monroy:
> Commit 8a04cb612589 ("pci: set default numa node for broken systems")
> added logic to default to NUMA node 0 when sysfs n
On Wed, Jul 12, 2017 at 06:23:38PM +0200, Thomas Monjalon wrote:
> 12/07/2017 17:57, Morten Brørup:
> > From: Stephen Hemminger
> > > Morten Brørup wrote:
> > > > From: Yang, Zhiyong [mailto:zhiyong.y...@intel.com]
> > > > > From: Morten Brørup
> > > > > > From: Wiles, Keith
> > > > > > > > On Jul
On 21/07/2017 15:53, Thomas Monjalon wrote:
The title and the text below should explain that you move
the warning log from scan to probe, thanks to a temporary
negative value.
I thought that saying that I only check for devices managed by dpdk
explains the purpose,
and the patch itself shows
11/07/2017 09:18, Jiayu Hu:
> This patch updates GRO API comments to generate correct
> API documentation by doxygen.
>
> Signed-off-by: Jiayu Hu
Applied with the small fix below, thanks
For rte_gro_timeout_flush:
- * @param nb_out
+ * @param max_nb_out
11/07/2017 06:27, Jiayu Hu:
> Add description to programmer's guide to explain the
> design of the GRO library.
>
> Signed-off-by: Jiayu Hu
> ---
> MAINTAINERS| 1 +
> .../prog_guide/generic_receive_offload_lib.rst | 163
> +
> d
On Thu, Jul 20, 2017 at 07:34:04PM +0300, Sagi Grimberg wrote:
>
> > mlx5_tx_complete() polls completion queue multiple times until it
> > encounters an invalid entry. As Tx completions are suppressed by
> > MLX5_TX_COMP_THRESH, it is waste of cycles to expect multiple completions
> > in a poll. A
21/07/2017 18:03, Sergio Gonzalez Monroy:
> On 21/07/2017 15:53, Thomas Monjalon wrote:
> > The title and the text below should explain that you move
> > the warning log from scan to probe, thanks to a temporary
> > negative value.
>
> I thought that saying that I only check for devices managed by
On 21/07/2017 16:37, Thomas Monjalon wrote:
21/07/2017 18:03, Sergio Gonzalez Monroy:
On 21/07/2017 15:53, Thomas Monjalon wrote:
The title and the text below should explain that you move
the warning log from scan to probe, thanks to a temporary
negative value.
I thought that saying that I onl
On Tue, Jul 04, 2017 at 02:42:24PM +0200, Thomas Monjalon wrote:
> > > Bruce Richardson (18):
> > > mk: require SSE4.2 support on all x86 platforms
> > > acl: remove checks for SSE4
> > > distributor: remove checks for SSE4
> > > eal: remove unneeded conditionals for SSE headers
> > > has
12/07/2017 12:25, Bernard Iremonger:
> The _rte_eth_dev_callback_process function has been modified.
> The return value has been changed form void to int and an
> extra parameter "void *ret_param" has been added.
>
> Signed-off-by: Bernard Iremonger
Applied, thanks
21/07/2017 18:47, Sergio Gonzalez Monroy:
> On 21/07/2017 16:37, Thomas Monjalon wrote:
> > 21/07/2017 18:03, Sergio Gonzalez Monroy:
> >> On 21/07/2017 15:53, Thomas Monjalon wrote:
> >>> The title and the text below should explain that you move
> >>> the warning log from scan to probe, thanks to
21/07/2017 12:11, Sergio Gonzalez Monroy:
> Commit 8a04cb612589 ("pci: set default numa node for broken systems")
> added logic to default to NUMA node 0 when sysfs numa_node information
> was wrong or not available.
>
> Unfortunately there are many devices with wrong NUMA node information
> that
14/07/2017 17:45, Thomas Monjalon:
> The file rte_flow_driver.h is a driver interface,
> thus it should not be listed in the API index.
>
> Signed-off-by: Thomas Monjalon
Applied
So the only change was replacing a nesting level with a continue? Yeah,
looks good.
On Thu, Jul 20, 2017 at 8:22 PM, Ajit Khaparde
wrote:
> Fix use of local variable to avoid segfault.
> cnt was incorrectly tested and decremented in the loop that removes
> a VLAN from the table.
>
> Fixes: 3673
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v17.08-rc2
What's new in RC2?
- service cores API
- traffic management API (QoS)
- lock-free Tx queue capability API
- failsafe driver
The release notes have been updated
33 matches
Mail list logo
