[dpdk-dev] [PATCH v2] i40e: Fix eth_i40e_dev_init sequence on ThunderX

On Tue, Nov 22, 2016 at 01:46:54PM +, Bruce Richardson wrote: > On Tue, Nov 22, 2016 at 03:46:38AM +0530, Jerin Jacob wrote: > > On Sun, Nov 20, 2016 at 11:21:43PM +, Ananyev, Konstantin wrote: > > > Hi > > > > > > > > i40e_asq_send_command: rd32 & wr32 under ThunderX gives unpredictable

[dpdk-dev] [PATCH 2/4] eventdev: implement the northbound APIs

On Tue, Nov 22, 2016 at 07:43:03PM +, Eads, Gage wrote: > > > > > > One open issue I noticed is the "typical workflow" description > > starting in > > > > rte_eventdev.h:204 conflicts with the centralized software PMD that > > Harry > > > > posted last week. Specifically, that PMD

[dpdk-dev] [PATCH 2/4] eventdev: implement the northbound APIs

On Tue, Nov 22, 2016 at 10:48:32PM +, Eads, Gage wrote: > > > > -Original Message- > > From: Jerin Jacob [mailto:jerin.jacob at caviumnetworks.com] > > Sent: Tuesday, November 22, 2016 2:00 PM > > To: Eads, Gage > > Cc: dev at dpdk.org; Richardson, Bruce ; Van > > Haaren,

[dpdk-dev] [PATCH 00/56] Solarflare libefx-based PMD

On 11/21/2016 3:00 PM, Andrew Rybchenko wrote: > The patch series adds Solarflare libefx-based network PMD. > > This version of the driver supports Solarflare SFN7xxx and SFN8xxx > families of 10/40 Gbps adapters. > > libefx is a platform-independent library to implement drivers for > Solarflare

[dpdk-dev] [PATCH] eal: postpone vdev initialization

On Mon, Nov 21, 2016 at 05:35:58PM +, Ferruh Yigit wrote: > On 11/21/2016 5:02 PM, Jerin Jacob wrote: > > On Mon, Nov 21, 2016 at 09:54:57AM +, Ferruh Yigit wrote: > >> On 11/20/2016 8:00 AM, Jerin Jacob wrote: > >>> Some platform like octeontx may use pci and > >>> vdev based combined

[dpdk-dev] [PATCH 00/56] Solarflare libefx-based PMD

On 11/23/2016 12:02 AM, Ferruh Yigit wrote: > On 11/21/2016 3:00 PM, Andrew Rybchenko wrote: >> The patch series adds Solarflare libefx-based network PMD. >> >> This version of the driver supports Solarflare SFN7xxx and SFN8xxx >> families of 10/40 Gbps adapters. >> >> libefx is a

[dpdk-dev] [PATCH v2] examples/ethtool: fix bug in drvinfo callback

Not sure this is a problem in practice, as the same set if fields is updated each time...at least for now. On 22/11/2016 09:41, Qiming Yang wrote: > Function pcmd_drvinfo_callback uses struct info to get > the ethtool information of each port. Struct info will > store the information of previous

[dpdk-dev] [PATCH 5/7] test/eventdev: unit and functional tests

On Wed, Nov 16, 2016 at 06:00:05PM +, Harry van Haaren wrote: > This commit adds basic unit and functional tests for the eventdev > API. The test code is added in this commit, but not yet enabled until > the next commit. > > Signed-off-by: Gage Eads > Signed-off-by: David Hunt >

[dpdk-dev] [PATCH 00/56] Solarflare libefx-based PMD

On 11/23/2016 03:02 AM, Ferruh Yigit wrote: > On 11/21/2016 3:00 PM, Andrew Rybchenko wrote: >> The patch series adds Solarflare libefx-based network PMD. >> >> This version of the driver supports Solarflare SFN7xxx and SFN8xxx >> families of 10/40 Gbps adapters. >> >> libefx is a

[dpdk-dev] Proposal for a new Committer model

> -Original Message- > From: Neil Horman [mailto:nhorman at tuxdriver.com] > Sent: Tuesday, November 22, 2016 7:52 PM > To: Thomas Monjalon > Cc: dev at dpdk.org; Mcnamara, John > Subject: Re: [dpdk-dev] Proposal for a new Committer model > > On Mon, Nov 21, 2016 at 09:52:41AM +0100,

