From: "Li, Xiaoyun" <xiaoyun.li@intel.com>
To: Aaron Conole <aconole@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 4/4] examples/ntb: support more functions for NTB
Date: Fri, 6 Sep 2019 01:19:56 +0000 [thread overview]
Message-ID: <B9E724F4CB7543449049E7AE7669D82F0B2D4FDE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <f7tsgpa978x.fsf@dhcp-25.97.bos.redhat.com>
Sure. Thanks for reminding. Will fix it in v2.
> -----Original Message-----
> From: Aaron Conole [mailto:aconole@redhat.com]
> Sent: Thursday, September 5, 2019 21:57
> To: Li, Xiaoyun <xiaoyun.li@intel.com>
> Cc: dev@dpdk.org
> Subject: re: [dpdk-dev] [PATCH 4/4] examples/ntb: support more functions for
> NTB
>
>
> Hi Xiaoyun,
>
> Xiaoyun Li writes:
>
> > Support to transmit files between two systems.
> > Support iofwd between one ethdev and NTB device.
> > Support rxonly and txonly for NTB device.
> > Support to set forwarding mode as file-trans, txonly, rxonly or iofwd.
> > Support to show/clear port stats and throughput.
> >
> > Signed-off-by: Xiaoyun Li <xiaoyun.li at intel.com>
> > ---
>
> ...
>
> > + static uint64_t prev_cycles[2];
> > +
> > + diff_cycles = prev_cycles[port];
> > + prev_cycles[port] = rte_rdtsc();
> > + if (diff_cycles > 0)
>
> This (and a few other places) causes error on aarch64 platform.
>
> Can you either restrict this example to x86 only, or rework it to use some other
> interface?
>
> See:
>
> https://travis-ci.com/ovsrobot/dpdk/jobs/231342972
>
> for more information.
next prev parent reply other threads:[~2019-09-06 1:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 13:56 Aaron Conole
2019-09-06 1:19 ` Li, Xiaoyun [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-05 5:39 [dpdk-dev] [PATCH 0/4] enable FIFO " Xiaoyun Li
2019-09-05 5:39 ` [dpdk-dev] [PATCH 4/4] examples/ntb: support more functions " Xiaoyun Li
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=B9E724F4CB7543449049E7AE7669D82F0B2D4FDE@SHSMSX101.ccr.corp.intel.com \
--to=xiaoyun.li@intel.com \
--cc=aconole@redhat.com \
--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 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).