Members Attending ------------------------- Aaron Conole Bruce Richardson Hemant Agrawal Jerin Jacob Kevin Traynor Konstantin Ananyev Maxime Coquelin Morten Brørup Stephen Hemminger Thomas Monjalon
NOTE: The technical board meetings are on every second Wednesday at 3pm UTC. Meetings are public, and DPDK community members are welcome to attend. Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes Next meeting will be on Wednesday 2024-Nov-27 @ 3pm UTC, and will be chaired by Hemant Agrawal Agenda Items ============ 1) A DPDK summit in Prague approved. The tentative dates are in May 7th to 8th or 21st to 22nd 2025. 2) Did we write down all ideas from the Montreal brainstorm (public + techboard)? Honnappa has summarized and sent this to Techboard. Action Item: Honnappa to add the list to the slides in Google Docs (https://docs.google.com/presentation/d/1TDmz1_xvWFWxrMtXgKA03e_4yPUUTWdJ7aWV9_BBUhE/edit?usp=sharing) 3) Did we summarize ideas coming from email and Slack? Stephen has summarized these. Action Item: Stephen to add these to the slides mentioned above. Create a excel sheet and send it to Techboard for voting. 4)Next Steps a) Need sizing for these challenges and Mentors b) Govboard has approved $10,000 for coding challenge prize. The coding challenge could happen in conjunction with that. c) Stephen, Ben and possibly Nathan would lead this effort. Once the mentors are decided, mentors will manage the individual coding challenge. The prize money will be decided once the priority is decided. Tentatively - publish 10 challenges and select 3 best. d) Can we send a teaser in advance? 5) PVS Studio has posted a blog on issues found in static analysis, worth look - https://pvs-studio.com/en/blog/posts/cpp/1183/ 6) Status of 24.11 release – RC2 released. Lots of features introduced. so_ring will be merged after this release. Lcore variable feature from Mathias is an interesting feature. One concern is the amount of memory it uses. The memory is not coming from Hugepages. It allocates 128KB per lcore. This is merged but not marked as Experimental this will allow us to make changes even if it breaks ABI. Action Item: Patrick to check if it is possible to add some test cases in CI pipeline to warn changes to memory usage caused by a patch. Action Item: Thomas to mark this feature as Experimental. 7) The documented process for merging is to have at least 2 reviews. However, the reality seems different, things get merged before the release. Thomas and David review the patches during the release process if there were few reviews. We could have list of patches that need review at some location (dpdk.org?).