[dpdk-dev] [RFC PATCH 0/6] Restructure EAL device model for bus support

I should have replied to this earlier, apologies. On Sunday 20 November 2016 09:00 PM, David Marchand wrote: > On Thu, Nov 17, 2016 at 6:29 AM, Shreyansh Jain > wrote: >> DPDK has been inherently a PCI inclined framework. Because of this, the >> design of device tree (or list) within DPDK is

[dpdk-dev] [PATCH 00/56] Solarflare libefx-based PMD

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Andrew Rybchenko > Sent: Wednesday, November 23, 2016 7:50 AM > To: Yigit, Ferruh ; dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH 00/56] Solarflare libefx-based PMD > > On 11/23/2016 03:02 AM, Ferruh Yigit

[dpdk-dev] [PATCH 2/4] eventdev: implement the northbound APIs

Hi Gage, just FYI, you can make it easier on your readers if you cut off the end of the original email that you are not replying to. It saves us having to scroll down to check for more comments. :-) /Bruce On Tue, Nov 22, 2016 at 03:15:52PM +, Eads, Gage wrote: > > > > -Original

[dpdk-dev] [PATCH] app/testpmd: display port driver name

This makes it easier to check which driver name is reported through ethdev rte_eth_dev_info_get(). Example: root at ubuntu1604:~/dpdk# ./build/app/testpmd -c 0x6 --vdev net_af_packet0,iface=mgmt0 -- -i --total-num-mbufs 2049 [snip] testpmd> show port info all * Infos for

[dpdk-dev] [PATCH] app/testpmd: display port driver name

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of David Marchand > Sent: Wednesday, November 23, 2016 10:55 AM > To: De Lara Guarch, Pablo > Cc: dev at dpdk.org > Subject: [dpdk-dev] [PATCH] app/testpmd: display port driver name > > This makes it easier to

[dpdk-dev] [PATCH] maintainers: update testpmd maintainers

add Jingjing Wu and Wei Dai as new maintainers of test-pmd. Signed-off-by: Wei Dai --- MAINTAINERS | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index d6bb8f8..8070ed6 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -614,7 +614,8 @@ F:

[dpdk-dev] [PATCH] examples: fix ip_pipeline makefile typo

Signed-off-by: Ilya V. Matveychikov --- examples/ip_pipeline/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/ip_pipeline/Makefile b/examples/ip_pipeline/Makefile index 5827117..6657237 100644 --- a/examples/ip_pipeline/Makefile +++

[dpdk-dev] [PATCH] maintainers: update testpmd maintainers

> -Original Message- > From: Dai, Wei > Sent: Wednesday, November 23, 2016 8:35 PM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo; Wu, Jingjing; Mcnamara, John; Zhang, Helin; Dai, > Wei > Subject: [PATCH] maintainers: update testpmd maintainers > > add Jingjing Wu and Wei Dai as new

[dpdk-dev] [PATCH] maintainers: update testpmd maintainers

2016-11-23 20:34, Wei Dai: > add Jingjing Wu and Wei Dai as new maintainers > of test-pmd. Thanks for proposing yourself. I think it is a bit strange for you Wei Dai to become maintainer now, as you are a newcomer and never sent a patch for testpmd yet.

[dpdk-dev] [PATCH] eal: postpone vdev initialization

2016-11-23 05:37, Jerin Jacob: > On Mon, Nov 21, 2016 at 05:35:58PM +, Ferruh Yigit wrote: > > On 11/21/2016 5:02 PM, Jerin Jacob wrote: > > > On Mon, Nov 21, 2016 at 09:54:57AM +, Ferruh Yigit wrote: > > >> This changes the port id assignments to the devices, right? > > >> > > >>

[dpdk-dev] [PATCH 00/56] Solarflare libefx-based PMD

2016-11-23 09:57, Mcnamara, John: > From: Andrew Rybchenko > > Yes, I have no ICC compilers. I'll try to fix these warnings, but I can't > > be sure without checking it. > > Also we cannot claim ICC supported without building and testing the > > generated binary. > > Hi, > > You can get a copy

[dpdk-dev] Proposal for a new Committer model

