[dpdk-dev] [PATCH RFC] eal: change default per socket memory allocation

2014-05-06 Thread Thomas Monjalon
2014-05-06 10:05, Burakov, Anatoly: > David Marchand: > > Actually, if we don't care where memory is allocated, we can at least try > > to have the more common setup work properly (i.e. spread memory > > allocations based on used cores). > > I can see no usual setup where you > > want to use cores

[dpdk-dev] [PATCH RFC] eal: change default per socket memory allocation

2014-05-06 Thread Burakov, Anatoly
Hi Thomas, > Having --socket-mem option to explicitly configure NUMA is OK. > Having -m option for simple configuration is OK. Exactly. No explicit requirements - use -m option. Explicit socket requirements - use --socket-mem option. > So I don't understand why we shouldn't do this enhancement.

[dpdk-dev] [PATCH] Use proper mac type for 82576 VF e1000_vfadapt type corresponds to 82576 VF devices, check e1000_set_mac_type() for more details.

2014-05-06 Thread Konstantin Ananyev
Signed-off-by: Konstantin Ananyev --- lib/librte_pmd_e1000/igb_rxtx.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/librte_pmd_e1000/igb_rxtx.c b/lib/librte_pmd_e1000/igb_rxtx.c index 6b454a5..7fe1780 100644 --- a/lib/librte_pmd_e1000/igb_rxtx.c +++ b/lib/librte_pm

[dpdk-dev] [PATCH] fix for jumbo frame issue with DPDK VF

2014-05-06 Thread Konstantin Ananyev
When latest Linux ixgbe PF is used, and DPDK VF is used in DPDK application, jumbo frames are not received. Also - if Linux ixgbe PF has MTU set to 1500 (default), then normal sized packets can be received by DPDK VF. However, if Linux PF has MTU > 1500, then DPDK VF receives no packets (normal or

[dpdk-dev] RTE Ring removing

2014-05-06 Thread Igor Ryzhov
Hello. For what reason RTE Rings can not be removed once created? In my application I want to use many rings with different names so I think there may be a problem with memory because of many ring that already not in use, but allocated. Or DPDK has a mechanism of reusing memory if rings are not

[dpdk-dev] [PATCH 5/5] add FILE arguement to debug functions

2014-05-06 Thread Burakov, Anatoly
Hi Stephen, > The DPDK dump functions are useful for remote debugging of an > applications. But when application runs as a daemon, stdout > is typically routed to /dev/null. > > Instead change all these functions to take a stdio FILE * handle > instead. An application can then use open_memstream(

[dpdk-dev] [PATCH] Use proper mac type for 82576 VF

2014-05-06 Thread Konstantin Ananyev
e1000_vfadapt type corresponds to 82576 VF devices, check e1000_set_mac_type() for more details. --- lib/librte_pmd_e1000/igb_rxtx.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/lib/librte_pmd_e1000/igb_rxtx.c b/lib/librte_pmd_e1000/igb_rxtx.c index 6b454a5..7fe1780 10

[dpdk-dev] [PATCH] fix for jumbo frame issue with DPDK VF

2014-05-06 Thread Konstantin Ananyev
When latest Linux ixgbe PF is used, and DPDK VF is used in DPDK application, jumbo frames are not received. Also - if Linux ixgbe PF has MTU set to 1500 (default), then normal sized packets can be received by DPDK VF. However, if Linux PF has MTU > 1500, then DPDK VF receives no packets (normal or

[dpdk-dev] Which vmxnet3 pmd is to be used in dpdk 1.6.x?

2014-05-06 Thread Prashant Upadhyaya
Hi Stephen, Kindly let me know if the multi-segment support for vmxnet3 pmd is already in, in a formal release of DPDK. Or which formal release you are targeting this for. Regards -Prashant -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Prashant Upadhyaya Sent:

[dpdk-dev] dpdk-1.6.0r1 problem with Intel 82599ES

2014-05-06 Thread Jun Xiao
It's not really CPU relevance but IOMMU fault, iommu=pt kernel option solves the problem. On Tue, May 6, 2014 at 10:55 AM, Jun Xiao wrote: > Sorry for the spam, I just noticed it's AMD cpu! Is it possible to > make it fail quickly if dpdk cannot really work with AMD cpu? > > On Tue, May 6, 2014 a

[dpdk-dev] dpdk-1.6.0r1 problem with Intel 82599ES

2014-05-06 Thread Jun Xiao
Sorry for the spam, I just noticed it's AMD cpu! Is it possible to make it fail quickly if dpdk cannot really work with AMD cpu? On Tue, May 6, 2014 at 10:26 AM, Jun Xiao wrote: > Hi, > > I am running dpdk-1.6.0r1 with Intel 82599ES with some problems: > - The test driver is l2fwd, and it is star

[dpdk-dev] dpdk-1.6.0r1 problem with Intel 82599ES

2014-05-06 Thread Jun Xiao
Hi, I am running dpdk-1.6.0r1 with Intel 82599ES with some problems: - The test driver is l2fwd, and it is started successfully without any problem (all DEBUG build flags are enabled, but I didn't find anything abnormal) - l2fwd cannot see any packet generated by pktgen on another machine. - The c

[dpdk-dev] [PATCH RFC] eal: change default per socket memory allocation

2014-05-06 Thread Burakov, Anatoly
Hi David, > Actually, if we don't care where memory is allocated, we can at least try to > have the more common setup work properly (i.e. spread memory allocations > based on used cores). > I can see no usual setup where you want to use cores on a socket while having > all memory on another soc

[dpdk-dev] [PATCH 4/5] memzone: add iterator function

2014-05-06 Thread Burakov, Anatoly
Hi Stephen, > When doing diagnostic function, it is useful to have a ability to iterate > over all > memzones. > You can already access all memzones through rte_eal_get_configuration()->mem_config.memzone[idx]. Best regards, Anatoly Burakov DPDK SW Engineer

[dpdk-dev] [PATCH 00/16] [RFC] [VFIO] Add VFIO support to DPDK

2014-05-06 Thread Burakov, Anatoly
Hi Vincent, > My 2 cents: >http://dpdk.org/browse/virtio-net-pmd/tree/README.rst > it works without UIO. > I meant the in-tree virtio driver. Obviously anything that doesn't depend on UIO will work with VFIO as well (or even without both - compilation of both will be optional). Best regar

[dpdk-dev] [PATCH 5/5] add FILE arguement to debug functions

2014-05-06 Thread Neil Horman
On Mon, May 05, 2014 at 06:55:31PM -0700, Stephen Hemminger wrote: > On Mon, 5 May 2014 06:53:09 -0400 > Neil Horman wrote: > > > On Sun, May 04, 2014 at 01:17:50PM -0700, Stephen Hemminger wrote: > > > On Sun, 4 May 2014 08:20:54 -0400 > > > Neil Horman wrote: > > > > > > > On Fri, May 02, 201