Hi Dan,
When we tried, perf did not work in ESX, it only works in KVM. oprofile
works in timer mode in ESX.
Thanks,
Selvaganapathy.C.
On Fri, Feb 28, 2014 at 6:07 PM, Daniel Kan wrote:
> Hi,
> I'm wondering which profilers are best for profiling DPDK applications
> running on VM: perf, oprofi
Hello all,
I'm a computer engineering student, and as part of my thesis... I would
like to use Intel DPDK for packet generation. I'm completely new to this
one and I only have a little knowledge on hardware programming. So could
anyone help me to find the resources required to start coding using I
Thanks for the tip. Maybe it?s better to optimize code on bare metal before
moving to VM.
Dan
On Feb 28, 2014, at 6:12 PM, Selvaganapathy Chidambaram wrote:
> Hi Dan,
>
> When we tried, perf did not work in ESX, it only works in KVM. oprofile works
> in timer mode in ESX.
>
> Thanks,
> Se
Hi,
I?m wondering which profilers are best for profiling DPDK applications running
on VM: perf, oprofile, vtune? The first 2 are open sourced while vtune is
commercial. DPDK apps are running on ubuntu 12.04 and centos 6.5. Thanks.
Dan
Hello Mats,
I reproduced the problem (and another one).
I will send two patches in a few minutes, can you try them ?
Thank you.
--
David Marchand
On Thu, Feb 27, 2014 at 3:08 PM, Mats Liljegren
wrote:
> I run a 64-bit host building for 32-bit DPDK, which fails with:
>
> dpdk/i686-default-li
Build issue reported by Mats Liljegren :
CC eal.o
In file included from
/home/lwrt/build/dpdk/lib/librte_eal/linuxapp/eal/eal.c:55:0:
/home/lwrt/build/dpdk/lib/librte_eal/linuxapp/eal/eal.c: In function
?eal_parse_base_virtaddr?:
/home/lwrt/build/dpdk/i686-default-linuxapp-gcc/include/rte_common
Rebase commit 57c24af85d9eaa81549a212169605b4e2468a29f introduced a build
regression for 32bits system.
CC eal_memory.o
/home/marchand/dpdk.org/lib/librte_eal/linuxapp/eal/eal_memory.c: In function
?rte_mem_virt2phy?:
/home/marchand/dpdk.org/lib/librte_eal/linuxapp/eal/eal_memory.c:140:12: error
On Fri, Feb 28, 2014 at 9:11 AM, David Marchand
wrote:
> Hello Mats,
>
> I reproduced the problem (and another one).
> I will send two patches in a few minutes, can you try them ?
>
>
> Thank you.
Yes, I can do that.
Best regards
Mats Liljegren
On 02/28/2014 09:47 AM, Mats Liljegren wrote:
> On Fri, Feb 28, 2014 at 9:11 AM, David Marchand
> wrote:
>> Hello Mats,
>>
>> I reproduced the problem (and another one).
>> I will send two patches in a few minutes, can you try them ?
>>
>>
>> Thank you.
>
> Yes, I can do that.
>
> Best regards
> M
The main goal of the following commits is to be able to load a PMD
virtual device driver as a shared library (DPDK extension). Today it is
already possible to load an external PMD PCI driver (ex: memnic,
virtio-net-pmd, ...), but the DPDK framework does not allow to load a
virtual device driver in
To fully support dpdk extensions (loading of .so), all symbols provided
by dpdk libraries must be available in the binaries: before this patch,
unused functions/variables from dpdk static libraries could be stripped
by the linker because they are not used. These symbols can be used by a
dpdk extens
This commit introduces a new API for storing device arguments given by
the user. It only adds the framework and the test. The modification of
EAL to use this new module is done in next commit.
The final goals:
- unify pci-blacklist, pci-whitelist, and virtual devices arguments
in one file
- all
This is useful for debug purposes. Example:
echo 100 >
/sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages
echo 100 >
/sys/devices/system/node/node1/hugepages/hugepages-2048kB/nr_hugepages
./app/test -c 0x15 -n 3 -m 64 \
--use-dev="eth_ring0" --use-device="eth_ring1" --use-d
Remove old whitelist code:
- remove references to rte_pmd_ring, rte_pmd_pcap and pmd_xenvirt in
is_valid_wl_entry() as we want to be able to register external virtual
drivers as a shared library. Moreover this code was duplicated with
dev_types[] from eal_common_pci.c
- eal_common_whitelist.c
To avoid confusion with virtual devices, rename device_list as
pci_device_list and driver_list as pci_driver_list.
Signed-off-by: Olivier Matz
---
app/test/test_pci.c | 2 +-
lib/librte_eal/common/eal_common_pci.c| 14 +++---
lib/librte_eal/common/include/rte_p
The name "nonpci" for virtual devices is ambiguous. A physical device
can be non-PCI (ex: usb, sata, ...). This file only deal with virtual
devices so rename it to avoid confusion.
Signed-off-by: Olivier Matz
---
lib/librte_eal/common/Makefile | 2 +-
lib/librte_eal/common/eal_
Instead of having a list of virtual device drivers in EAL code, add an
API to register drivers. Thanks to this change:
- we don't need to reference pmd_ring, pmd_pcap and pmd_xenvirt in EAL code
- it is now possible to provide a virtual device driver as a shared
library.
The registration is done
This commit changes the API of --use-device. It changes the separator
used between each key/value pairs from ';' to ','. Indeed, ';' was not
the best choice as this character is also used to separate shell
commands, forcing the user to surround arguments with quotes.
Signed-off-by: Olivier Matz
-
This commit splits the "--use-device" option in two new options:
- "--pci-whitelist or -w": add a PCI device in the white list
- "--vdev": instanciate a new virtual device
Before the patch, the same option "--use-device" was used for these 2
use-cases.
By the way, we also add "--pci-blacklist" i
Some PCI drivers may require some specific initialization arguments at
start-up.
Even if unused today, adding this feature seems coherent with virtual
devices in order to provide a full-featured rte_devargs framework. In
the future, it could be added in pmd_ixgbe or pmd_igb for instance to
enable
Copy all the dump commands provided in app/test into app/testpmd. These
commands are useful to debug a problem when using testpmd.
Signed-off-by: Olivier Matz
---
app/test-pmd/cmdline.c | 114 +
1 file changed, 114 insertions(+)
diff --git a/app/t
On Fri, 28 Feb 2014 18:25:41 +0100
Olivier Matz wrote:
> switch (devargs->type) {
> + case RTE_DEVTYPE_WHITELISTED_PCI:
> + case RTE_DEVTYPE_BLACKLISTED_PCI:
> + /* try to parse pci identifier */
> + if (eal_parse_pci_BDF(buf,
22 matches
Mail list logo
