From: "Gao, DaxueX" <daxuex.gao@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: David Marchand <david.marchand@redhat.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: RE: [PATCH] eal/freebsd: fix use of newer CPU_* macros
Date: Tue, 24 May 2022 06:50:35 +0000 [thread overview]
Message-ID: <MW4PR11MB5799F17F2E9DF0F4BDE8E3CA9DD79@MW4PR11MB5799.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220520181050.55654-1-bruce.richardson@intel.com>
> -----Original Message-----
> From: Bruce Richardson <bruce.richardson@intel.com>
> Sent: 2022年5月21日 2:11
> To: dev@dpdk.org
> Cc: David Marchand <david.marchand@redhat.com>; stable@dpdk.org;
> Richardson, Bruce <bruce.richardson@intel.com>
> Subject: [PATCH] eal/freebsd: fix use of newer CPU_* macros
>
> From: David Marchand <david.marchand@redhat.com>
>
> FreeBSD has updated its CPU macros to align more with the definitions used on
> Linux[1]. Unfortunately, while this makes compatibility better in future, it means
> we need to have both legacy and newer definition support. Use a meson check
> to determine which set of macros are used.
>
> [1]
> https://cgit.freebsd.org/src/commit/?id=e2650af157bc7489deaf2c9054995f0f8
> 8a6e5da
>
> Fixes: c3568ea37670 ("eal: restrict control threads to startup CPU affinity")
> Fixes: b6be16acfeb1 ("eal: fix control thread affinity with --lcores") Bugzilla ID:
> 1014
> CC: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
Tested-by: Daxue Gao <daxuex.gao@intel.com>
next prev parent reply other threads:[~2022-05-24 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 18:10 Bruce Richardson
2022-05-24 6:50 ` Gao, DaxueX [this message]
2022-05-24 10:37 ` David Marchand
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=MW4PR11MB5799F17F2E9DF0F4BDE8E3CA9DD79@MW4PR11MB5799.namprd11.prod.outlook.com \
--to=daxuex.gao@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.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).