DPDK patches and discussions
 help / color / mirror / Atom feed
From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "techboard@dpdk.org" <techboard@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>, nd <nd@arm.com>
Subject: [dpdk-dev] Techboard Minutes of Meeting - 10/8/2020
Date: Thu, 8 Oct 2020 23:37:50 +0000	[thread overview]
Message-ID: <DBAPR08MB5814A768A09120774187B429980B0@DBAPR08MB5814.eurprd08.prod.outlook.com> (raw)

Members Attending:
---------------------------

     Bruce Richardson
     Ferruh Yigit
     Honnappa Nagarahalli (Chair)
     Jerin Jacob
     Kevin Traynor
     Konstantin Ananyev
     Maxime Coquelin
     Olivier Matz
     Stephen Hemminger
     Thomas Monjalon

The technical board meetings takes place every second Wednesday on https://meet.jit.si/DPDK, at 3pm UTC.
(Trial runs on jitsi, backup on IRC channel #dpdk-board) Meetings are public and DPDK community members are welcome to attend.

Next meeting will be on 2020-10-21, and will be chaired by Jerin.

Minutes:
-----------

#1 ABI and API breaks in 20.11 - Pending requests to Techboard?
    a) stats per queues in common stats
	- Use xstats as the alternative
	- Techboard decided to remove (deprecation notice in 20.11 and removed in 21.11) the queue stats from common stats (array at the end of the structure)
		-  Suggestion to do a POC to ensure there are no other dependencies
		- AI: Ferruh: Communicate to the mailing list and send the deprecation email. Add documentation to indicate that the array size is limited to 256
	- Telemetry needs to be updated using xstats only
	- AI: Thomas: Improve xstats documentation and fix the underscore typo

    b) pmdinfogen rewrite in Python
	- Creates a dependency for build on latest version of Python
	- CI needs to be updated to use the Python package
	- AI: Maxime to check the dependencies for RedHat

    c) minimum meson version
	- Latest version of meson, 0.55, is not packaged with distros
	- AI: Bruce to work with patch owner to check if an older version of meson can be used to implement these new features
	- REL packages 0.49.2 version of meson.

    d) LPM
	- Looks like other projects are using the LPM structure members, not just APIs.
	- AI: Honnappa: will take a closer look.

#2 Asks from Governing Board
    a) Ask from Trishan for Governing board call on 2021 priorities. What Technical board want to achieve in 2021?
        * Inspiration and actionable goals that are on the roadmap
        * API/ABI support plans, new capabilities, CI testing integration, gaps that the Techboard would like address etc...
	- DTS
	- Documentation
	- ABI work to continue - increase the ABI stability for CryptoDev APIs
	- Reduce barriers to adopt DPDK
		- DPDK Interaction with Kernel
		- Make it easier to pass arguments to DPDK initialization
	- Using DPDK in containers

    b) Review of Technical Section of DPDK "Golden Deck".  https://docs.google.com/presentation/d/1xD5R_WN8xMjEFcb6nBarHWNMRI5nrE0g-poKqc0M0HA/edit#slide=id.g9118ec1251_0_0

#3 Do we need a reviewer role in the process?
      Techboard members to discuss this on email.
      AI: Honnappa will initiate an email to Techboard.

#4 Call for reviews - ethdev and testpmd patches need review

#5 Next governing board meeting is the last meeting for Bruce to represent the tech board. It is Ferruh's turn next.

Agenda items not discussed:

#1 Update on DTS usability
    a) UNH has started the document

#2 Security process issues
    a) Ferruh/Stephen: Anything to discuss?

#3 DMARC mitigation in the mailing list

#4 Prepare the CFP text for a virtual Asia event in January 2021


Thank you,
Honnappa

             reply	other threads:[~2020-10-08 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 23:37 Honnappa Nagarahalli [this message]
2020-10-09 16:30 ` Stephen Hemminger

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=DBAPR08MB5814A768A09120774187B429980B0@DBAPR08MB5814.eurprd08.prod.outlook.com \
    --to=honnappa.nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    --cc=techboard@dpdk.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).