[dpdk-dev] [PATCH v7 03/21] eal/linux: generalize PCI kernel unbinding driver to EAL

On 28 October 2016 at 20:26, Shreyansh Jain wrote: > From: Jan Viktorin > > Generalize the PCI-specific pci_unbind_kernel_driver. It is now divided > into two parts. First, determination of the path and string identification > of the device to be unbound. Second, the actual unbind operation

[dpdk-dev] [PATCH v3] net/qede: fix advertising link speed capability

> >2016-10-31 11:35, Rasesh Mody: >> From: Harish Patil >> >> Fix to advertise device's link speed capability based on NVM >> port configuration instead of returning driver supported speeds. >> >> Fixes: 95e67b479506 ("net/qede: add 100G link speed capability") >> >> Signed-off-by: Harish

[dpdk-dev] [PATCH] app/test: fix crash of lpm test

Hi, Oliver Thanks for your catching this bug. After reviewing related codes, I can acknowledge it. Thanks -Wei > -Original Message- > From: Olivier Matz [mailto:olivier.matz at 6wind.com] > Sent: Wednesday, November 9, 2016 9:08 PM > To: dev at dpdk.org; Dai, Wei > Cc: Richardson, Bruce

[dpdk-dev] [PATCH v7 08/21] eal/soc: implement SoC device list and dump

On 28 October 2016 at 20:26, Shreyansh Jain wrote: > From: Jan Viktorin > > SoC devices would be linked in a separate list (from PCI). This is used for > probe function. > A helper for dumping the device list is added. > > Signed-off-by: Jan Viktorin > Signed-off-by: Shreyansh Jain >

[dpdk-dev] [PATCH v7 11/21] eal/soc: implement probing of drivers

On 28 October 2016 at 20:26, Shreyansh Jain wrote: > Each SoC PMD registers a set of callback for scanning its own bus/infra and > matching devices to drivers when probe is called. > This patch introduces the infra for calls to SoC scan on rte_eal_soc_init() > and match on rte_eal_soc_probe(). >

[dpdk-dev] [PATCH v7 06/21] eal/soc: introduce very essential SoC infra definitions

On 28 October 2016 at 20:26, Shreyansh Jain wrote: > From: Jan Viktorin > > Define initial structures and functions for the SoC infrastructure. > This patch supports only a very minimal functions for now. > More features will be added in the following commits. > > Includes rte_device/rte_driver

[dpdk-dev] [PATCH v7 03/21] eal/linux: generalize PCI kernel unbinding driver to EAL

Hello Jianbo, Thanks a lot for your time in commenting this. My comments inline (as well as on other similar mails). On Thursday 10 November 2016 07:54 AM, Jianbo Liu wrote: > On 28 October 2016 at 20:26, Shreyansh Jain wrote: >> From: Jan Viktorin >> >> Generalize the PCI-specific

[dpdk-dev] [PATCH] examples/l3fwd: force CRC stripping for i40evf

I'm testing some DPDK sample under VMware. During the testing work, I find l3fwd+ ixgbe vf can work ,but L3fwd + i40evf can't work. So I reported this issue to Bjorn. From my perspective, if can add new parameter in l3fwd sample like what have already don?t in testpmd "crc-strip enable"

[dpdk-dev] [PATCH v7 06/21] eal/soc: introduce very essential SoC infra definitions

On Thursday 10 November 2016 09:39 AM, Jianbo Liu wrote: > On 28 October 2016 at 20:26, Shreyansh Jain wrote: >> From: Jan Viktorin >> >> Define initial structures and functions for the SoC infrastructure. >> This patch supports only a very minimal functions for now. >> More features will be

[dpdk-dev] [PATCH v7 08/21] eal/soc: implement SoC device list and dump

On Thursday 10 November 2016 08:36 AM, Jianbo Liu wrote: > On 28 October 2016 at 20:26, Shreyansh Jain wrote: >> From: Jan Viktorin >> >> SoC devices would be linked in a separate list (from PCI). This is used for >> probe function. >> A helper for dumping the device list is added. >> >>

