From: Peter Chen <peter.feifan.chen@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] testpmd errors
Date: Fri, 14 Jun 2013 13:44:49 -0700 [thread overview]
Message-ID: <CAMGYKAeuw+fMy8hcbXTsYsSSFhr-zdrE5UWZv+jqAFjZE3e4JA@mail.gmail.com> (raw)
In-Reply-To: <CAMGYKAfXaTBLAPU9gZJJr8r5=Rd15Se9v4hNR3OBJ-rkcQB2ew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2621 bytes --]
Hi, it seems the above error is due to the fact I don't have NUMA enabled
even though half of my cores use socket 0 and half of my cores use socket
1. For some reason all the hugepage allocations are on socket 0 (it makes
sense as I don't have NUMA enabled). Also I am unable to use:
sudo ./testpmd -c ff -n 4 -r 2 --socket-mem=1024,1024 command to
allocate memory to socket 1 as it is not part of dpdk usage which is weird
(do I have to have NUMA enabled to use this feature?)
I have two Intel quad-core Xeon 5506. I am not sure how to enable NUMA on
them or if these Intel chips even support them. Does anyone know?
Peter
On Tue, Jun 11, 2013 at 4:23 PM, Peter Chen <peter.feifan.chen@gmail.com>wrote:
> Just a bit more of information, I am using ubuntu 12.04 server.
>
>
> On Tue, Jun 11, 2013 at 3:56 PM, Peter Chen <peter.feifan.chen@gmail.com>wrote:
>
>> Hi All,
>>
>> I am trying to install dpdk. Since it says to run test and testpmd to
>> see if everything works, I ran those apps.
>>
>> So far test works fine for me. However when I run testpmd, I get the
>> following:
>>
>> *probe driver: 8086:10c8 rte_ixgbe_pmd
>> *
>> * unbind kernel driver /sys/bus/pci/devices/0000:04:00.0/driver/unbind
>> *
>> * bind PCI device 0000:04:00.0 to igb_uio driver
>> *
>> * Device bound
>> *
>> * map PCI resource for device 0000:04:00.0
>> *
>> * PCI memory mapped at 0x7f0e680e6000
>> *
>> * rte_memzone_reserve_aligned(): No appropriate segment found
>> *
>> * pci_uio_map_resource(): cannot store uio mmap details
>> *
>> * Error - exiting with code: 1
>> *
>> * No probed ethernet devices - check that CONFIG_RTE_LIBRTE_IGB_PMD
>> =y and that CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file *
>>
>> Below is what I see in dmesg:
>>
>> *igb_uio 0000:04:00.0: irq 79 for MSI/MSI-X
>> *
>> * uio device registered with irq 4f
>>
>> *
>> * *My setup is a dell R510 with two quad-core Xeons (E5506), 32 GB
>> memory. It has 5 NICs of which two are up (eth0: BCM5716 and eth4 Intel
>> 82598EB 10 Gigabit). Both NICs are on the same subnet before I had dpdk
>> attach to eth4 by running the following command:
>>
>> *sudo ./testpmd -c ff -n 4 -r 2 -m 2048 -b 0000:01:00.0*
>>
>> 0000:04:00.0 is the Intel and 0000:01:00.0 is the Broadcom.
>>
>> Originally I was getting the "No probed ethernet devices" because I
>> had a non-supported NIC, however 82598 is a supported NIC and it seems that
>> dpdk did bind to the Intel NIC. However, rte_eth_dev_count() somehow still
>> returns 0. Any help would be great! Thanks!
>>
>> Peter
>>
>
>
[-- Attachment #2: Type: text/html, Size: 3786 bytes --]
prev parent reply other threads:[~2013-06-14 20:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-11 22:56 Peter Chen
2013-06-11 23:23 ` Peter Chen
2013-06-14 20:44 ` Peter Chen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMGYKAeuw+fMy8hcbXTsYsSSFhr-zdrE5UWZv+jqAFjZE3e4JA@mail.gmail.com \
--to=peter.feifan.chen@gmail.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).