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

2014-05-13 Thread Thomas Monjalon
Hi Venky, There were comments on the first version of this patch and you suggested to try this new implementation. So do you acknowledge this patch? Thanks for your review 2014-05-09 15:30, David Marchand: > From: Didier Pallard > > Currently, if there is more memory in hugepages than the amo

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

2014-05-13 Thread Venkatesan, Venky
From: Didier Pallard Currently, if there is more memory in hugepages than the amount requested by dpdk application, the memory is allocated by taking as much memory as possible from each socket, starting from first one. For example if a system is configured with 8 GB in 2 sockets (4 GB per sock

[dpdk-dev] [PATCH v2 0/2] ring: allow to init a rte_ring outside of an rte_memzone

2014-05-13 Thread Thomas Monjalon
> These 2 patches adds 2 new functions that permits to initialize and use > a rte_ring anywhere in memory. > > Before this patches, only rte_ring_create() was available. This function > allocates a rte_memzone (that cannot be freed) and initializes a ring > inside. > > This series allows to do th

[dpdk-dev] [PATCH v2 0/7] pci cleanup

2014-05-13 Thread Thomas Monjalon
2014-05-09 15:15, David Marchand: > Hello all, > > Here is an attempt at having an equal implementation in bsd and linux > eal_pci.c. It results in following changes : > - checks on driver flag in bsd which were missing > - remove virtio-uio workaround in linux eal_pci.c > - remove deprecated RTE_

[dpdk-dev] [PATCH] EAL: Take reserved hugepages into account

2014-05-13 Thread Thomas Monjalon
2014-04-16 11:11, Burakov, Anatoly: > Some applications reserve hugepages for later use, but DPDK doesn't take > reserved pages into account when calculating number of available number of > hugepages. This patch adds reading from "resv_hugepages" file in addition > to "free_hugepages". Acked-by: T

[dpdk-dev] [PATCH] version: 1.7.0-rc0

2014-05-13 Thread Thomas Monjalon
> > Start development cycle for version 1.7.0. > > > > This new development workflow introduces a new versioning scheme. > > Instead of having releases r0, r1, r2, etc, there will be release > > candidates. Last number has special meanings: > > < 16 numbers are reserved for release candidates (RTE

[dpdk-dev] [PATCH RFC 06/11] mbuf: replace data pointer by an offset

2014-05-13 Thread Thomas Monjalon
Hi Venky, 2014-05-13 13:54, Venkatesan, Venky: > An alternative way to save 6 bytes (without the side effects this change > has) would be to change the mempool struct * to a uint16_t mempool_id. That > limits the changes to a return function, and the performance impact of that > can be mitigated q

[dpdk-dev] [PATCH v3 2/6] examples: use rte.extsubdir.mk to process subdirectories

2014-05-13 Thread Olivier Matz
Signed-off-by: Olivier Matz --- examples/l2fwd-ivshmem/Makefile | 9 + examples/multi_process/Makefile | 16 +++- examples/multi_process/client_server_mp/Makefile | 15 ++- examples/quota_watermark/Makefile| 12 +++

[dpdk-dev] [PATCH RFC 06/11] mbuf: replace data pointer by an offset

2014-05-13 Thread Olivier MATZ
Hi Stephen, On 05/12/2014 07:13 PM, Stephen Hemminger wrote: > In cloned mbuf > rte_pktmbuf_mtod(m, char *) points to the original data. > RTE_MBUF_TO_BADDR(m) points to buffer in the mbuf which we > use for metadata (timestamp). I still don't see the problem. Let's take an example: m2 is a clone

[dpdk-dev] Heads up: Fedora packaging plans

2014-05-13 Thread Neil Horman
Hey all- This isn't really germaine to dpdk development, but Thomas and Vincent, you expressed interest in my progress regarding packaging of dpdk for Fedora, so I figured I would post here in case others were interested. Please find here: http://people.redhat.com/nhorman/dpdk-1.7.0-0.1.gi

[dpdk-dev] [PATCH RFC 06/11] mbuf: replace data pointer by an offset

2014-05-13 Thread Venkatesan, Venky
An alternative way to save 6 bytes (without the side effects this change has) would be to change the mempool struct * to a uint16_t mempool_id. That limits the changes to a return function, and the performance impact of that can be mitigated quite easily. -Venky -Original Message- Fro

[dpdk-dev] Need help "How to use dpdk on Mellanox MT27520"

2014-05-13 Thread L Nageshwar L
Hi, I am using Mellanox Technologies MT27520 Family card and it is not recognized by DPDK test program. When I run the l2fwd binary, I got the below error. Please guide me how to solve the issue. I am using DPDK-1.6.0r2 version. # ./build/l2fwd -c 3 -n 2 --huge-dir /mnt/huge -m 4096 -b :01:

[dpdk-dev] RSS for double vlan tagged packets

2014-05-13 Thread Richardson, Bruce
I don't think the hardware supports using RSS on packets with a double VLAN tag. Regards, /Bruce > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Surya Nimmagadda > Sent: Tuesday, May 13, 2014 3:17 AM > To: dev at dpdk.org > Subject: Re: [dpdk-dev] RSS for

[dpdk-dev] RSS for double vlan tagged packets

2014-05-13 Thread Surya Nimmagadda
I have also tried by enabling vlan_extended support in port_conf and set rss_hf as all 1s. .hw_vlan_extend = 1 .rss_hf = ~0 Still there is no change? Surya On May 12, 2014, at 12:38 PM, Surya Nimmagadda wrote: > Hi, > > I am using RSS functionality on 82599 with dpdk igb_uio driver. > > I