DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2021-Oct-20
Date: Mon, 25 Oct 2021 14:32:13 +0000	[thread overview]
Message-ID: <DM6PR11MB4491F6503478EDC870AE7D479A839@DM6PR11MB4491.namprd11.prod.outlook.com> (raw)


Minutes of Technical Board Meeting, 2021-Oct-20

Members Attending
-----------------
-Bruce
-Ferruh
-Hemant
-Honnappa
-Jerin
-Kevin
-Konstantin (Chair)
-Maxime
-Stephen
-Thomas

NOTE: The technical board meetings every second Wednesday at
https://meet.jit.si/DPDK at 3 pm UTC.
Meetings are public, and DPDK community members are welcome to attend.

NOTE: Next meeting will be on Wednesday 2021-Oct-27 @3pm UTC, and will
be chaired by Maxime.

1) DTS proposal discussion [1]
  TB agreed on following roadmap for DTS:
   a) DTS adoption:
       -  DTS framework will be merged to DPDK repository
       -  existing DTS test-cases will be uploaded to DPDK repo on step by step basis
          (submit a patch to dpdk.org, review, accept).
       - All communication regarding new DTS framework will go through dev@dpdk.org
         mailing list and will follow usual DPDK policies. 
       - existing DTS repository and mailing list will remain available for legacy purposes.
         
       Concern was expressed regarding that due to companies internal policies,
       DTS code adopted to DPDK will be matter of extra scanning (legacy, security, etc.). 
       Need to figure out what are exact requirements for this scanning (AR to John Mcnamara).
       
   b) Patch submission changes:
     When new feature is added to DPDK a test-case(s) have to be provided along with it
     (either with DPDK UT, or DPDK DTS frameworks). 
     When new DTS test-case is required:  
     - Same patch series will contain patches for both DPDK and DTS.
     - DTS patches will follow DPDK patches review/accept policy.

    c) Patch backporting changes:
      - DTS patches will follow DPDK backporting policy
      - Any backporting of the DPDK patches should also backport the DTS changes (if there are any).

2) DTS framework adoption timeframe and resources
  -  There are few people working on it half of their time, but more help is needed.
      2-3 extra people working 50% of their time on that task would be ideal.  
  -   First DTS related patches are expected in 22.02 timeframe.
  -   22.11 as preliminary target for DTS framework adoption

3) DTS framework maintainer
   - Need to talk with current DTS maintainer -
     is Lijuan ok to also maintain DTS framework within DPDK (AR to Honnappa)
   - Would be good to have at least one more maintainer for DTS
      (better coverage/split load, etc.).

4) GPU library / DWA library inclusion
  http://inbox.dpdk.org/dev/DM6PR12MB41079FAE6B5DA35102B1BBFACDB79@DM6PR12MB4107.namprd12.prod.outlook.com/
  http://mails.dpdk.org/archives/dev/2021-October/226070.html  

  Separate TB meeting is scheduled to cover that topic.
  Date: Wednesday, October 27th
  Time: 3pm UTC
   https://meet.jit.si/DPDK
   Backup On IRC libera.chat #dpdk-board

[1]
https://docs.google.com/presentation/d/1gTMJGP40FlWoSxMwdZsE2ydmd5SrMvGfWA9wtqvdbbM/edit?usp=sharing



             reply	other threads:[~2021-10-25 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-25 14:32 Ananyev, Konstantin [this message]
2021-10-26 21:48 ` Ananyev, Konstantin

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=DM6PR11MB4491F6503478EDC870AE7D479A839@DM6PR11MB4491.namprd11.prod.outlook.com \
    --to=konstantin.ananyev@intel.com \
    --cc=dev@dpdk.org \
    --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).