From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: stable@dpdk.org, dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH 1/2] examples/performance-thread: fix FreeBSD compilation
Date: Thu, 20 Apr 2017 19:33:20 +0200 [thread overview]
Message-ID: <4178086.HJDzW4j0Qm@xps> (raw)
In-Reply-To: <20170420163250.1373-2-bruce.richardson@intel.com>
20/04/2017 18:32, Bruce Richardson:
> This set of sample apps did not compile on FreeBSD due to use of a number
> of Linux/glibc-specific APIs, or APIs which existed in different headers
> on FreeBSD. Specifically, the following APIs has problems:
> * sched_getcpu() is a glibc extension
> * pthread_yield() returns int on Linux, but void on FreeBSD
> * APIs for managing cpu affinity are in pthread_np.h on FreeBSD, rather
> than in pthread.h
> * the type for managing cpu sets is cpuset_t on FreeBSD rather than
> cpu_set_t as on Linux.
It can be fixed by using rte_cpuset_t defined in
lib/librte_eal/common/include/rte_lcore.h
next prev parent reply other threads:[~2017-04-20 17:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 16:32 [dpdk-dev] [PATCH 0/2] fixes for " Bruce Richardson
2017-04-20 16:32 ` [dpdk-dev] [PATCH 1/2] examples/performance-thread: fix " Bruce Richardson
2017-04-20 17:33 ` Thomas Monjalon [this message]
2017-04-20 16:32 ` [dpdk-dev] [PATCH 2/2] net/ark: " Bruce Richardson
2017-04-20 17:23 ` john miller
2017-04-21 13:50 ` [dpdk-dev] [PATCH v2 0/4] Fixes for BSD compilation Bruce Richardson
2017-04-21 13:50 ` [dpdk-dev] [PATCH v2 1/4] net/ark: fix FreeBSD compilation Bruce Richardson
2017-04-21 13:50 ` [dpdk-dev] [PATCH v2 2/4] examples: fix examples_clean build target on FreeBSD Bruce Richardson
2017-04-21 13:50 ` [dpdk-dev] [PATCH v2 3/4] examples/performance-thread: fix FreeBSD compilation Bruce Richardson
2017-04-21 13:50 ` [dpdk-dev] [PATCH v2 4/4] examples/performance-thread: use a single build output dir Bruce Richardson
2017-04-21 14:12 ` [dpdk-dev] [PATCH v2 0/4] Fixes for BSD compilation Thomas Monjalon
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=4178086.HJDzW4j0Qm@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@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).