test suite reviews and discussions
 help / color / mirror / Atom feed
From: Rami Rosen <ramirose@gmail.com>
To: "Tu, Lijuan" <lijuan.tu@intel.com>
Cc: "Yao, BingX Y" <bingx.y.yao@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] tests/pmdrss_hash:change hard code
Date: Fri, 15 Mar 2019 09:30:19 +0200	[thread overview]
Message-ID: <CAHLOa7T_Kyosfbqbt--oqP-QBCREhxUkUfs8ETF2dU0OPsiz8A@mail.gmail.com> (raw)
In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0BA432C6@SHSMSX101.ccr.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]

> -        self.dut.send_expect("./%s/app/testpmd -c f -n 4 -- -i" %
self.target,
> "testpmd> ", 120)
> +        self.dut.send_expect("./%s/app/testpmd -c %s -n 4 -- -i" %
> + (self.target, self.coremask), "testpmd> ", 120)

[Lijuan] Do you forget to change hardcode of memory channel?
>          out = self.dut.send_expect("create bonded device 3 0", "testpmd>
", 30)
>          bond_device_id = int(re.search("port \d+", out).group().split("
")[-1].strip())

Hi all,

Good point.
Actually, the number of channels is a non mandatory EAL parameter, and in
DTS it defaults to 1.
http://git.dpdk.org/tools/dts/tree/framework/dut.py#n565

In this module, the other invocations of testpmd were indeed with
get_memory_channels().
In this occurrence it is hardcoded to 4.

The number of memory channels is merely an optimization, as you can see in
the following thread:
https://dev.dpdk.narkive.com/78gtSXha/dpdk-dev-patch-eal-default-to-one-memory-channel-if-not-specified

According to it,
...
Obtaining the correct value of memory channels, especially from a
running system, can be anything from difficult to plain impossible.
...

Not sure what was the reason for hard coding it to 4 in this test case, but
anyhow on this occasion maybe it is better to replace it with
get_memory_channels() as with the rest of the module, for the sake of
consistency.

Regards,
Rami Rosen





>
>

[-- Attachment #2: Type: text/html, Size: 3898 bytes --]

      reply	other threads:[~2019-03-15  7:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12  5:10 yaobing
2019-03-12  9:05 ` Zhu, WenhuiX
2019-03-14  5:34   ` Rami Rosen
2019-03-15  6:13 ` Tu, Lijuan
2019-03-15  7:30   ` Rami Rosen [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=CAHLOa7T_Kyosfbqbt--oqP-QBCREhxUkUfs8ETF2dU0OPsiz8A@mail.gmail.com \
    --to=ramirose@gmail.com \
    --cc=bingx.y.yao@intel.com \
    --cc=dts@dpdk.org \
    --cc=lijuan.tu@intel.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).