On Tue, Nov 22, 2016 at 08:56:23PM +, Ferruh Yigit wrote: > On 11/22/2016 7:52 PM, Neil Horman wrote: > > On Mon, Nov 21, 2016 at 09:52:41AM +0100, Thomas Monjalon wrote: > >> 2016-11-18 13:09, Neil Horman: > >>> A) Further promote subtree maintainership. This was a conversation that I > >>>

[dpdk-dev] Proposal for a new Committer model

On 11/23/2016 1:48 PM, Neil Horman wrote: > On Tue, Nov 22, 2016 at 08:56:23PM +, Ferruh Yigit wrote: >> On 11/22/2016 7:52 PM, Neil Horman wrote: >>> On Mon, Nov 21, 2016 at 09:52:41AM +0100, Thomas Monjalon wrote: 2016-11-18 13:09, Neil Horman: > A) Further promote subtree

[dpdk-dev] Proposal for a new Committer model

On Wed, Nov 23, 2016 at 08:21:39AM +, Mcnamara, John wrote: > > > > -Original Message- > > From: Neil Horman [mailto:nhorman at tuxdriver.com] > > Sent: Tuesday, November 22, 2016 7:52 PM > > To: Thomas Monjalon > > Cc: dev at dpdk.org; Mcnamara, John > > Subject: Re: [dpdk-dev]

[dpdk-dev] [PATCH 01/56] net/sfc: libefx-based PMD stub sufficient to build and init

On 11/21/2016 3:00 PM, Andrew Rybchenko wrote: > The PMD is put into the sfc/efx subdirectory to have a place for > the second PMD and library shared by both. > > Enable the PMD by default on supported configuratons. > > Reviewed-by: Andy Moreton > Signed-off-by: Andrew Rybchenko > --- >

[dpdk-dev] [PATCH 30/56] net/sfc: include libefx in build

On 11/21/2016 3:00 PM, Andrew Rybchenko wrote: > From: Artem Andreev > > Implement efsys.h for the PMD. > > Reviewed-by: Andy Moreton > Signed-off-by: Artem Andreev > Signed-off-by: Andrew Rybchenko > --- > drivers/net/sfc/efx/Makefile | 54 +++ > drivers/net/sfc/efx/efsys.h | 767 >

[dpdk-dev] [PATCH 31/56] net/sfc: implement dummy callback to get device information

On 11/21/2016 3:00 PM, Andrew Rybchenko wrote: > Just a stub to be filled in when corresponding functionality is > implemented. What about merging this stub with real implementation? Or perhaps replace with code that adds dummy .dev_configure? > > Reviewed-by: Andy Moreton > Signed-off-by:

[dpdk-dev] [PATCH 32/56] net/sfc: implement driver operation to init device on attach

On 11/21/2016 3:00 PM, Andrew Rybchenko wrote: > The setup and configuration of the PMD is not performance sensitive, > but is not thread safe either. It is possible that the multiple > read/writes during PMD setup and configuration could be corrupted > in a multi-thread environment. Right,

[dpdk-dev] [PATCH 33/56] net/sfc: add device configure and close stubs

On 11/21/2016 3:00 PM, Andrew Rybchenko wrote: > Reviewed-by: Andy Moreton > Signed-off-by: Andrew Rybchenko > --- <...> > diff --git a/drivers/net/sfc/efx/sfc.h b/drivers/net/sfc/efx/sfc.h > index 01d652d..d040f98 100644 > --- a/drivers/net/sfc/efx/sfc.h > +++ b/drivers/net/sfc/efx/sfc.h

[dpdk-dev] [PATCH 00/56] Solarflare libefx-based PMD

On 11/21/2016 3:00 PM, Andrew Rybchenko wrote: > The patch series adds Solarflare libefx-based network PMD. > > This version of the driver supports Solarflare SFN7xxx and SFN8xxx > families of 10/40 Gbps adapters. > > libefx is a platform-independent library to implement drivers for > Solarflare

[dpdk-dev] Proposal for a new Committer model

On Wed, Nov 23, 2016 at 02:01:44PM +, Ferruh Yigit wrote: > On 11/23/2016 1:48 PM, Neil Horman wrote: > > On Tue, Nov 22, 2016 at 08:56:23PM +, Ferruh Yigit wrote: > >> On 11/22/2016 7:52 PM, Neil Horman wrote: > >>> On Mon, Nov 21, 2016 at 09:52:41AM +0100, Thomas Monjalon wrote: >

