[dpdk-dev] [PATCH] skeleton app: Very simple code for l2fwding

> +#ifdef RTE_EXEC_ENV_BAREMETAL >>+#define MAIN _main >>+#else >>+#define MAIN main >>+#endif >>+ >>+int MAIN(int argc, char *argv[]); >>+ >>+#endif /* ifndef_MAIN_H_ */ why keeping the baremetal? It was dropped for a while. Best regards, Vincent

[dpdk-dev] [PATCH] skeleton app: Very simple code for l2fwding

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Vincent JARDIN > Sent: Thursday, June 26, 2014 1:57 PM > To: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH] skeleton app: Very simple code for l2fwding > > > +#ifdef RTE_EXEC_ENV_BAREMETAL > >>+#define MAIN

[dpdk-dev] [PATCH] skeleton app: Very simple code for l2fwding

On Thu, Jun 26, 2014 at 09:22:40PM +0100, Bruce Richardson wrote: > This is a very simple example app for doing packet forwarding with the > Intel DPDK. It's designed to serve as a start point for people new to > the Intel DPDK and who want to develop a new app. > > Therefore it's meant to: > *

[dpdk-dev] [PATCH v8 0/6] Link Bonding Library

> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Declan Doherty > Sent: Wednesday, June 25, 2014 9:08 PM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH v8 0/6] Link Bonding Library > > This patch contains the initial release of the Link Bonding PMD

[dpdk-dev] [PATCH 1/3] stringfns: remove rte_snprintf

> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Wednesday, June 25, 2014 1:33 AM > To: Richardson, Bruce > Cc: dev at dpdk.org; Stephen Hemminger > Subject: Re: [dpdk-dev] [PATCH 1/3] stringfns: remove rte_snprintf > > 2014-06-24 17:39,

[dpdk-dev] [PATCH 5/5] testpmd: change some of testpmd default parameter to well tuned value

We usually use testpmd fwd to demostrate IO forwarding throughput. For best throughput, it has to assign the special parameter to testpmd. To makes it easier to run, now set it as defalut value. Such parameters are MBUF Mempool Cache and RX/TX threshold registers. MBCACHE: 250 RX threshold

[dpdk-dev] [PATCH 4/5] ixgbe: set default burst size 32 in testpmd

The vpmd RX don't accept burst size less than 32. As vPMD is set =y by default, while default testpmd burst size is 16. Which will cause RX nothing if not assign burst size correctly. Signed-off-by: Cunming Liang Acked-by: Bruce Richardson Acked-by: Yong Liu Tested-by: Zhaochen Zhan ---

[dpdk-dev] [PATCH 3/5] ixgbe: not 'DISABLE' may make confuse, change RTE_IXGBE_RX_OLFLAGS_DISABLE=n to RTE_IXGBE_RX_OLFLAGS_ENABLE=y

RTE_IXGBE_RX_OLFLAGS_ENABLE gives a hint whick keeping packet type in RX ol_flags or not. By default it is set to update ol_flags in RX mbuf header. If unset it, will gain addtional performance, but will lose packet type information. Signed-off-by: Cunming Liang Acked-by: Bruce Richardson

[dpdk-dev] [PATCH 2/5] ixgbe: fix vpmd compiling error when RTE_LIBRTE_IEEE1588=y

Signed-off-by: Cunming Liang Acked-by: Bruce Richardson Acked-by: Yong Liu Tested-by: Zhaochen Zhan --- lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c | 1 + 1 file changed, 1 insertion(+) diff --git a/lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c b/lib/librte_pmd_ixgbe/ixgbe_rxtx_vec.c index

[dpdk-dev] [PATCH 1/5] ixgbe: avoid compiler error when RTE_IXGBE_INC_VECTOR=y and RTE_LIBRTE_IXGBE_RX_ALLOC_BULK_ALLOC=n

The vpmd RX routine won't be used if RTE_LIBRTE_IXGBE_RX_ALLOW_BULK_ALLOC is not defined or its condition check fail. The case RTE_LIBRTE_IXGBE_RX_ALLOC_BULK_ALLOC=n and RTE_IXGBE_INC_VECTOR=y may exist when choose to use standard RX and optimized TX(ixgbe_xmit_pkts_vec/ixgbe_xmit_pkts_simple).

[dpdk-dev] [PATCH 0/5] ixgbe: vPMD compiling issue and testpmd default value change

