From: Jose Gavine Cueto <pepedocs@gmail.com>
To: Surya Nimmagadda <nscsekhar@juniper.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Issue while running test/testpmd applications
Date: Mon, 2 Dec 2013 17:14:05 +0800 [thread overview]
Message-ID: <CAJ5bv6E2h+YUO=+JP-ob40w5xbZirg-yLCLKnH3XCX0-eOfAUw@mail.gmail.com> (raw)
In-Reply-To: <6535e2f7ec214f82b9899d4d6534a74d@BN1PR05MB279.namprd05.prod.outlook.com>
Hi,
#2 - It depends on the platform that testpmd is running on. If it ran
directly on top of the hardware then usually you have fixed lcores. For
example, in Linux, you can call "nproc" to check how many cores are
available.
Make sure you have sufficient number of cores and set the core mask
appropriately.
Cheers,
Pepe
On Mon, Dec 2, 2013 at 1:45 PM, Surya Nimmagadda <nscsekhar@juniper.net>wrote:
> Hi,
>
> I am trying to run the test and testpmd applications with dpdk-1.5.0r1,
> using tools/setup.sh
>
> I see two errors in EAL. Can someone please help where I am going wrong.
>
> 1. The test application panics with the following log.
>
> EAL: Master core 0 is ready (tid=b74b5800)
> EAL: Core 7 is ready (tid=733fab40)
> EAL: pthread_setaffinity_np failed
> PANIC in eal_thread_loop():
> cannot set affinity
> 5: [/lib/i386-linux-gnu/libc.so.6(clone+0x5e) [0xb75a901e]]
> 4: [/lib/i386-linux-gnu/libpthread.so.0(+0x6d78) [0xb7671d78]]
> 3: [i686-default-linuxapp-gcc/app/test(eal_thread_loop+0x284) [0x80b9e24]]
> 2: [i686-default-linuxapp-gcc/app/test(__rte_panic+0x5c) [0x804edbb]]
> 1: [i686-default-linuxapp-gcc/app/test(rte_dump_stack+0x1c) [0x80bb92c]]
> EAL: Core 2 is ready (tid=75bffb40)
>
> 2. I cant see lcores other than 0. How can I configure more than 1 lcores?
>
> Option: 11
>
>
> Enter hex bitmask of cores to execute test app on
> Example: to execute app on cores 0 to 7, enter 0xff
> bitmask: 0xff
> Launching app
> EAL: Cannot read numa node link for lcore 0 - using physical package id
> instead
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Skip lcore 1 (not detected)
> EAL: Skip lcore 2 (not detected)
> EAL: Skip lcore 3 (not detected)
> :::::::::::::::::::::::::::::::
> EAL: Skip lcore 63 (not detected)
> EAL: Setting up memory...
> EAL: cannot open /proc/self/numa_maps, consider that all memory is in
> socket_id 0
> EAL: Ask a virtual area of 0x2097152 bytes
>
> Any help is greatly appreciated.
>
> Thanks,
> Surya
>
>
--
To stop learning is like to stop loving.
prev parent reply other threads:[~2013-12-02 9:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 5:45 Surya Nimmagadda
2013-12-02 9:14 ` Jose Gavine Cueto [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='CAJ5bv6E2h+YUO=+JP-ob40w5xbZirg-yLCLKnH3XCX0-eOfAUw@mail.gmail.com' \
--to=pepedocs@gmail.com \
--cc=dev@dpdk.org \
--cc=nscsekhar@juniper.net \
/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).