[dpdk-dev] [PATCH v2] log: do not drop debug logs at compile time

Today, all logs whose level is lower than INFO are dropped at compile-time. This prevents from enabling debug logs at runtime using --log-level=8. The rationale was to remove debug logs from the data path at compile-time, avoiding a test at run-time. This patch changes the behavior of RTE_LOG()

[dpdk-dev] Proposal for a new Committer model

On Wed, Nov 23, 2016 at 09:11:54AM -0500, Neil Horman wrote: > > Could we define some of the potential subtrees now and look to introduce > > them in the this release cycle? EAL and the Core libs, as suggested by > > Thomas, seem like 2 obvious ones. > > > Sure, I'd suggest the following: I

[dpdk-dev] [PATCH] examples: fix ip_pipeline makefile typo

On 11/23/2016 12:56 PM, Ilya Matveychikov wrote: > Signed-off-by: Ilya V. Matveychikov > --- > examples/ip_pipeline/Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/examples/ip_pipeline/Makefile b/examples/ip_pipeline/Makefile > index 5827117..6657237 100644 >

[dpdk-dev] Proposal for a new Committer model

On 11/23/2016 3:33 PM, Neil Horman wrote: > On Wed, Nov 23, 2016 at 02:01:44PM +, Ferruh Yigit wrote: >> On 11/23/2016 1:48 PM, Neil Horman wrote: >>> On Tue, Nov 22, 2016 at 08:56:23PM +, Ferruh Yigit wrote: On 11/22/2016 7:52 PM, Neil Horman wrote: > On Mon, Nov 21, 2016 at

[dpdk-dev] KNI discussion in userspace event

Hi Stephen, Ferruh, As an end-user take on this (hence community comment) :), this ties into the rte_eth_tap that Keith sent out and it has been acked and reviewed, So I am trying to see the pros/cons of using this (kni pmd) vs. the tun/tap PMD [1]. Previously, we were using Ferruh's KDP/KCP

[dpdk-dev] [PATCH v12 0/6] add Tx preparation

As discussed in that thread: http://dpdk.org/ml/archives/dev/2015-September/023603.html Different NIC models depending on HW offload requested might impose different requirements on packets to be TX-ed in terms of: - Max number of fragments per packet allowed - Max number of fragments per TSO

[dpdk-dev] [PATCH v12 1/6] ethdev: add Tx preparation

Added API for `rte_eth_tx_prepare` uint16_t rte_eth_tx_prepare(uint8_t port_id, uint16_t queue_id, struct rte_mbuf **tx_pkts, uint16_t nb_pkts) Added fields to the `struct rte_eth_desc_lim`: uint16_t nb_seg_max; /**< Max number of segments per whole packet. */

[dpdk-dev] [PATCH v12 2/6] e1000: add Tx preparation

Signed-off-by: Tomasz Kulasek Acked-by: Konstantin Ananyev --- drivers/net/e1000/e1000_ethdev.h | 11 drivers/net/e1000/em_ethdev.c|5 +++- drivers/net/e1000/em_rxtx.c | 48 ++- drivers/net/e1000/igb_ethdev.c |4 +++

[dpdk-dev] [PATCH v12 3/6] fm10k: add Tx preparation

Signed-off-by: Tomasz Kulasek Acked-by: Konstantin Ananyev --- drivers/net/fm10k/fm10k.h|6 + drivers/net/fm10k/fm10k_ethdev.c |5 drivers/net/fm10k/fm10k_rxtx.c | 50 +- 3 files changed, 60 insertions(+), 1 deletion(-) diff

[dpdk-dev] [PATCH v12 4/6] i40e: add Tx preparation

Signed-off-by: Tomasz Kulasek Acked-by: Konstantin Ananyev --- drivers/net/i40e/i40e_ethdev.c |3 ++ drivers/net/i40e/i40e_rxtx.c | 72 +++- drivers/net/i40e/i40e_rxtx.h |8 + 3 files changed, 82 insertions(+), 1 deletion(-) diff --git

[dpdk-dev] [PATCH v12 5/6] ixgbe: add Tx preparation