This patch is used to fix several issue found in R1.7 RC1. 1. There's compiling error when change some defalut config in common_linuxapp. They are RTE_LIBRTE_IXGBE_RX_ALLOC_BULK_ALLOC=n RTE_LIBRTE_IEEE1588=y 2. Renaming RTE_IXGBE_RX_OLFLAGS_DISABLE to RTE_IXGBE_RX_OLFLAGS_ENABLE

[dpdk-dev] [PATCH v3 0/2] malloc: fix malloc and free linear complexity

> From: Robert Sanford > > Comments on previous versions of this patch: > > http://dpdk.org/ml/archives/dev/2014-May/002297.html > > http://dpdk.org/ml/archives/dev/2014-June/003518.html > > > > Additional changes from original to v3: > > * Reduce the minimum-sized block that we put on a free

[dpdk-dev] [PATCH 0/5] ixgbe: vPMD compiling issue and testpmd default value change

2014-06-26 14:53, Cunming Liang: > This patch is used to fix several issue found in R1.7 RC1. > 1. There's compiling error when change some defalut config in > common_linuxapp. They are >RTE_LIBRTE_IXGBE_RX_ALLOC_BULK_ALLOC=n >RTE_LIBRTE_IEEE1588=y > 2. Renaming

[dpdk-dev] [PATCH] ixgbe: Alternative fix for 82599 Bypass NIC, getting incorrect media type

> > This was previosly solved in commit > > 60a70d4e042350ca0f9200334b341063438be89b, but this alternative fix solves > > the same issue, but without modifying the ixgbe shared code. > > > > Signed-off-by: Pablo de Lara > > Acked-by: Konstantin Ananyev Applied for version 1.7.0. Thanks --

[dpdk-dev] [PATCH] i40e: fix shared code compile warning

2014-06-24 14:43, Ananyev, Konstantin: > Yes, it is much nicer to fix it in i40e_lan_hmc.c. > But I don't really want us to open that door. > So my vote would be to initial Mark's patch: add '-Wno-error' in the > Makefile. 2014-06-24 15:25, Zhang, Helin: > We should not modify code in shared

[dpdk-dev] [PATCH 0/3] previous patches about "shared code"/"base drivers"

2014-06-25 16:07, Richardson, Bruce: > > Thomas Monjalon (1): > > i40e: explicit shared code naming as base driver > > Chen Jing D(Mark) (1): > > i40e/base: ignore warning > > Pablo de Lara (1): > > ixgbe: rework fix of media type for bypass device > > Acked-by: Bruce Richardson I've done

[dpdk-dev] [PATCH 1/3] stringfns: remove rte_snprintf

On Jun 26, 2014, at 12:09 PM, Richardson, Bruce wrote: >> I agree we should try to use the "deprecated" attribute when possible. >> So application porting effort will be smoother. >> >> But in this case, there is something different: as Stephen wrote, >> rte_snprintf >> is useless. It's

[dpdk-dev] [PATCH] kni: compatibility with RHEL 7

Hi, > Subject: RE: [dpdk-dev] [PATCH] kni: compatibility with RHEL 7 > > Hi Hiroshi, > > Helin submitted one patch to fix compilation error in the redhat 6.4 and > 6.5. > Patch title is [dpdk-dev] [PATCH] kni: fix compile errors on Oracle > Linux6.4 and RHEL6.5 > With this patch, we

[dpdk-dev] [PATCH] kni: compatibility with RHEL 7

Hi Hiroshi, Helin submitted one patch to fix compilation error in the redhat 6.4 and 6.5. Patch title is [dpdk-dev] [PATCH] kni: fix compile errors on Oracle Linux6.4 and RHEL6.5 With this patch, we don't meet this compilation error in latest RHEL 7.0 Can you download latest DPDK code,

[dpdk-dev] [PATCH] eal: fix invalid memory read as reported by valgrind

==29880== Invalid read of size 1 ==29880==at 0x56FF9A5: cpu_socket_id (eal_lcore.c:101) ==29880==by 0x56FFAE9: rte_eal_cpu_init (eal_lcore.c:168) ==29880==by 0x56F944A: rte_eal_init (eal.c:975) The problem is that endptr points to memory allocated underneath the DIR handle, which has

[dpdk-dev] [PATCH] dpdk_nic_bind: allow status query without igb_uio

From: Bruce richardson Allow the nic bind/unbind script to print out its status messages even if the igb_uio driver is not loaded. For binding and unbinding NICs, the behaviour is the same, and the igb_uio driver still needs to be loaded. Signed-off-by: Bruce