From: bugzilla@dpdk.org
To: spp@dpdk.org
Subject: [spp] [Bug 457] rte_mempool_create is based on lcore socketid and not the port socketid
Date: Tue, 21 Apr 2020 09:24:10 +0000 [thread overview]
Message-ID: <bug-457-394-UIWf9ZgbHK@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-457-394@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=457
Hideyuki Yamashita (yamashita.hideyuki@ntt-tx.co.jp) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yamashita.hideyuki@ntt-tx.c
| |o.jp
--- Comment #1 from Hideyuki Yamashita (yamashita.hideyuki@ntt-tx.co.jp) ---
Hello Vipin,
Thanks for your comments.
However I could not understand what is the real problem on the current code.
I mean primary process can be run any lcore id which can be specified in
primary
process startup parameter (with -l option).
With -l option, any lcore id can be specified. In other words, either of NUMA
node
(e.g. numa0 numa1) can be specified.
Original coding (calling rte_socket_id()) is considering above situation.
However your "Expected" codeing specifies "soeket id = 0".
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-04-21 9:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 7:02 bugzilla
2020-04-21 9:24 ` bugzilla [this message]
2020-04-21 11:06 ` bugzilla
2020-04-23 5:04 ` bugzilla
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-457-394-UIWf9ZgbHK@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=spp@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).