DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "dev@dpdk.org" <dev@dpdk.org>, "techboard@dpdk.org" <techboard@dpdk.org>
Subject: [dpdk-dev] Minutes of Technical Board Meeting, 2019-10-23
Date: Thu, 7 Nov 2019 04:37:32 +0000	[thread overview]
Message-ID: <VI1PR0401MB2541804BC420C003567A85C889780@VI1PR0401MB2541.eurprd04.prod.outlook.com> (raw)

Members Attending
-----------------
Bruce
Ferruh
Hemant (chair)
Honnapa
Jerin
Kevin
Konstantin
Maxime
Olivier
Stephen
Thomas

NOTE: The technical board meetings every second Wednesday on IRC  channel  #dpdk-board, at 3pm UTC. Meetings are public and DPDK community members  are welcome to attend.
 
NOTE: Next meeting will be on Wednesday 2019-11-06 @3pm UTC, and will be chaired by Jerin


1. SPDX Discussions
 	Hemant and Stephen provided an update on the gaps to be closed for achieving
 	use of SPDX tags alone (i.e. no license text in files) in 19.11. 
 	Key gaps:
 
 	* Issue identified with pmdinfogen using GPL derived code, meaning
 	  it needs a license exception. Stephen to follow with GB to get exception
	 approval. 
 
	* Few drivers, test files are still having old licensing style.
	  Patches have been created, but we are still waiting for original
                 authors to ack them. 

	* In the worst, we will apply top SPDK tag while leaving the original
	   License text in the file intact for the remaining files.

2. MIT license for Windows.
	- The code has been re-submitted as BSD-3 (or MIT+BSD-3), we will check the legal team for any concerns. 
              -  TB will check for global exception for dual licensing. 

3. Removal of examples (standing agenda item):
	All the removed examples should be mentioned in Release notes.
	Bruce's patchset (5 examples) was agreed.  
	Jin Yu also submitted a patch to remove vhost_scsi example.

4. KNI IOVA as VA support
KNI supposes that mbufs are contiguous in kernel virtual memory. This may not be true when using the IOVA=VA mode.

 -  check original context at http://mails.dpdk.org/archives/dev/2019-October/148339.html
  - It is not wise to break KNI - as customers are using it in production.
  - choice to enable it optionally with EAL FLAG is not acceptable to Jerin. 
  - Olivier's new mempool patch series for " mempool: avoid objects allocations across pages" will help here. 

The decision is to accelerate the review of this mempool patch series and make it part of 19.11 itself to resolve this issue. 

5. VFIO - PF Kernel module
 - enabling SRIOV of VFIO PF device. 
- some members raised concerns for supporting out of tree kernel modules (especially related to VM) as it creates lots of long term support nightmare.
- for this particular module, kernel.org is not in favour on integrating these changes as this may cause security issue with netdev
- mcoquelin and shemminger to review it further and discuss this topic again in next meeting.7



                 reply	other threads:[~2019-11-07  4:37 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=VI1PR0401MB2541804BC420C003567A85C889780@VI1PR0401MB2541.eurprd04.prod.outlook.com \
    --to=hemant.agrawal@nxp.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).