test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: Kevin Wilson <wkevils@gmail.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] Question regarding to self.core_config in TestSuite_l2fwd.py and in other test modules
Date: Tue, 30 Jan 2018 01:34:42 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62F79D09@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CAGXs5wVsCwsm3CWvxbu4r6vwxDf80Azegp3LamhD5TobaXtRow@mail.gmail.com>

Hi Kevin,
"1S/4C/1T" mean return core list with the first four physical cores on the first socket. Definitely this configuration should be workable on 2S system.
Similarly, "2S/4C/1T" mean return core list with the first physical cores belong to first and second socket.
When developing the test suite, core requirement has been determined. So you do not need to change the configuration.
Suites should check returned core list and alert when cores can't fulfill the requirement.

Thanks,
Marvin

> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Kevin Wilson
> Sent: Monday, January 29, 2018 11:16 PM
> To: dts@dpdk.org
> Subject: [dts] Question regarding to self.core_config in
> TestSuite_l2fwd.py and in other test modules
> 
> Hello,
> I want to clarify one point:
> we have in
> http://dpdk.org/browse/tools/dts/tree/tests/TestSuite_l2fwd.py#n58
> ...
> self.core_config = "1S/4C/1T"
> ...
> 
> We have also some similiar core_config in other DTS tests modules.
> 
> 1S stands for "one socket".
> 
> Is this expected to work also on a machine which has 2 sockets ?  or
> should we change it to
> ...
> self.core_config = "2S/4C/1T"
> ...
> 
> so it will work ?
> 
> Regards,
> IB

      reply	other threads:[~2018-01-30  1:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-29 15:15 Kevin Wilson
2018-01-30  1:34 ` 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=86228AFD5BCD8E4EBFD2B90117B5E81E62F79D09@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=wkevils@gmail.com \
    /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).