DPDK patches and discussions
 help / color / mirror / Atom feed
From: Zhou congjie <zcjie0802@qq.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>, "anatoly.burakov" <anatoly.burakov@intel.com>
Subject: Re: [PATCH v2] eal/linux: fix fbarray name with multiple secondaryprocesses
Date: Sat, 16 Nov 2024 10:16:47 +0800	[thread overview]
Message-ID: <tencent_A9AD717234F532679AE5A40672514B737309@qq.com> (raw)
In-Reply-To: <20241115120920.6ae82b8e@hermes.local>

On Fri, 15 Nov 2024, Stephen Hemminger wrote:

> Need to include <rte_cycles.h> to get the prototype rte_get_tsc_cycles()

When I compile locally (on x86), it compiles successfully whether or not 
<rte_cycles.h> is included. 

However, cloud testing indicates that compilation fails on other 
architectures when <rte_cycles.h> is not included.
 
Is <rte_cycles.h> the cause of the compilation failure? 
If so, I'm curious why this is the case.


  reply	other threads:[~2024-11-16  2:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-14  8:37 [PATCH] eal/linux: redefine the name for rte_fbarray_init() Congjie Zhou
2024-11-14 16:24 ` Stephen Hemminger
2024-11-14 17:06   ` Stephen Hemminger
2024-11-15  2:26     ` Zhou congjie
2024-11-15  5:32       ` Stephen Hemminger
2024-11-15  1:57   ` Zhou congjie
2024-11-15  2:00   ` Zhou congjie
2024-11-15  7:50 ` [PATCH v2] eal/linux: fix fbarray name with multiple secondary processes Congjie Zhou
2024-11-15 16:38   ` Stephen Hemminger
2024-11-15 20:09   ` Stephen Hemminger
2024-11-16  2:16     ` Zhou congjie [this message]
2024-11-16  2:53     ` [PATCH v2] eal/linux: fix fbarray name with multiple secondaryprocesses Zhou congjie
2024-11-16  4:07 ` [PATCH v3] eal/linux: fix fbarray name with multiple secondary processes Congjie Zhou

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=tencent_A9AD717234F532679AE5A40672514B737309@qq.com \
    --to=zcjie0802@qq.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).