Signed-off-by: Tomasz Kulasek Acked-by: Konstantin Ananyev --- drivers/net/ixgbe/ixgbe_ethdev.c |3 ++ drivers/net/ixgbe/ixgbe_ethdev.h |5 +++- drivers/net/ixgbe/ixgbe_rxtx.c | 56 ++ drivers/net/ixgbe/ixgbe_rxtx.h |2 ++ 4 files changed,

[dpdk-dev] [PATCH v12 6/6] testpmd: use Tx preparation in csum engine

Added "csum txprep (on|off)" command which allows to switch to the tx path using Tx preparation API. By default unchanged implementation is used. Using Tx preparation path, pseudo header calculation for udp/tcp/tso packets from application, and used Tx preparation API for packet preparation and

[dpdk-dev] [PATCH 1/4] eventdev: introduce event driven programming model

Hi Jerin, Thanks for bringing a big new piece in DPDK. I made some comments below. 2016-11-18 11:14, Jerin Jacob: > +Eventdev API - EXPERIMENTAL > +M: Jerin Jacob > +F: lib/librte_eventdev/ OK to mark it experimental. What is the plan to remove the experimental word? > + * RTE event device

[dpdk-dev] [PATCH 2/4] eventdev: implement the northbound APIs

2016-11-18 11:15, Jerin Jacob: > This patch set defines the southbound driver interface > and implements the common code required for northbound > eventdev API interface. Please make two separate patches. > +#ifdef RTE_LIBRTE_EVENTDEV_DEBUG > +#define RTE_PMD_DEBUG_TRACE(...) \ > +

[dpdk-dev] [PATCH 00/56] Solarflare libefx-based PMD

On Wed, 23 Nov 2016 10:49:33 +0300 Andrew Rybchenko wrote: > I've tried to explain it above in item (2): > > >>> > > 2. Another Solarflare PMD with in-kernel part (for control operations) > is considered and could be added in the future. Code for data path > should be shared by

[dpdk-dev] Improved PCI hotplug support

This series of patches adds support for PCI hot insert and remove. Detection of new devices or removed devices is accomplished by polling rte_eal_pci_probe, with the registered PCI drivers being loaded or unloaded when a new device is found or previously known device is removed. There are some

[dpdk-dev] [PATCH 3/7] pci: Pass rte_pci_addr to functions instead of separate args

Instead of passing domain, bus, devid, func, just pass an rte_pci_addr. Signed-off-by: Ben Walker --- lib/librte_eal/linuxapp/eal/eal_pci.c | 32 +--- 1 file changed, 13 insertions(+), 19 deletions(-) diff --git a/lib/librte_eal/linuxapp/eal/eal_pci.c

[dpdk-dev] [PATCH 2/7] pci: Separate detaching ethernet ports from PCI devices

Attaching and detaching ethernet ports from an application is not the same thing as physically removing a PCI device, so clarify the flags indicating support. All PCI devices are assumed to be physically removable, so no flag is necessary in the PCI layer. Signed-off-by: Ben Walker ---

[dpdk-dev] [PATCH 4/7] pci: rte_eal_pci_scan now handles removal of PCI devices

rte_eal_pci_scan can be called repeatedly to re-scan the PCI bus. If a device was removed from the system, the associated driver will automatically be unloaded. Signed-off-by: Ben Walker --- lib/librte_eal/linuxapp/eal/eal_pci.c | 58 +++ 1 file changed, 58

[dpdk-dev] [PATCH 5/7] pci: Move driver registration above pci scan

The user needs to register drivers before scanning, so it makes the most sense to put the registration functions above the scan function in the header file. Signed-off-by: Ben Walker --- lib/librte_eal/common/include/rte_pci.h | 56 - 1 file changed, 28

[dpdk-dev] [PATCH 6/7] pci: Combine rte_eal_pci_scan and rte_eal_pci_probe

Two functions is both confusing and unnecessary. Previously, rte_eal_pci_scan populated an internal list of devices by scanning sysfs. Then, rte_eal_pci_probe would match registered drivers to that internal list. These are not really useful operations to perform separately independently, though,

[dpdk-dev] [PATCH 7/7] pci: Clarify interfaces for dynamic attach/detach of drivers

