From: "Liu, Yong" <yong.liu@intel.com>
To: Jianbo Liu <jianbo.liu@linaro.org>
Cc: "dts@dpdk.org" <dts@dpdk.org>,
"herbert.guan@arm.com" <herbert.guan@arm.com>
Subject: Re: [dts] [PATCH] tests/kni: fix failures for kni
Date: Fri, 18 Aug 2017 08:55:27 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62E55BE9@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CAP4Qi3-GoZimPa0Rri6iJtj9+t5X747ygPEZtHS_GQTaPD6KfQ@mail.gmail.com>
Hi Jianbo,
> -----Original Message-----
> From: Jianbo Liu [mailto:jianbo.liu@linaro.org]
> Sent: Friday, August 18, 2017 9:56 AM
> To: Liu, Yong <yong.liu@intel.com>
> Cc: dts@dpdk.org; herbert.guan@arm.com
> Subject: Re: [dts] [PATCH] tests/kni: fix failures for kni
>
> Hi Marvin,
>
> On 17 August 2017 at 20:40, Liu, Yong <yong.liu@intel.com> wrote:
> > Hi Jianbo,
> > Is there any particular reason for not chose hyper-threading cores?
> > There're some performance cases are depending on hyper-threading cores.
> > If hyper-threading is not enabled on the platform, those cases won't be
> able to run.
> > Could you please clear the reason?
> >
>
> I think my patch only changed the function testing cases, not performance
> ones.
> Besides, there is no hyper-threading for the arm64 server.
>
There're still some cases which required for hyper-threading cores remaining in DTS.
I'm looking up for one method to handle those cases. Anyway, thanks a lot and patch merged.
> Thanks!
> Jianbo
>
> > Thanks,
> > Marvin
> >
prev parent reply other threads:[~2017-08-18 8:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 5:22 Jianbo Liu
2017-08-17 12:40 ` Liu, Yong
2017-08-18 1:55 ` Jianbo Liu
2017-08-18 8:55 ` Liu, Yong [this message]
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=86228AFD5BCD8E4EBFD2B90117B5E81E62E55BE9@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=herbert.guan@arm.com \
--cc=jianbo.liu@linaro.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).