DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nicholas Pratte <npratte@iol.unh.edu>
To: Luca Vizzarro <luca.vizzarro@arm.com>
Cc: dev@dpdk.org, "Jeremy Spewock" <jspewock@iol.unh.edu>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
	"Honnappa Nagarahalli" <honnappa.nagarahalli@arm.com>,
	"Paul Szczepanek" <paul.szczepanek@arm.com>
Subject: Re: [PATCH] dts: add l2fwd test suite
Date: Mon, 9 Sep 2024 13:54:24 -0400	[thread overview]
Message-ID: <CAKXZ7ej7fMjw=b0fuSv7mTA4M9A6kqbi8Avngfh1-JDukYfNEA@mail.gmail.com> (raw)
In-Reply-To: <20240806125140.2582859-1-luca.vizzarro@arm.com>

Just a few clarifying questions below. Otherwise,

(Test cases was run on Connect_x5 and Broadcom P225p devices).

Reviewed-by: Nicholas Pratte <npratte@iol.unh.edu>
Tested-by: Nicholas Pratte <npratte@iol.unh.edu>

<snip>
> +
> +        with TestPmdShell(
> +            self.sut_node,
> +            lcore_filter_specifier=LogicalCoreCount(cores_per_socket=4),
> +            forward_mode=SimpleForwardingModes.mac,
> +            eth_peer=[EthPeer(1, self.tg_node.ports[1].mac_address)],
> +            disable_device_start=True,

Would you be able to elaborate on the explicit lcore definition and
the eth_peer defined in the testpmd parameters above? I tried doing
some digging to understand the existence of these parameters, but
couldn't find anything insightful. Were these parameters basically
just copied over from old DTS?

  parent reply	other threads:[~2024-09-09 17:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-06 12:51 Luca Vizzarro
2024-08-09 15:27 ` Jeremy Spewock
2024-09-09 10:44   ` Luca Vizzarro
2024-09-04 18:11 ` Dean Marx
2024-09-09 15:05 ` Patrick Robb
2024-09-09 17:54 ` Nicholas Pratte [this message]
2024-10-30 15:03 ` [PATCH v2] " Thomas Wilks
2024-11-08 17:01 ` [PATCH v3 0/3] " Luca Vizzarro
2024-11-08 17:01   ` [PATCH v3 1/3] dts: fix adjust L2/L3 addresses behavior Luca Vizzarro
2024-11-08 17:01   ` [PATCH v3 2/3] dts: allow to get multiple expected packets Luca Vizzarro
2024-11-08 17:01   ` [PATCH v3 3/3] dts: add l2fwd test suite Luca Vizzarro

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='CAKXZ7ej7fMjw=b0fuSv7mTA4M9A6kqbi8Avngfh1-JDukYfNEA@mail.gmail.com' \
    --to=npratte@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=jspewock@iol.unh.edu \
    --cc=juraj.linkes@pantheon.tech \
    --cc=luca.vizzarro@arm.com \
    --cc=paul.szczepanek@arm.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).