There are now two functions - rte_eal_pci_attach_driver and rte_eal_pci_detach_driver - that dynamically attempt to attach and detach drivers from PCI devices. These only control whether a registered PCI driver is loaded or not - they are independent of whether the PCI device exists on the system.

[dpdk-dev] [PATCH 1/4] ethdev: Call rx/tx_queue_release before rx/tx_queue_setup

If a queue has been setup before lets release it before we setup. Otherwise we might leak resources. Signed-off-by: Jan Blunck --- lib/librte_ether/rte_ethdev.c | 18 ++ 1 file changed, 18 insertions(+) diff --git a/lib/librte_ether/rte_ethdev.c b/lib/librte_ether/rte_ethdev.c

[dpdk-dev] [PATCH 2/4] ethdev: Free rx/tx_queues after releasing all queues

If all queues are released lets also free up the dev->data->rx/tx_queues to be able to properly reinitialize. Signed-off-by: Jan Blunck --- lib/librte_ether/rte_ethdev.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/lib/librte_ether/rte_ethdev.c b/lib/librte_ether/rte_ethdev.c index

[dpdk-dev] [PATCH 3/4] ethdev: Add DPDK internal _rte_eth_dev_reset()

This is a helper for DPDK internal users to force a reconfiguration of a device. Signed-off-by: Jan Blunck --- lib/librte_ether/rte_ethdev.c | 15 +++ lib/librte_ether/rte_ethdev.h | 13 + lib/librte_ether/rte_ether_version.map | 6 ++ 3 files

[dpdk-dev] [PATCH 4/4] bond: Force reconfiguration of removed slave interfaces

After a slave interface is removed from a bond group it still has the configuration of the bond interface. Lets enforce that the slave interface is reconfigured after removal by resetting it. Signed-off-by: Jan Blunck --- drivers/net/bonding/rte_eth_bond_pmd.c | 3 +++ 1 file changed, 3

[dpdk-dev] [PATCH v2 1/7] pci: If a driver's probe function fails, unmap resources.

If resources were mapped prior to probe, unmap them if probe fails. This does not handle the case where the kernel driver was forcibly unbound prior to probe. Signed-off-by: Ben Walker --- lib/librte_eal/common/eal_common_pci.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff

[dpdk-dev] [PATCH v2 3/7] pci: Pass rte_pci_addr to functions instead of separate args

Instead of passing domain, bus, devid, func, just pass an rte_pci_addr. Signed-off-by: Ben Walker --- lib/librte_eal/linuxapp/eal/eal_pci.c | 32 +--- 1 file changed, 13 insertions(+), 19 deletions(-) diff --git a/lib/librte_eal/linuxapp/eal/eal_pci.c

[dpdk-dev] [PATCH v2 2/7] pci: Separate detaching ethernet ports from PCI devices

Attaching and detaching ethernet ports from an application is not the same thing as physically removing a PCI device, so clarify the flags indicating support. All PCI devices are assumed to be physically removable, so no flag is necessary in the PCI layer. Signed-off-by: Ben Walker ---

[dpdk-dev] [PATCH v2 4/7] pci: rte_eal_pci_scan now handles removal of PCI devices

rte_eal_pci_scan can be called repeatedly to re-scan the PCI bus. If a device was removed from the system, the associated driver will automatically be unloaded. Signed-off-by: Ben Walker --- lib/librte_eal/linuxapp/eal/eal_pci.c | 62 +++ 1 file changed, 62

[dpdk-dev] [PATCH v2 5/7] pci: Move driver registration above pci scan

The user needs to register drivers before scanning, so it makes the most sense to put the registration functions above the scan function in the header file. Signed-off-by: Ben Walker --- lib/librte_eal/common/include/rte_pci.h | 56 - 1 file changed, 28

[dpdk-dev] [PATCH v2 6/7] pci: Combine rte_eal_pci_scan and rte_eal_pci_probe

Two functions is both confusing and unnecessary. Previously, rte_eal_pci_scan populated an internal list of devices by scanning sysfs. Then, rte_eal_pci_probe would match registered drivers to that internal list. These are not really useful operations to perform separately, though, so simplify the

[dpdk-dev] [PATCH 05/16] e1000/base: expose e1000_write_vfta_i350

Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/base/e1000_82575.c | 1 - drivers/net/e1000/base/e1000_82575.h | 1 + 2 files changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/net/e1000/base/e1000_82575.c b/drivers/net/e1000/base/e1000_82575.c index 723885d..c6400bd 100644 ---

