All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Oscar Zhao" <oz@quacker.org>
To: dev@dpdk.org
Subject: [dpdk-dev] Feature Discussion: CPU topology detection on FreeBSD
Date: Thu, 28 Jan 2021 04:07:07 +0000	[thread overview]
Message-ID: <f030640f01e2c3dca2cb1bea3e45ae81@quacker.org> (raw)

Hello dpdk devs,

I would like to discuss the feasibility of implementing CPU topology detection on FreeBSD. Currently both eal_cpu_core_id() and eal_cpu_socket_id() in rte_eal library always return 0 on FreeBSD, making NUMA-aware development impossible without resorting to external libraries or system APIs.

The CPU topology information is available via sysct kern.sched.topology_spec. The only issue is that the return value is an XML formatted object (see https://forums.freebsd.org/threads/number-of-cpus-and-cores.41299/). (https://forums.freebsd.org/threads/number-of-cpus-and-cores.41299/) I'm not sure how feasible it is to parse XML inside DPDK.

On a side note, obtaining the physical NUMA node id of a core is easy - sysctl dev.cpu.[cpu#].%domain returns the corresponding node id but I have yet found a straightforward way to detect hyperthreads besides the XML thing.

Oscar

             reply	other threads:[~2021-01-29  9:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  4:07 Oscar Zhao [this message]
2021-01-29 10:05 ` [dpdk-dev] Feature Discussion: CPU topology detection on FreeBSD Bruce Richardson
2021-01-29 12:52   ` Burakov, Anatoly
2021-01-29 13:45     ` Bruce Richardson
2021-01-29 22:24       ` Oscar Zhao
2021-02-10 16:01       ` Burakov, Anatoly

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=f030640f01e2c3dca2cb1bea3e45ae81@quacker.org \
    --to=oz@quacker.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.