DPDK patches and discussions
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 439] memif pmd is allocating from Node 0, even after passing Node 1 in eal args
Date: Sat, 04 Apr 2020 14:11:36 +0000	[thread overview]
Message-ID: <bug-439-3@http.bugs.dpdk.org/> (raw)

https://bugs.dpdk.org/show_bug.cgi?id=439

            Bug ID: 439
           Summary: memif pmd is allocating from Node 0, even after
                    passing Node 1 in eal args
           Product: DPDK
           Version: 20.02
          Hardware: x86
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: High
         Component: ethdev
          Assignee: dev@dpdk.org
          Reporter: vipin.varghese@intel.com
  Target Milestone: ---

CMD: ` rm /tmp/*.sock; ./build/l2fwd
--vdev=net_memif0,socket=/tmp/1.sock,role=master
--vdev=net_memif1,socket=/tmp/2.sock,role=master --no-pci -l 22,66
--socket-mem=0,256 --socket-limit=0,1024  -- -p 1 -T 1`

logs:
`
# numastat -p l2fwd

Per-node process memory usage (in MBs) for PID 65331 (l2fwd)
                           Node 0          Node 1           Total
                  --------------- --------------- ---------------
Huge                      1024.00         1024.00         2048.00
Heap                         0.07            0.05            0.12
Stack                        0.03            0.00            0.03
Private                      3.29            2.93            6.23
----------------  --------------- --------------- ---------------
Total                     1027.39         1026.98         2054.38

`

note: main.c is edited no to fail for promiscuous fail.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2020-04-04 14:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-439-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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).