[dpdk-dev] [PATCH 06/16] e1000/base: add max RX jumbo frame define

Add a define for MAX_RX_JUMBO_FRAME_SIZE to be used by igb as all igb parts (82575 and newer) have 9.5K max jumbo frame as per the datasheet. Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/base/e1000_defines.h | 2 ++ 1 file changed, 2 insertions(+) diff --git

[dpdk-dev] [PATCH 07/16] e1000/base: restore link speed after ULP exit

After cable reconnect with Ultra Low Power (ULP) enabled, the Client PHY needs to be set up for link configuration. Previously this was only done in auto-negotiate mode. This fixes that and calls e1000_setup_copper_link_generic if autoneg is disabled. Signed-off-by: Wenzhuo Lu ---

[dpdk-dev] [PATCH 08/16] e1000/base: clear ULP configuration register on ULP exit

There are some Client PHY Ultra Low Power (ULP) register bits that are configured by the Manageability Engine (ME) FW. The driver must ensure that these bits are cleared on exit from ULP. Ordinarily the ME FW would do that, but there are cases in which the FW is not present, and the driver must

[dpdk-dev] [PATCH 09/16] e1000/base: increase LANPHYPC low duration

LANPHYPC low duration of 10 usec was too low for some corner cases causing interface mismatches during Ultra Low Power (ULP) exit. This patch increases the duration to 1 msec which should be enough. Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/base/e1000_ich8lan.c | 2 +- 1 file changed, 1

[dpdk-dev] [PATCH 10/16] e1000/base: workaround for ULP entry flow

For i217 revision 6, when entering Ultra Low Power (ULP) we need to enable Low Power Link Up (LPLU) and disable Gig speed to make it work. Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/base/e1000_ich8lan.c | 30 ++ 1 file changed, 30 insertions(+) diff --git

[dpdk-dev] [PATCH 11/16] e1000/base: enable new i219 devices

Enable the support of new i219 devices. Also define some registers for future usage. Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/base/e1000_api.c | 12 + drivers/net/e1000/base/e1000_defines.h | 7 + drivers/net/e1000/base/e1000_hw.h | 15 +-

[dpdk-dev] [PATCH 12/16] e1000/base: always request clock during K1 at 1G link speed

This works around a possible stalled packet issue, which may occur due to clock recovery from the PCH being too slow, when the LAN is transitioning from K1 at 1G link speed. Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/base/e1000_ich8lan.c | 10 ++

[dpdk-dev] [PATCH 13/16] e1000/base: ability to force K1-off disabled

MAC-PHY desync may occur causing misdetection of link up event. Disabling K1-off feature can work around the problem. Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/base/e1000_hw.h | 1 + drivers/net/e1000/base/e1000_ich8lan.c | 3 +++ 2 files changed, 4 insertions(+) diff --git

[dpdk-dev] [PATCH 14/16] e1000/base: support more i219 devices

Add the support of more new i219 devices. Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/base/e1000_api.c | 7 +++ drivers/net/e1000/base/e1000_hw.h | 5 + drivers/net/e1000/base/e1000_ich8lan.c | 7 +++ 3 files changed, 19 insertions(+) diff --git

[dpdk-dev] [PATCH 15/16] e1000/base: update readme

Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/base/README | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/e1000/base/README b/drivers/net/e1000/base/README index 8d48135..6cdd9b3 100644 --- a/drivers/net/e1000/base/README +++ b/drivers/net/e1000/base/README

[dpdk-dev] [PATCH 16/16] e1000: add new i219 devices

Enable the new i219 devices. Signed-off-by: Wenzhuo Lu --- drivers/net/e1000/em_ethdev.c | 34 +- 1 file changed, 33 insertions(+), 1 deletion(-) diff --git a/drivers/net/e1000/em_ethdev.c b/drivers/net/e1000/em_ethdev.c index aee3d34..6a4cf2b 100644 ---

[dpdk-dev] [PATCH 1/1] net/i40e: enable auto link update for XXV710

From: root This patch remove the limitation that XXV710 device does not support auto link update. Signed-off-by: root --- drivers/net/i40e/i40e_ethdev.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/net/i40e/i40e_ethdev.c