DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Piotr Kubaj <pkubaj@anongoth.pl>
Cc: dev@dpdk.org, David Christensen <drc@linux.vnet.ibm.com>
Subject: Re: [dpdk-dev] [PATCH] ppc64le: fix build without glibc and using Clang
Date: Wed, 19 May 2021 11:59:35 +0200	[thread overview]
Message-ID: <3175316.hIkBcZur5t@thomas> (raw)
In-Reply-To: <YKThADLi0sDAdBHO@KGPE-D16>

19/05/2021 11:57, Piotr Kubaj:
> Well, isn't FreeBSD already supported?
> 
> Even https://www.dpdk.org/ mentions supporting FreeBSD.

Yes it is supposed to be supported.
But why are you adding all this code for PPC?
It doesn't seem to be all related to clang only.

PS: please do not top-post.


> On 21-05-19 09:53:16, Thomas Monjalon wrote:
> > 18/05/2021 22:42, David Christensen:
> > > On 5/16/21 5:46 PM, Piotr Kubaj wrote:
> > > > __ppc_get_timebase() is only present when glibc is used.
> > > > 
> > > > Signed-off-by: Piotr Kubaj <pkubaj@FreeBSD.org>
> > > > ---
> > > >   lib/eal/ppc/include/rte_altivec.h |  3 +++
> > > >   lib/eal/ppc/include/rte_cycles.h  | 12 ++++++++++++
> > > >   lib/eal/ppc/rte_cycles.c          | 16 ++++++++++++++++
> > > >   3 files changed, 31 insertions(+)
> > > 
> > > Reviewed-by: David Christensen <drc@linux.vnet.ibm.com>
> > 
> > This patch does a lot more than what is described.
> > It seems adding support for FreeBSD.
> > For testing OS, please use #ifdef RTE_EXEC_ENV_*





  reply	other threads:[~2021-05-19  9:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  0:46 Piotr Kubaj
2021-05-18 20:42 ` David Christensen
2021-05-19  7:53   ` Thomas Monjalon
2021-05-19  9:57     ` Piotr Kubaj
2021-05-19  9:59       ` Thomas Monjalon [this message]
2021-05-19 12:07         ` Piotr Kubaj

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=3175316.hIkBcZur5t@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=drc@linux.vnet.ibm.com \
    --cc=pkubaj@anongoth.pl \
    /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).