From: Dheeraj Dang <dheerajdang138@gmail.com>
To: Changchun Zhang <changchun.zhang@oracle.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Invalid NUMA socket when running helloworld on VM linux
Date: Sun, 3 Mar 2019 15:27:50 +0530 [thread overview]
Message-ID: <CAJyVW49T6NGVg7UFfbaWCFcJyK1Tm5oNLnA-uiGyCGVQBeCWxg@mail.gmail.com> (raw)
In-Reply-To: <fce56772-28bd-4672-8dad-1289f8462c2e@default>
Hi Changchun,
You can set numa_node using this command
*echo 0 > /sys/devices/pci0000\:00/<pci_id>/numa_node (if numa node is 0)*
*echo 1 > /sys/devices/pci0000\:00/<pci_id>/numa_node *
*(if numa node is 1)*
In logs, you are seeing its invalid value i.e -1.
Regards
Dheeraj Dang
On Sun, Mar 3, 2019 at 4:22 AM Changchun Zhang <changchun.zhang@oracle.com>
wrote:
>
>
> Hi Gurus,
>
>
>
> I launched a virtual box based linux on my windows, and my PC is thinkpad
> T480.
>
> After configured the huge pages as number of 2MBs and the cpu number as 4
> on the vm linux, I build DPDK and run the example of hellowworld but get
> the below output, in which I saw the "invalid NUMA socket". What does it
> mean and does it matter, as I see the hello from core # is also printed.
>
>
>
> [~ build]$ sudo ./helloworld
>
> EAL: Detected 4 lcore(s)
>
> EAL: Detected 1 NUMA nodes
>
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
>
> EAL: Probing VFIO support...
>
> EAL: PCI device 0000:00:03.0 on NUMA socket -1
>
> EAL: Invalid NUMA socket, default to 0
>
> EAL: probe driver: 8086:100e net_e1000_em
>
> hello from core 1
>
> hello from core 2
>
> hello from core 3
>
> hello from core 0
>
next prev parent reply other threads:[~2019-03-03 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 22:51 Changchun Zhang
2019-03-03 9:57 ` Dheeraj Dang [this message]
2019-03-04 19:32 ` Changchun Zhang
2019-03-05 6:35 ` Dheeraj Dang
2019-03-05 16:42 ` Changchun Zhang
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=CAJyVW49T6NGVg7UFfbaWCFcJyK1Tm5oNLnA-uiGyCGVQBeCWxg@mail.gmail.com \
--to=dheerajdang138@gmail.com \
--cc=changchun.zhang@oracle.com \
--cc=users@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).