[dpdk-dev] [PATCH v7 11/21] eal/soc: implement probing of drivers

On Thursday 10 November 2016 09:00 AM, Jianbo Liu wrote: > On 28 October 2016 at 20:26, Shreyansh Jain wrote: >> Each SoC PMD registers a set of callback for scanning its own bus/infra and >> matching devices to drivers when probe is called. >> This patch introduces the infra for calls to SoC

[dpdk-dev] [PATCH] examples/l3fwd: force CRC stripping for i40evf

Lei wrote: > I'm testing some DPDK sample under VMware. During the testing work, I > find l3fwd+ ixgbe vf can work ,but L3fwd + i40evf can't work. So I > reported this issue to Bjorn. From my perspective, if can add new > parameter in l3fwd sample like what have already don?t in testpmd >

[dpdk-dev] Clarification for eth_driver changes

Hello David, list, I need some help and clarification regarding some changes I am doing to cleanup the EAL code. There are some changes which should be done for eth_driver/rte_eth_device structures: 1. most obvious, eth_driver should be renamed to rte_eth_driver. 2. eth_driver currently has

[dpdk-dev] [PATCH v7 11/21] eal/soc: implement probing of drivers

On 10 November 2016 at 14:10, Shreyansh Jain wrote: > On Thursday 10 November 2016 09:00 AM, Jianbo Liu wrote: >> >> On 28 October 2016 at 20:26, Shreyansh Jain >> wrote: >>> >>> Each SoC PMD registers a set of callback for scanning its own bus/infra >>> and >>> matching devices to drivers when

[dpdk-dev] Clarification for eth_driver changes

On 10 November 2016 at 15:26, Shreyansh Jain wrote: > Hello David, list, > > I need some help and clarification regarding some changes I am doing to > cleanup the EAL code. > > There are some changes which should be done for eth_driver/rte_eth_device > structures: > > 1. most obvious, eth_driver

[dpdk-dev] [PATCH] net/qede: fix unknown speed errmsg for 25G link

