DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	"juraj.linkes@pantheon.tech" <juraj.linkes@pantheon.tech>,
	Lijuan Tu <lijuan.tu@intel.com>
Cc: nd <nd@arm.com>
Subject: [dpdk-dev] DTS Workgroup: MoM 05/12/2021
Date: Wed, 19 May 2021 05:02:02 +0000
Message-ID: <DBAPR08MB58142D48157063CD8A624B99982B9@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)

Attendees:
Aaron Conole
Daniel Martin Buckley
Honnappa Nagarahalli
Thomas Monjalon
Lijuan Tu
Juraj Linkes
Lincoln Lavoie
Owen Hilyard

The meeting announcements are sent to dev@dpdk.org.

Minutes:

1) Action items from the meeting held on 4/28
	a) Juraj Linkes - Understand and discuss the patches that DTS applies on DPDK in the next call.
               	app/test-pmd/macfwd.c - a printf statement, can be provided by test-pmd 'show fdwstats' command.
	              fm10K - Might not be used anymore
	              ABI patch is not used in DTS - Documentation needs to be updated.
		Many of the test cases use sed scripts to modify the code. These need to be explored further.

2) Agreed to create two lists of test cases - i) reviewed by DTS working group ii) non-reviewed test cases. This will help in introducing the test cases in stages without having to review the entire list.

3) Agreed to set up the meeting for the next 4 weeks.

4) Action Items
Honnappa - Validate test-pmd to make sure the mac-fwd printf statement output is available in 'show fwd stats'
Lijuan Tu - Check if the fm10K test case is still valid
Juraj Linkes - Explore the code modified using sed commands in various test cases.

5) The work item related discussions are captured in [1]


[1] https://docs.google.com/document/d/1c5S0_mZzFvzZfYkqyORLT2-qNvUb-fBdjA6DGusy4yM/edit?usp=sharing

                 reply	other threads:[~2021-05-19  5:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=DBAPR08MB58142D48157063CD8A624B99982B9@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=juraj.linkes@pantheon.tech \
    --cc=lijuan.tu@intel.com \
    --cc=nd@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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git