2015-07-20 18:04, Rauta, Alin:
> --- a/lib/Makefile
> +++ b/lib/Makefile
> @@ -33,7 +33,6 @@ include $(RTE_SDK)/mk/rte.vars.mk
>
> DIRS-y += librte_compat
> DIRS-$(CONFIG_RTE_LIBRTE_EAL) += librte_eal
> -DIRS-$(CONFIG_RTE_LIBRTE_EAL) += librte_malloc
I feel it's not the right fix :)
>From
2015-07-20 10:25, Stephen Hemminger:
> Fix for a fix for a fix...
> This set includes Changchun's patch for vq_size but adds
> follow on fix to make it work with GCE and other environments.
>
> Ouyang Changchun (1):
> virtio: fix the vq size issue
>
> Stephen Hemminger (2):
> virtio: allow
Signed-off-by: Alin Rauta
---
lib/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/lib/Makefile b/lib/Makefile index 2055539..9727b83 100644
--- a/lib/Makefile
+++ b/lib/Makefile
@@ -33,7 +33,6 @@ include $(RTE_SDK)/mk/rte.vars.mk
DIRS-y += librte_compat
Hi,
I'm trying to build the latest dpdk code into one combine library, but the
compilation fails like below. The issue seems to be around "librte_malloc".
" make install T=x86_64-native-linuxapp-gcc"
== Build lib/librte_malloc
AR librte_malloc.a
cp: missing destination file operand after
Hi David,
On Mon, Jul 20, 2015 at 09:43:57 +0200, David Marchand wrote:
>Hum, what bothers me is that you do not rely on the same criteria to
>re-attach the devices to nic_uio.
>See below.
>
> ?lib/librte_eal/bsdapp/nic_uio/nic_uio.c | 48
> +
To fix the FVL's flow director issue for SCTP flow, rte_eth_fdir_filter
need to be change to support SCTP flow keys extension. Here announce
the ABI deprecation.
Signed-off-by: jingjing.wu
---
doc/guides/rel_notes/deprecation.rst | 4
1 file changed, 4 insertions(+)
diff --git
> Fixes: f6bf669b990004dc69231476d9fcf0b80574e568. Bug fix to remove
> (rxnfgpc - hw_stats->gprc) which does not account for phy errors.
> hw_stats->gprc is the Number of good (non-erred) Rx packets (from the
> network) that pass L2 filtering and has a legal length as defined by
>
Hi All,
Need your inputs on the following queries on ACL contexts.
1. Has anyone tried creating ACL context with multiple tries?
2. The document/code mentioned that we can have the maximum of 8
tries(RTE_ACL_MAX_TRIES) per ACL context.
What is the use case for having more than single trie?
Fixes: f6bf669b990004dc69231476d9fcf0b80574e568. Bug fix to remove
(rxnfgpc - hw_stats->gprc) which does not account for phy errors.
hw_stats->gprc is the Number of good (non-erred) Rx packets (from the
network) that pass L2 filtering and has a legal length as defined by
LongPacketEnable. While
Signed-off-by: Konstantin Ananyev
---
app/test-pmd/cmdline.c | 48
app/test-pmd/config.c | 67 ++
app/test-pmd/testpmd.h | 2 ++
3 files changed, 117 insertions(+)
diff --git a/app/test-pmd/cmdline.c
Signed-off-by: Konstantin Ananyev
---
drivers/net/ixgbe/ixgbe_ethdev.c | 4
drivers/net/ixgbe/ixgbe_ethdev.h | 6 ++
drivers/net/ixgbe/ixgbe_rxtx.c | 42
3 files changed, 52 insertions(+)
diff --git a/drivers/net/ixgbe/ixgbe_ethdev.c
Signed-off-by: Konstantin Ananyev
---
drivers/net/i40e/i40e_ethdev.c | 2 ++
drivers/net/i40e/i40e_ethdev.h | 5 +
drivers/net/i40e/i40e_rxtx.c | 42 ++
3 files changed, 49 insertions(+)
diff --git a/drivers/net/i40e/i40e_ethdev.c
Add the ability for the upper layer to query RX/TX queue information.
Add new structures:
struct rte_eth_rxq_info
struct rte_eth_txq_info
new functions:
rte_eth_rx_queue_info_get
rte_eth_tx_queue_info_get
into rte_etdev API.
Left extra free space in the queue info structures,
so extra fields
Add the ability for the upper layer to query RX/TX queue information.
Right now supported for:
ixgbe, i40e, e1000 PMDs.
Konstantin Ananyev (5):
ethdev: add new API to retrieve RX/TX queue information
i40e: add support for eth_(rxq|txq)_info_get
ixgbe: add support for eth_(rxq|txq)_info_get
Bug fix to remove (rxnfgpc - hw_stats->gprc) which does not account
for phy errors. hw_stats->gprc is the Number of good (non-erred) Rx
packets (from the network) that pass L2 filtering and has a legal
length as defined by LongPacketEnable. While rxnfgpc is the Number of
good (non-erred with legal
2015-07-20 06:18, Ouyang, Changchun:
> Another thing burst into my thought.
> Can we think more about how to setup a mechanism to block those patches which
> causes critical regression issue?
Yes. Non-regression tests are needed. As it must be done with many hardwares
and many configurations, it
Update cxgbe documentation to include support for FreeBSD:
1. Add instructions on how to compile CXGBE PMD in FreeBSD.
2. Add instructions on how to flash firmware image on Chelsio T5 cards in
FreeBSD.
3. Add sample application usage for FreeBSD.
4. Add an extra step to reload kernel module in
Fix "MACRO redefined" and "function redefined" compilation errors in FreeBSD
by adding CXGBE prefix to them. Also remove reference to a linux header
linux/if_ether.h and use DPDK macros directly. Finally, enable CXGBE PMD for
FreeBSD.
Signed-off-by: Rahul Lakkireddy
Signed-off-by: Kumar
This series of patches fix compilation and enable CXGBE poll mode driver for
FreeBSD. The first patch fixes a limitation of nic_uio that only binds to
devices present in rte_pci_dev_ids.h. The second patch does the actual
compilation fix and enabling of CXGBE PMD for FreeBSD. The last patch
Some minor cleanups.
* pass constant to virtio_dev_queue_setup
* fix message on rx_queue_setup
* get rid of extra double spaces
Signed-off-by: Stephen Hemminger
---
drivers/net/virtio/virtio_ethdev.c | 7 +++
drivers/net/virtio/virtio_ethdev.h | 2 +-
drivers/net/virtio/virtio_rxtx.c
On Mon, 20 Jul 2015 19:43:20 +0200
Thomas Monjalon wrote:
> 2015-07-20 10:25, Stephen Hemminger:
> > Fix for a fix for a fix...
> > This set includes Changchun's patch for vq_size but adds
> > follow on fix to make it work with GCE and other environments.
> >
> > Ouyang Changchun (1):
> >
Hi Wenzhuo,
> Hi Klaus,
>
>> -Original Message-
>> From: Klaus Degner [mailto:kd at allegro-packets.com]
>> Sent: Friday, July 17, 2015 7:56 PM
>> To: Lu, Wenzhuo
>> Cc: dev at dpdk.org
>> Subject: jumbo frame support for 82583V
>>
>> Hi Wenzhuo,
>>
>> We are testing different Intel NICs
The patch demonstrates how to handle per rx queue interrupt in a NAPI-like
implementation in userspace. The working thread mainly runs in polling mode
and switch to interrupt mode only if there is no packet received in recent
polls.
The working thread returns to polling mode immediately once it
The patch does below for igb PF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register to map interrupt causes to vectors
- Implement interrupt enable/disable functions
Signed-off-by: Danny Zhou
Signed-off-by: Cunming Liang
---
v14 changes
- per-patch basis ABI compatibility rework
The patch does below things for ixgbe PF and VF:
- Setup NIC to generate MSI-X interrupts
- Set the IVAR register to map interrupt causes to vectors
- Implement interrupt enable/disable functions
Signed-off-by: Danny Zhou
Signed-off-by: Yong Liu
Signed-off-by: Cunming Liang
---
v14 changes
-
The patch adds two dev_ops functions to enable and disable rx queue interrupts.
In addtion, it adds rte_eth_dev_rx_intr_ctl/rx_intr_q to support per port or
per queue rx intr event set.
Signed-off-by: Danny Zhou
Signed-off-by: Cunming Liang
---
v15 changes
- remove ifdef RTE_NEXT_ABI from
Signed-off-by: Cunming Liang
---
lib/librte_eal/bsdapp/eal/include/exec-env/rte_interrupts.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/lib/librte_eal/bsdapp/eal/include/exec-env/rte_interrupts.h
b/lib/librte_eal/bsdapp/eal/include/exec-env/rte_interrupts.h
index
To make bsd compiling happy with new intr changes.
Signed-off-by: Cunming Liang
---
v15 changes
- remove ifdef RTE_NEXT_ABI from header file
v14 changes
- per-patch basis ABI compatibility rework
v13 changes
- version map cleanup for v2.1
v12 changes
- fix unused variables compiling
The intr handle type(RTE_INTR_HANDLE_UIO_INTX) was introduced by UIO pci
generic.
When turning on the lsc interrupt, it complains fd read error.
The patch uses the correct read size in the case of RTE_INTR_HANDLE_UIO_INTX.
Fixes: 3f313bef3467 ("eal/linux: fix irq handling with igb_uio")
The patch exposes intr event fd create and release for PMD.
The device driver can assign the number of event associated with interrupt
vector.
It also provides misc functions to check 1) allows other slowpath intr(e.g.
lsc);
2) intr event on fastpath is enabled or not.
Signed-off-by: Cunming
The patch maps each of the eventfd to the interrupt vector of VFIO MSI-X.
Signed-off-by: Danny Zhou
Signed-off-by: Cunming Liang
---
v14 changes
- per-patch basis ABI compatibility rework
- reword commit comments
v8 changes
- move eventfd creation out of the setup_interrupts to a standalone
Signed-off-by: Cunming Liang
---
lib/librte_eal/linuxapp/eal/eal_interrupts.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/lib/librte_eal/linuxapp/eal/eal_interrupts.c
b/lib/librte_eal/linuxapp/eal/eal_interrupts.c
index ffccb0e..5acc3b7 100644
---
The patch adds 'rte_intr_rx_ctl' to add or delete interrupt vector events
monitor on specified epoll instance.
Signed-off-by: Cunming Liang
---
v15 changes
- remove ifdef RTE_NEXT_ABI from header file
v14 changes
- per-patch basis ABI compatibility rework
- remove unnecessary 'local: *'
The patch adds 'rte_epoll_wait' and 'rte_epoll_ctl' for async event wakeup.
It defines 'struct rte_epoll_event' as the event param.
When the event fds add to a specified epoll instance, 'eptrs' will hold the
rte_epoll_event object pointer.
The 'op' uses the same enum as epoll_wait/ctl does.
The
The patch adds interrupt vectors support in rte_intr_handle.
'vec_en' is set when interrupt vectors are detected and associated event fds
are set.
Those event fds are stored in efds[].
'intr_vec' is reserved for device driver to initialize the vector mapping table.
Signed-off-by: Danny Zhou
v15 changes
- remove unnecessary RTE_NEXT_ABI comment
- remove ifdef RTE_NEXT_ABI from header file
v14 changes
- per-patch basis ABI compatibility rework
- remove unnecessary 'local: *' from version map
- minor comments rework
v13 changes
- version map cleanup for v2.1
- replace
Some minor cleanups.
* pass constant to virtio_dev_queue_setup
* fix message on rx_queue_setup
* get rid of extra double spaces
Signed-off-by: Stephen Hemminger
---
drivers/net/virtio/virtio_ethdev.c | 7 +++
drivers/net/virtio/virtio_ethdev.h | 2 +-
drivers/net/virtio/virtio_rxtx.c
When running on GCE vq_size is 16K but number of Rx descriptors
desired maybe less than that. Handle the situtaiton by initializing
full ring but only filling the smaller number.
Signed-off-by: Stephen Hemminger
---
drivers/net/virtio/virtio_ethdev.c | 9 -
1 file changed, 4
From: Ouyang Changchun
This commit breaks virtio basic packets rx functionality:
d78deadae4dca240e85054bf2d604a801676becc
The QEMU use 256 as default vring size, also use this default value to
calculate the virtio avail ring base address and used ring base
address,
Fix for a fix for a fix...
This set includes Changchun's patch for vq_size but adds
follow on fix to make it work with GCE and other environments.
Ouyang Changchun (1):
virtio: fix the vq size issue
Stephen Hemminger (2):
virtio: allow nb_desc < vq_size
virtio: small cleanups
The example includes an ethtool library and two applications:
one application is a non- DPDK process (nic-control)
and the other is a DPDK l2fwd applicaiton (l2fwd-app).
The nic-control process sends ethtool alike device management
requests to l2fwd-app through a named pipe IPC. This example
is
This implementation is designed to provide an example illlustrating how to
create a
user-space ethtool library from existing ethdev APIs. This example only
implements
19 popular used Ethtool and Netdevice ops as described in
examples/l2fwd-ethtool/lib/rte_ethtool.h
Liang-Min Larry Wang (1):
On 7/18/2015 5:40 AM, Stephen Hemminger wrote:
>> +/**
>>* Turn on the LED on the Ethernet device.
>>* This function turns on the LED on the Ethernet device.
>>*
>> diff --git a/lib/librte_ether/rte_ether_version.map
>> b/lib/librte_ether/rte_ether_version.map
>> index
On 7/20/2015 7:39 AM, Thomas Monjalon wrote:
> 2015-07-20 01:35, Thomas Monjalon:
>> 2015-07-17 14:16, Cunming Liang:
>>> +#ifdef RTE_NEXT_ABI
>>> +extern int
>>> +rte_intr_efd_enable(struct rte_intr_handle *intr_handle, uint32_t nb_efd);
>>> +#else
>>> +static inline int
>>>
Hi Thomas,
On 07/20/2015 03:00 AM, Thomas Monjalon wrote:
> Please Olivier,
> What is the status of this patch?
>From what I remember, the last mail was a comment from Konstantin
on another thread (but same topic):
http://dpdk.org/ml/archives/dev/2015-May/017633.html
Regards,
Olivier
>
>
On 7/20/2015 7:31 AM, Thomas Monjalon wrote:
> 2015-07-17 14:16, Cunming Liang:
>> +#ifdef RTE_NEXT_ABI
>> +/**
>> + * RTE_NEXT_ABI will be removed from v2.2.
>> + * It's only used to avoid ABI(unannounced) broken in v2.1.
>> + * Make sure being aware of the impact before turning
> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Monday, July 20, 2015 1:13 AM
> To: Ananyev, Konstantin
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCHv2 1/5] ethdev: add new API to retrieve RX/TX
> queue information
>
> 2015-06-18
> -Original Message-
> From: Ananyev, Konstantin
> Sent: Monday, July 20, 2015 10:37 AM
> To: Richardson, Bruce; dev at dpdk.org
> Subject: RE: [dpdk-dev] [PATCH 2/2] ixgbe: check mbuf refcnt when clearing
> RX/TX ring
>
> Hi Bruce,
>
> > -Original Message-
> > From: dev
Hi Bruce,
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Bruce Richardson
> Sent: Friday, July 03, 2015 4:40 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH 2/2] ixgbe: check mbuf refcnt when clearing RX/TX
> ring
>
> The function to clear the TX
This is build infrastructure changes for bnx2x driver.
- enable BNX2X poll mode driver in default config.
- add it to mk
- put entry in MAINTAINERS
Note: I intentionally did not list myself as maintainer of this
driver. QLogic has discussed taking over as maintainer.
Signed-off-by: Stephen
More code for the Broadcom/Qlogic NetExtreme II poll mode driver.
Split into pieces for review and not to overwhelm mailers.
Signed-off-by: Stephen Hemminger
---
drivers/net/bnx2x/debug.c | 113 +
drivers/net/bnx2x/ecore_fw_defs.h | 422 +
This is the first of several parts for a new driver supporting
Broadcom/Qlogic NetXtremeII 10 gigabit devices.
Signed-off-by: Stephen Hemminger
---
drivers/net/bnx2x/bnx2x.c| 11821 +
drivers/net/bnx2x/bnx2x.h| 1998 +++
Some drivers need ability to access PCI config (for example for power
management). This adds an abstraction to do this for both Linux
and BSD.
Signed-off-by: Stephen Hemminger
---
lib/librte_eal/bsdapp/eal/eal_pci.c | 83 +
Changes in this version (v5):
- rebase to 2.1.0-rc1
- fix version map for 2.1
- fix doxygen comments
- add BCM57410 ids
Stephen Hemminger (4):
eal: provide functions to access PCI config
bnx2x: driver core
bnx2x: driver support routines
bnx2x: enable PMD build
MAINTAINERS
Acked-by: Marvin Liu
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Jijiang Liu
> Sent: Friday, July 17, 2015 4:13 PM
> To: dev at dpdk.org
> Subject: [dpdk-dev] [PATCH] doc/testpmd_app_ug:add a comment for outer-ip
> option in csum
>
> Add a comment for
On Sat, 18 Jul 2015 12:11:11 +
"Ouyang, Changchun" wrote:
> Hi Stephen,
>
> > -Original Message-
> > From: Stephen Hemminger [mailto:stephen at networkplumber.org]
> > Sent: Saturday, July 18, 2015 12:28 AM
> > To: Ouyang, Changchun
> > Cc: dev at dpdk.org
> > Subject: Re:
We?are?very?excited?to?announce?that?CloudNetEngine?vswitch?is?available?for
technical?preview!
CloudNetEngine?vswitch?perfectly?bridges the?gaps?of?performance,?efficiency?and
full?feature?requirements?which?existing?vswitches?simply?cannot?provide.
On Mon, 20 Jul 2015 06:18:53 +
"Ouyang, Changchun" wrote:
> Hi Thomas,
>
> I think we have 3 options for this issue.
> 1) applying this patch;
> 2) reverting Stephen's original patch;
> 3) new patch to make both QEMU and GCE work.
I am working on #3
On Sun, Jul 19, 2015 at 12:52:13PM +0200, Thomas Monjalon wrote:
> The main change of these patches is to improve naming consistency
> across ethdev and EAL.
> It should be applied shortly to be part of rc1. If some comments arise,
> it can be fixed/improved in rc2.
>
> Thomas Monjalon (4):
>
Hi Thomas,
I think we have 3 options for this issue.
1) applying this patch;
2) reverting Stephen's original patch;
3) new patch to make both QEMU and GCE work.
1) and 2) will make the test case recover quickly from fail.
As for 3) I don't know whether Stephen has such a patch which can work on
A new DPDK release candidate is ready for testing:
http://dpdk.org/browse/dpdk/tag/?id=v2.1.0-rc1
This is the first release candidate for DPDK 2.1.
It means we are entering in the RC testing phase.
Only fixes and cleanups will be accepted.
Changelog (main enhancements since 2.0.0)
Hi, Thomas and all
I saw in the latest rc1 package, the patch is not merged, and it's a critical
issue from validation view. I'm responsible for testing the dpdk vhost/virtio
features, and I found using the latest code, dpdk-vhost/dpdk-virtio can't RX/TX
package, then my 50% tests are failed
Hi Klaus,
> -Original Message-
> From: Klaus Degner [mailto:kd at allegro-packets.com]
> Sent: Friday, July 17, 2015 7:56 PM
> To: Lu, Wenzhuo
> Cc: dev at dpdk.org
> Subject: jumbo frame support for 82583V
>
> Hi Wenzhuo,
>
> We are testing different Intel NICs for DPDK. We have tested
Please Olivier,
What is the status of this patch?
2015-05-12 01:15, Paul Emmerich:
> this improves the throughput of a simple tx-only application by 11% in
> the full-featured ixgbe tx path and by 14% in the simple tx path.
> ---
> lib/librte_mbuf/rte_mbuf.h | 1 +
> 1 file changed, 1
> > This problem was discovered when passing invalid PCI id to the
> > blacklist API in devargs.
> >
> > Any failures in rte_devargs_add would cause a core dump because
> > it would call rte_log() before the the EAL log environment was
> > initailized. Rather than try and log just remove the
> Change the log level of startup messages. Anything that is
> just normal activity (like getting virtual areas) is changed
> to debug level. Anything that is a failure should be NOTICE
> or ERR severity.
>
> Signed-off-by: Stephen Hemminger
Applied, thanks
> These are a couple things found while doing code inspection for
> some other bonding related issues.
>
> Stephen Hemminger (2):
> ethdev: make rte_eth_dev_is_valid_port public
> bonding: fix name and port validation
Applied, thanks
Hi,
> -Original Message-
> From: Wiles, Keith
> Sent: Friday, July 17, 2015 7:06 PM
> To: Thomas Monjalon; Stephen Hemminger; Lu, Wenzhuo
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] igb PMD should set the default tx wthresh correctly.
>
>
>
> On 7/17/15, 9:15 AM, "dev on behalf of
2015-06-18 14:18, Konstantin Ananyev:
> new functions:
> rte_eth_rx_queue_info_get
> rte_eth_tx_queue_info_get
>
> into rte_etdev API.
[...]
> lib/librte_ether/rte_ethdev.c | 54 ++
> lib/librte_ether/rte_ethdev.h | 77
> ++-
>
2015-07-15 10:16, Stephen Hemminger:
> The read for events in the interrupt thread may get interrupted
> by signals from application. Avoid generating stray log message.
>
> Signed-off-by: Stephen Hemminger
Applied, thanks
2015-07-20 01:35, Thomas Monjalon:
> 2015-07-17 14:16, Cunming Liang:
> > +#ifdef RTE_NEXT_ABI
> > +extern int
> > +rte_intr_efd_enable(struct rte_intr_handle *intr_handle, uint32_t nb_efd);
> > +#else
> > +static inline int
> > +rte_intr_efd_enable(struct rte_intr_handle *intr_handle, uint32_t
2015-07-17 14:16, Cunming Liang:
> +#ifdef RTE_NEXT_ABI
> +extern int
> +rte_intr_efd_enable(struct rte_intr_handle *intr_handle, uint32_t nb_efd);
> +#else
> +static inline int
> +rte_intr_efd_enable(struct rte_intr_handle *intr_handle, uint32_t nb_efd)
> +{
> + RTE_SET_USED(intr_handle);
> +
2015-07-17 14:16, Cunming Liang:
> +#ifdef RTE_NEXT_ABI
> + /**
> + * RTE_NEXT_ABI will be removed from v2.2.
> + * It's only used to avoid ABI(unannounced) broken in v2.1.
> + * Make sure being aware of the impact before turning on the feature.
> + */
We are not going to
2015-07-17 23:50, Rahul Lakkireddy:
> nic_uio requires the pci ids to be present in rte_pci_dev_ids.h in order to
> bind the devices to nic_uio. However, it's better to remove this whitelist of
> pci ids, and instead rely on hw.nic_uio.bdfs kenv parameter to allow binding
> any device to nic_uio.
There was no explanation.
The changed title should be more explicit:
"i40e: fix registers access from big endian CPU"
> > Signed-off-by: Zhe Tao
> Acked-by: Chao Zhu
Applied, thanks
> > I40e VF driver uses the num_queue_pairs in vf structure to construct queue
> > index look up table. When the nb_rx_queue is less than nb_tx_queue,
> > num_queue_pairs is equal to nb_tx_queue. It will make the table use invalid
> > queue index, then application cannot poll packets on these
> > This patch set fixes the issue SCTP flow cannot be matched by FVL's flow
> > director. The issue's root cause is that due to the NIC's firmware update,
> > the input set of sctp flow are changed to source IP, destination IP,
> > source port, destination port and Verification-Tag, which are
Not sure for Mr. Kim, but for me, performance is actually not my main
inspiration to use DPDK. I began using it in about 2011 when I got a training
on it from the 6WIND guys before it became open source. What impressed me most
was how much simpler it was to troubleshoot, debug, maintain, and
2015-07-13 14:04, Bernard Iremonger:
> Signed-off-by: Bernard Iremonger
Applied without the first patch which seems useless.
2015-07-19 12:52, Thomas Monjalon:
> The main change of these patches is to improve naming consistency
> across ethdev and EAL.
> It should be applied shortly to be part of rc1. If some comments arise,
> it can be fixed/improved in rc2.
>
> Thomas Monjalon (4):
> doc: rename ABI chapter to
80 matches
Mail list logo