2016-11-09 18:26, Rasesh Mody: > From: Harish Patil > > Fix to use bitmapped values in NVM configuration for speed capability > advertisement. This issue is specific to 25G NIC since it is capable > of 25G and 10G speeds. > > Fixes: 64c239b7f8b7 ("net/qede: fix advertising link speed

[dpdk-dev] [PATCH] examples/l3fwd: force CRC stripping for i40evf

2016-11-10 07:17, Bj?rn T?pel: > As discussed in the thread, it might be better to just change the > default in l3fwd from .hw_strip_crc = 0 to 1. > > I'll be looking into changing igbvf and ixgbevf to match the semantics > of i40evf. Just to make it sure, you mean returning an error in the

[dpdk-dev] [PATCH] examples/l3fwd: force CRC stripping for i40evf

Thomas wrote: > Just to make it sure, you mean returning an error in the driver when > a configuration cannot be applied, right? Yes, as in 1bbcc5d21129 ("i40evf: report error for unsupported CRC stripping config"), where -EINVAL is returned. Bj?rn

[dpdk-dev] Clarification for eth_driver changes

2016-11-10 15:51, Jianbo Liu: > On 10 November 2016 at 15:26, Shreyansh Jain > wrote: > > This is what the current outline of eth_driver is: > > > > ++ > > | eth_driver | > > | +-+| > > | | rte_pci_driver || > > | |

[dpdk-dev] Clarification for eth_driver changes

Hello Shreyansh, On Thu, Nov 10, 2016 at 8:26 AM, Shreyansh Jain wrote: > I need some help and clarification regarding some changes I am doing to > cleanup the EAL code. > > There are some changes which should be done for eth_driver/rte_eth_device > structures: > > 1. most obvious, eth_driver

[dpdk-dev] Clarification for eth_driver changes

On Thursday 10 November 2016 01:21 PM, Jianbo Liu wrote: > On 10 November 2016 at 15:26, Shreyansh Jain > wrote: >> Hello David, list, >> >> I need some help and clarification regarding some changes I am doing to >> cleanup the EAL code. >> >> There are some changes which should be done for

[dpdk-dev] Clarification for eth_driver changes

On Thursday 10 November 2016 01:33 PM, Thomas Monjalon wrote: > 2016-11-10 15:51, Jianbo Liu: >> On 10 November 2016 at 15:26, Shreyansh Jain >> wrote: >>> This is what the current outline of eth_driver is: >>> >>> ++ >>> | eth_driver | >>> |

[dpdk-dev] Clarification for eth_driver changes

2016-11-10 14:12, Shreyansh Jain: > On Thursday 10 November 2016 01:33 PM, Thomas Monjalon wrote: > > 2016-11-10 15:51, Jianbo Liu: > >> On 10 November 2016 at 15:26, Shreyansh Jain > >> wrote: > >>> This is what the current outline of eth_driver is: > >>> > >>> ++ > >>>

[dpdk-dev] [PATCH v7 11/21] eal/soc: implement probing of drivers

On Thursday 10 November 2016 01:11 PM, Jianbo Liu wrote: > On 10 November 2016 at 14:10, Shreyansh Jain > wrote: >> On Thursday 10 November 2016 09:00 AM, Jianbo Liu wrote: >>> >>> On 28 October 2016 at 20:26, Shreyansh Jain >>> wrote: Each SoC PMD registers a set of callback for

[dpdk-dev] Fwd: mbuf changes

I forgot to include dev at dpdk.org in my response. My comment at the end o this email. On Wed, Oct 26, 2016 at 10:28 AM, Alejandro Lucero < alejandro.lucero at netronome.com> wrote: > > > On Tue, Oct 25, 2016 at 2:05 PM, Bruce Richardson < > bruce.richardson at intel.com> wrote: > >> On Tue,

[dpdk-dev] Clarification for eth_driver changes

Hi Thomas, On 10 November 2016 at 16:58, Thomas Monjalon wrote: > 2016-11-10 14:12, Shreyansh Jain: >> On Thursday 10 November 2016 01:33 PM, Thomas Monjalon wrote: >> > 2016-11-10 15:51, Jianbo Liu: >> >> On 10 November 2016 at 15:26, Shreyansh Jain >> >> wrote: >> >>> This is what the

[dpdk-dev] [PATCH v7 11/21] eal/soc: implement probing of drivers

2016-11-10 14:40, Shreyansh Jain: > On Thursday 10 November 2016 01:11 PM, Jianbo Liu wrote: > > On 10 November 2016 at 14:10, Shreyansh Jain > > wrote: > >> On Thursday 10 November 2016 09:00 AM, Jianbo Liu wrote: > >>> I'm still not sure about the purpose of soc_scan, and how to use it. > >> >

[dpdk-dev] [PATCH] doc: postpone ABI changes for Tx prepare

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon > Sent: Wednesday, November 9, 2016 10:31 PM > To: Kulasek, TomaszX > Cc: dev at dpdk.org > Subject: [dpdk-dev] [PATCH] doc: postpone ABI changes for Tx prepare > > The changes for the

[dpdk-dev] [PATCH] doc: postpone ABI changes for Tx prepare

> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, November 9, 2016 23:31 > To: Kulasek, TomaszX > Cc: dev at dpdk.org > Subject: [PATCH] doc: postpone ABI changes for Tx prepare > > The changes for the feature "Tx prepare" should be

[dpdk-dev] [PATCH v1] doc: announce API and ABI change for librte_ether

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Bernard Iremonger > Sent: Tuesday, October 18, 2016 2:38 PM > To: dev at dpdk.org; Mcnamara, John > Cc: Iremonger, Bernard > Subject: [dpdk-dev] [PATCH v1] doc: announce API and ABI change for > librte_ether

[dpdk-dev] [PATCH v1] doc: announce API and ABI change for librte_ether

On 11/4/2016 1:39 PM, Mcnamara, John wrote: > > >> -Original Message- >> From: Iremonger, Bernard >> Sent: Tuesday, October 18, 2016 2:38 PM >> To: dev at dpdk.org; Mcnamara, John >> Cc: Iremonger, Bernard >> Subject: [PATCH v1] doc: announce API and ABI change for librte_ether >> >>

[dpdk-dev] Clarification for eth_driver changes

I also think drv_flags should part of device not PCI. Most of the flags there like link state support are generic. If it isn't changed for this release will probably have to break ABI to fully support VMBUS

[dpdk-dev] Clarification for eth_driver changes

Hello David, On Thursday 10 November 2016 01:46 PM, David Marchand wrote: > Hello Shreyansh, > > On Thu, Nov 10, 2016 at 8:26 AM, Shreyansh Jain > wrote: >> I need some help and clarification regarding some changes I am doing to >> cleanup the EAL code. >> >> There are some changes which should

[dpdk-dev] Clarification for eth_driver changes

Hi Stephen, 2016-11-10 02:51, Stephen Hemminger: > I also think drv_flags should part of device not PCI. Most of the flags > there like link state support are generic. If it isn't changed for this > release will probably have to break ABI to fully support VMBUS When do you plan to send VMBUS

[dpdk-dev] [PATCH] doc: add more tested platforms and nics and OSes

> -Original Message- > From: Pei, Yulong > Sent: Thursday, November 10, 2016 10:03 AM > To: dev at dpdk.org > Cc: Mcnamara, John ; thomas.monjalon at 6wind.com; > Pei, Yulong > Subject: [PATCH] doc: add more tested platforms and nics and OSes > > Add more tested platforms and nics and

[dpdk-dev] [PATCH] doc: announce API and ABI changes for librte_eal

Signed-off-by: Shreyansh Jain --- doc/guides/rel_notes/deprecation.rst | 10 ++ 1 file changed, 10 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index 1a9e1ae..2af2476 100644 --- a/doc/guides/rel_notes/deprecation.rst +++

[dpdk-dev] [PATCH] doc: postpone ABI changes for Tx prepare

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Thomas Monjalon > Sent: Wednesday, November 9, 2016 10:31 PM > To: Kulasek, TomaszX > Cc: dev at dpdk.org > Subject: [dpdk-dev] [PATCH] doc: postpone ABI changes for Tx prepare > > The changes for the

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

i40e_asq_send_command: rd32 & wr32 under ThunderX gives unpredictable results. To solve this include rte memory barriers Signed-off-by: Satha Rao --- drivers/net/i40e/base/i40e_adminq.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

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

On Thu, Nov 10, 2016 at 04:04:27AM -0800, Satha Rao wrote: > i40e_asq_send_command: rd32 & wr32 under ThunderX gives unpredictable >results. To solve this include rte memory barriers > > Signed-off-by: Satha Rao > --- > drivers/net/i40e/base/i40e_adminq.c | 5 - > 1

[dpdk-dev] [PATCH] maintainers: add staging tree for network drivers

Signed-off-by: Ferruh Yigit --- CC: Bruce Richardson CC: Thomas Monjalon --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 065397b..d6bb8f8 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -252,6 +252,8 @@ F: examples/l2fwd-crypto/ Networking

[dpdk-dev] disable hugepages

I tried using the following dpdk options: --no-huge --vdev eth_pcap0 ,rx_pcap=/t1,tx_pcap=/t2 *It's worked but the number of elements is limited, although the machine has enough free memory. *rte_mempool_create is failed when I'm trying to allocate more memory. Is there any limitation on the

[dpdk-dev] disable hugepages

> On Nov 10, 2016, at 6:32 AM, Keren Hochman > wrote: > > I tried using the following dpdk options: > --no-huge --vdev eth_pcap0 ,rx_pcap=/t1,tx_pcap=/t2 > *It's worked but the number of elements is limited, although the machine > has enough free memory. *rte_mempool_create is failed when I'm

[dpdk-dev] disable hugepages

On 11/10/2016 02:10 PM, Wiles, Keith wrote: > >> On Nov 10, 2016, at 6:32 AM, Keren Hochman >> wrote: >> >> I tried using the following dpdk options: >> --no-huge --vdev eth_pcap0 ,rx_pcap=/t1,tx_pcap=/t2 >> *It's worked but the number of elements is limited, although the machine >> has

[dpdk-dev] [PATCH] examples/l3fwd: force CRC stripping for i40evf

Hi, Re: >Subject: Re: [dpdk-dev] [PATCH] examples/l3fwd: force CRC stripping > for i40evf >Message-ID: >Thomas wrote: > > Just to make it sure, you mean returning an error in the driver when > > a configuration cannot be applied, right? > >Yes, as in

[dpdk-dev] [PATCH] maintainers: add staging tree for network drivers

> Networking Drivers > -- > +M: Ferruh Yigit > +T: git://dpdk.org/next/dpdk-next-net Acked-by: Thomas Monjalon It will be applied at the beginning of 17.02 cycle to reflect the change.

[dpdk-dev] [PATCH 1/2] net: remove dead driver names

Since b1fb53a39d88 ("ethdev: remove some PCI specific handling"), rte_eth_dev_info_get() relies on dev->data->drv_name to report the driver name to caller. Having the pmds set driver_info->driver_name in the pmds is useless, since ethdev overwrites it right after. The only thing the pmd must do

[dpdk-dev] [PATCH 2/2] net: align ethdev and eal driver names

Some virtual pmds report a different name than the vdev driver name registered in eal. While it does not hurt, let's try to be consistent. Signed-off-by: David Marchand --- drivers/net/af_packet/rte_eth_af_packet.c | 4 +++- drivers/net/bonding/rte_eth_bond_api.c | 7 +++

[dpdk-dev] [PATCH] ethdev: check number of queues less than RTE_ETHDEV_QUEUE_STAT_CNTRS

From: Bert van Leeuwen A device can have more than RTE_ETHDEV_QUEUE_STAT_CNTRS queues which is used inside struct rte_eth_stats. Ideally, DPDK should be built with RTE_ETHDEV_QUEUE_STAT_CNTRS to the maximum number of queues a device can support, 65536, as uint16_t

[dpdk-dev] [PATCH] examples/l3fwd: force CRC stripping for i40evf

2016-11-10 13:50, Mori, Naoyuki: > Hi, > > >Thomas wrote: > > > Just to make it sure, you mean returning an error in the driver when > > > a configuration cannot be applied, right? > > > >Yes, as in 1bbcc5d21129 ("i40evf: report error for unsupported CRC > >stripping

[dpdk-dev] [PATCH] ethdev: check number of queues less than RTE_ETHDEV_QUEUE_STAT_CNTRS

2016-11-10 14:00, Alejandro Lucero: > From: Bert van Leeuwen > > A device can have more than RTE_ETHDEV_QUEUE_STAT_CNTRS queues which > is used inside struct rte_eth_stats. Ideally, DPDK should be built with > RTE_ETHDEV_QUEUE_STAT_CNTRS to the maximum number of queues a device > can support,

[dpdk-dev] [PATCH] examples/l3fwd: force CRC stripping for i40evf

Hi Thomas, > 2016-11-10 13:50, Mori, Naoyuki: > > >Thomas wrote: > > > > Just to make it sure, you mean returning an error in the driver when > > > > a configuration cannot be applied, right? > > > > > >Yes, as in 1bbcc5d21129 ("i40evf: report error for unsupported CRC > > >

[dpdk-dev] [PATCH 0/2] enables vhost/virtio any layout feature

On Mon, Sep 26, 2016 at 02:40:54PM +0800, Yuanhan Liu wrote: > The feature is actually supported both in virtio PMD and vhost lib. > We just haven't enabled it yet. This patchset simply enables it. Any input on handling versioning? Do people prefer to handle it completely at the backend, or

[dpdk-dev] [PATCH] ethdev: check number of queues less than RTE_ETHDEV_QUEUE_STAT_CNTRS

On Thu, Nov 10, 2016 at 2:42 PM, Thomas Monjalon wrote: > 2016-11-10 14:00, Alejandro Lucero: > > From: Bert van Leeuwen > > > > A device can have more than RTE_ETHDEV_QUEUE_STAT_CNTRS queues which > > is used inside struct rte_eth_stats. Ideally, DPDK should be built with > >

[dpdk-dev] [PATCH] doc: announce API and ABI changes for librte_eal

On Thu, Nov 10, 2016 at 12:17 PM, Shreyansh Jain wrote: > Signed-off-by: Shreyansh Jain > --- > doc/guides/rel_notes/deprecation.rst | 10 ++ > 1 file changed, 10 insertions(+) > > diff --git a/doc/guides/rel_notes/deprecation.rst > b/doc/guides/rel_notes/deprecation.rst > index

[dpdk-dev] [PATCH] ethdev: check number of queues less than RTE_ETHDEV_QUEUE_STAT_CNTRS

2016-11-10 15:43, Alejandro Lucero: > On Thu, Nov 10, 2016 at 2:42 PM, Thomas Monjalon 6wind.com> > wrote: > > > 2016-11-10 14:00, Alejandro Lucero: > > > From: Bert van Leeuwen > > > > > > A device can have more than RTE_ETHDEV_QUEUE_STAT_CNTRS queues which > > > is used inside struct

[dpdk-dev] [PATCH] ethdev: check number of queues less than RTE_ETHDEV_QUEUE_STAT_CNTRS

On Thu, Nov 10, 2016 at 4:01 PM, Thomas Monjalon wrote: > 2016-11-10 15:43, Alejandro Lucero: > > On Thu, Nov 10, 2016 at 2:42 PM, Thomas Monjalon < > thomas.monjalon at 6wind.com> > > wrote: > > > > > 2016-11-10 14:00, Alejandro Lucero: > > > > From: Bert van Leeuwen > > > > > > > > A device

[dpdk-dev] [PATCH] pdump: fix log message to display correct error number

The ethdev Rx/Tx remove callback apis doesn't set rte_errno during failures, instead they just return negative error number, so using that number in logs instead of rte_errno upon Rx and Tx callback removal failures. Fixes: 278f9454 ("pdump: add new library for packet capture") Signed-off-by:

[dpdk-dev] [PATCH] doc: fix l3fwd mode selection from compile to run time

The l3fwd application route lookup mode can be selected at run time but not at compile time. This patch corrects the statement in the doc. Fixes: d0dff9ba ("doc: sample application user guide") Signed-off-by: Reshma Pattan --- doc/guides/sample_app_ug/l3_forward.rst | 2 +- 1 file changed, 1

[dpdk-dev] [PATCH] doc: fix l3fwd mode selection from compile to run time

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Reshma Pattan > Sent: Thursday, November 10, 2016 4:30 PM > To: dev at dpdk.org > Cc: Pattan, Reshma > Subject: [dpdk-dev] [PATCH] doc: fix l3fwd mode selection from compile to > run time > > The l3fwd

[dpdk-dev] [PATCH] pdump: fix log message to display correct error number

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Reshma Pattan > Sent: Thursday, November 10, 2016 4:30 PM > To: dev at dpdk.org > Cc: Reshma Pattan > Subject: [dpdk-dev] [PATCH] pdump: fix log message to display correct > error number > > The ethdev Rx/Tx

[dpdk-dev] [PATCH] pdump: fix log message to display correct error number

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Reshma Pattan > Sent: Thursday, November 10, 2016 4:30 PM > To: dev at dpdk.org > Cc: Reshma Pattan > Subject: [dpdk-dev] [PATCH] pdump: fix log message to display correct error > number > > The ethdev Rx/Tx

[dpdk-dev] [PATCH] doc: add known issue on QAT PMD into release notes

Issue is with the digest appended feature on QAT PMD. A workaround is also documented. Signed-off-by: Fiona Trahe --- doc/guides/rel_notes/release_16_11.rst | 13 - 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/doc/guides/rel_notes/release_16_11.rst

[dpdk-dev] [PATCH] doc: add known issue on QAT PMD into release notes

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Fiona Trahe > Sent: Thursday, November 10, 2016 4:47 PM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo ; Trahe, Fiona > ; Griffin, John > Subject: [dpdk-dev] [PATCH] doc: add known issue on QAT PMD into

[dpdk-dev] [PATCH] doc: add known issue on QAT PMD into release notes

> -Original Message- > From: Trahe, Fiona > Sent: Thursday, November 10, 2016 4:47 PM > To: dev at dpdk.org > Cc: De Lara Guarch, Pablo ; Trahe, Fiona > ; Griffin, John > Subject: [PATCH] doc: add known issue on QAT PMD into release notes > > Issue is with the digest appended feature

[dpdk-dev] [PATCH] doc: add sub-repositories information

DPDK switched to main and sub-repositories approach, this patch documents new approach and updates development process according. Signed-off-by: Ferruh Yigit --- doc/guides/contributing/patches.rst | 18 +++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git

[dpdk-dev] [PATCH v2] doc: add known issue on QAT PMD into release notes

Issue is with the digest appended feature on QAT PMD. A workaround is also documented. Signed-off-by: Fiona Trahe Acked-by: John McNamara --- v2 - fixed trailing whitespace checkpatch errors doc/guides/rel_notes/release_16_11.rst | 13 - 1 file changed, 12 insertions(+), 1

[dpdk-dev] [PATCH v2] doc: add known issue on QAT PMD into release notes

On 10/11/16 17:27, Fiona Trahe wrote: > Issue is with the digest appended feature on QAT PMD. > A workaround is also documented. > > Signed-off-by: Fiona Trahe > Acked-by: John McNamara > --- > v2 > - fixed trailing whitespace checkpatch errors > Acked-by: John Griffin

[dpdk-dev] [PATCH 2/2] net: align ethdev and eal driver names

On 11/10/2016 1:51 PM, David Marchand wrote: > Some virtual pmds report a different name than the vdev driver name > registered in eal. > While it does not hurt, let's try to be consistent. > > Signed-off-by: David Marchand > --- Since you did all the work, instead of second patch what do you

[dpdk-dev] [PATCH] maintainers: claim responsability for xen

On Wed, Nov 9, 2016 at 5:03 PM, Thomas Monjalon wrote: > 2016-11-07 07:38, Jianfeng Tan: >> As some users are still using xen as the hypervisor, I suggest to >> continue support for xen in DPDK. And from 16.11, I will be the >> maintainer of all xen-related files. >> >> Signed-off-by: Jianfeng

[dpdk-dev] [PATCH] doc: move testpmd guide with other tools

> On Nov 10, 2016, at 5:02 PM, Thomas Monjalon > wrote: > > 2016-11-10 16:11, Mcnamara, John: >> I had a look at the html output before and after this patch and I don't >> quite agree with it. I see that you are trying to clean up and make the >> documentation more consistent but I don't

[dpdk-dev] [PATCH v3] mempool: Add sanity check when secondary link-in less mempools than primary

If the mempool ops the caller wants to use is not registered, the library will segfault in an obscure way when trying to use that mempool. It's better to catch it early and warn the user. If the primary and secondary process were build using different build systems, the list of constructors