Hi Honnappa, Since we didn't sync this morning at DTS meeting, I wanted to share the current proposed 24.07 roadmap with you. I think we can asynchronously look it over and approve it. Or, if you want to discuss more in depth, maybe the DPDK CI meeting next week is an appropriate venue. 1) Write ethdev testsuites: Jumboframes: https://git.dpdk.org/tools/dts/tree/test_plans/jumboframes_test_plan.rst Mac Filter: https://git.dpdk.org/tools/dts/tree/test_plans/mac_filter_test_plan.rst Dynamic Queue: https://git.dpdk.org/tools/dts/tree/test_plans/dynamic_queue_test_plan.rst 2) Replace XMLRPC server with Scapy interactive shell: https://bugs.dpdk.org/show_bug.cgi?id=1374 3) Configuration schema updates: Extend hugepage configuration options to allow for different sizes: https://bugs.dpdk.org/show_bug.cgi?id=1370 Cut down total configuration options in schema (not all we originally added are needed): https://bugs.dpdk.org/show_bug.cgi?id=1360 Split testbed and test configuration to different files: https://bugs.dpdk.org/show_bug.cgi?id=1344 4)API Docs generation: https://patchwork.dpdk.org/project/dpdk/list/?series=30877 5)Skip test cases based on testbed capabilities: https://patches.dpdk.org/project/dpdk/patch/20240301155416.96960-1-juraj.linkes@pantheon.tech/ Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1351 6)Rename the execution section/stage: Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1355 7)Add support for externally compiled DPDK: Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=136
Sorry, I forgot to send these last week. March 7, 2024 ##################################################################### Attendees 1. Patrick Robb 2. Ali Alnubani 3. Paul Szczepanek 4. David Marchand 5. Aaron Conole ##################################################################### Minutes ===================================================================== General Announcements * IPSEC-MB requirement increase: * Aaron has some questions about whether this new requirement has been properly documented - having a conversation with Ciara to that end on the mailing list currently * Arm did publish an updated tag for this repo - Ciara has some ideas for what may be going wrong and started a conversation on the mailing list * Patrick Robbwill forward this conversation to Paul * Building under OpenSSL is still supported * Server Refresh: * See the mailing list for the most recent ideas, but we will be putting various options in front of GB in the March meeting * Idea is to try to support as many arches as possible (intel x86, amd x86, arm grace-grace) ===================================================================== CI Status --------------------------------------------------------------------- UNH-IOL Community Lab * Hardware Refresh: * NVIDIA CX7: * Without writing out the whole background for the cx7 testing on our NVIDIA DUT, we are being bandwidth capped by the server with this performance testing, but this can be worked around by acquiring a 2nd CX7 NIC for the DUT server. * For on thing, this corresponds to the testing NVIDIA publishes: https://fast.dpdk.org/doc/perf/DPDK_23_07_NVIDIA_NIC_performance_report.pdf * Patrick has asked whether NVIDIA can donate this NIC. We can also go to the DPDK project asking for it, but they have already provided two cx7 to the Community Lab, so it is not ideal. * Over email we have noted that the Broadwell CPU is old and may not be adequate for higher bandwidth testing * QAT 8970 on Amper Server: Has been dry run and is working * Requires a few change in DTS which Patrick can submit once David/Dharmik give approval (basically relates to loading vfio with custom options for certain QAT devices only) * If there are no objections, UNH folks can write up the automation scripts today and get the testing online today or next week. * Test Coverage changes: * OpenSSL driver test has been added to our unit testing jobs * Marvell mvneta build test has been added, per: https://doc.dpdk.org/guides/nics/mvneta.html * Debian 12 has been added to the CI template engine, and we’re running testing from this now * Need to upstream this. * Robin Jarry noted on Slack UNH has been sending out results to test-reports mailing list without setting in-reply-to message-id for the patchseries. Adam has resolved this. * Ferruh also notes that in looking at this he noticed duplicate emails being sent by UNH, which we still need to resolve * Cody at UNH has been making updates to testing on Windows: * Did modify the 2022 build test this week, moving it from the MSVC preview compiler to the MSVC standard compiler (which with v17.9.2 has now caught up to the build features previously only available in the preview version) * Cody is also adding the Clang and Mingw64 compile jobs to the 2022 server (they are only on server 2019 right now) and also is adding DPDK unit test/fast tests to the 2022 server. * David Marchand noticed a bug with the create artifact script: After failing to apply on the recommended branch and trying to fall back on applying to main, it did not checkout to tip of main. Patrick will look. * Bugzilla ticket was creating noting that we need to add 23.11-staging to our CI --------------------------------------------------------------------- Intel Lab * None --------------------------------------------------------------------- Github Actions * Has to double check the ipsec-mb requirement and how we generate abi symbols. Need to check that they are pulling the right version. * In progress in migrating back to the original server this ran on before the server was physically moved to another location * Going to completely re-image/update the server * Posted a series for adding Cirrus-CI to the robot monitoring * Comments are welcome on the mailin list * Need to add a Cirrus YAML config for the DPDK repo --------------------------------------------------------------------- Loongarch Lab * Zhoumin has stated on the mailing list that he can support the email based retest framework * Possible to store commit hash when series as submitted, and recreate those artifacts as needed * Also can support re-apply on tip of branch X * There is an ongoing conversation on CI mailing list for this ===================================================================== DTS Improvements & Test Development 24.07 Roadmap * Ethdev testsuites: * Nicholas: * Jumboframes: https://git.dpdk.org/tools/dts/tree/test_plans/jumboframes_test_plan.rst * Mac Filter: https://git.dpdk.org/tools/dts/tree/test_plans/mac_filter_test_plan.rst * Prince: * Dynamic Queue: https://git.dpdk.org/tools/dts/tree/test_plans/dynamic_queue_test_plan.rst * Need to vet the testsuites. It may be possible to add additional testcases, refactor testcases. We want to flex the same capabilities as the old testsuites, but make improvements where possible. * We should loop in ethdev maintainers and ask for their review on the testcases * David test an email a couple years ago which priority ranked some ethdev capabilities and testsuites, and if we can find this email we should use it. * https://inbox.dpdk.org/ci/CAJFAV8y8-LSh5vniZXR812ckKNa2ELEJVRKRzT53PVu2zO902w@mail.gmail.com/ * Configuration schema updates: * Nicholas: * Working on the Hugepages allocation first, then will do the other config updates (ripping out some unneeded keys from the schema) * Will follow up with the ethdev testsuites * API Docs generation: * Juraj: Needs review from Thomas (the Doxygen integration part), may need to be addressed when Juraj gets back from vacation. * Skip test cases based on testbed capabilities: * Juraj: RFC should be ready before Juraj leaves on vacation. 24.07 shouldn't be a problem. * RFC Patch: https://patches.dpdk.org/project/dpdk/patch/20240301155416.96960-1-juraj.linkes@pantheon.tech/ * The patch requires https://patches.dpdk.org/project/dpdk/list/?series=31329 * Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1351 * Rename the execution section/stage: * Juraj: Juraj will work on this in 24.07 and submit a patch to continue the discussion. The v1 patch will be ready for 24.07, but the discussion/review could push the patch to 24.11. * Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1355 * Add support for externally compiled DPDK: * Juraj: Juraj will start working on this in 24.07. There's a small chance we'll get this in 24.07, but Juraj wants to target this for 24.11. * Bugzilla: https://bugs.dpdk.org/show_bug.cgi?id=1365 * Jeremy has a bugzilla ticket for refactoring how we handle scapy on the TG (no more XMLRPC server), and will do this in 24.07 * We will finalize at next DTS meeting ===================================================================== Any other business * Next Meeting: March 21, 2024
[-- Attachment #1: Type: text/plain, Size: 611 bytes --] https://bugs.dpdk.org/show_bug.cgi?id=1278 techno miz (technomiz.com@gmail.com) changed: What |Removed |Added ---------------------------------------------------------------------------- URL|https://www.thebeststockbro |https://www.technomiz.com/h |ker.com/upcoming-ipo-in-ind |ow-to-get-rid-of-creases-in |ia/ |-shoes-in-simple-steps/ CC| |technomiz.com@gmail.com -- You are receiving this mail because: You are the assignee for the bug. [-- Attachment #2: Type: text/html, Size: 1799 bytes --]
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --] You have been invited to a recurring meeting for Data Plane Development Kit (DPDK) Meeting to guide and oversee the DTS work ramp up in the UNH Community Lab Meeting minutes: https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing <https://www.google.com/url?q=https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp%3Dsharing&sa=D&source=calendar&ust=1709510381135599&usg=AOvVaw3_oFqWD78LB0ObEbhVt4d2> Ways to join meeting: 1. Join from PC, Mac, iPad, or Android https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password=66221d21-9c8b-4ccd-bc34-e56f8afafab2 <https://www.google.com/url?q=https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password%3D66221d21-9c8b-4ccd-bc34-e56f8afafab2&sa=D&source=calendar&ust=1709510381135599&usg=AOvVaw0xZ-EI6DFuBS4Tt61C20hz> 2. Join via audio One tap mobile: US: +12532158782,,96185056077# or +13462487799,,96185056077 Or dial: US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592 or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free) Canada: +1 647 374 4685 or +1 647 558 0588 or +1 778 907 2071 or +1 204 272 7920 or +1 438 809 7799 or +1 587 328 1099 or 855 703 8985 (Toll Free) Meeting ID: 96185056077 Meeting Passcode: 004462 International numbers: https://zoom.us/u/alwnPIaVT <https://www.google.com/url?q=https://zoom.us/u/alwnPIaVT&sa=D&source=calendar&ust=1709510381135599&usg=AOvVaw2fJBJlshyTG7NGBM-Xz2m7> [-- Attachment #2: Type: text/html, Size: 5929 bytes --]
[-- Attachment #1: Type: text/plain, Size: 5570 bytes --] February 22, 2024 ##################################################################### Attendees 1. Patrick Robb 2. Ali Alnubani 3. Paul Szczepanek 4. Juraj Linkeš 5. Luca Vizzarro ##################################################################### Minutes ===================================================================== General Announcements * Aaron is polling the tech board for feedback on what server hardware is most needed in the community lab going forward. Some ideas are: * AMD CPUs * RISC-V CPUs * Better PCI-E generation slots which will allow us to use newer NICs * He is visiting UNH today so we can work on starting a proposal and plan * 24.03 RC1 has been released this morning * Retest framework: Email has been sent out with the proposed syntax and approach for retests in which users want to request their patch be re-applied on tip of branch ===================================================================== CI Status --------------------------------------------------------------------- UNH-IOL Community Lab * Hardware Refresh: * NVIDIA CX7: * Had some minor improvements in the performance results, but still debugging with Ali and NVIDIA * Can possibly replaced the cx5 with another cx7, and do forwarding between 2 nics, solving 1 bandwidth bottleneck * Will work on resolving the lower speeds seen on the CX6 first - this could be related to using a different board and CPU with different clock rate etc. * This server has a broadwell CPU * Patrick Robb Make sure that Ali and Gal are included for the initial feedback thread for server refresh and what is most needed * Bringing the NVIDIA testbed offline today for a few hours so Ali and Bing can do some debugging on the mlx5 failure on the CX5 yesterday * Arm IPSEC-MB Library: Had to move to running from tip of main on the ARM ipsec repo to enablev1.4 - just storing the commit hash right now but ARM will publish a new tag for a known good version soon. * Wathsala will be doing the new tag soon --------------------------------------------------------------------- Intel Lab * None --------------------------------------------------------------------- Github Actions * We plan to have a maintenance window either Thus the 22nd, or sometime next week to cover migrating to the original server. This will involve upgrading the base os for both the host and the VM. Michael will send out the notice on the day it happens letting everyone know of the downtime. * We don't expect that the downtime will last too long, less than a day. We will likely recover the workflows shortly after that. --------------------------------------------------------------------- Loongarch Lab * Patrick pinged Zhoumin about adding retest framework support to the Loongson lab * UNH willing to assist - not sure right now what is possible/not possible based on how the loongson lab stood up their automation. They do use the dpdk-ci repo tools. ===================================================================== DTS Improvements & Test Development * Dockerfile patch can be merged - Thomas has been pinged about this on slack * Scattered packets patch: * Patrick tested this on a bnxt_en NIC, and it worked fine * When gathering device capabilities, the scatter capability is always off on mlnx nics, even when including the scatter offload flag with testpmd * Juraj is going to send to Patrick and Jermey a summary of what he has learned about passing the scatter flag and how DPDK handles it. And what he has learned about querying for this capability. * For now, not including the scatter offload flag testcase with this testsuite, only submitting the testcase which is a direct port from old dts * Luca is going to review this today. He is also running it on a MLNX nic. * Juraj: Interestingly, on the Intel NICs it is on whether you include the --enable-scatter flag or not, but the Mellanox NICs don't have it set to on in either case * Ali: Have you tried "--enable-scatter --tx-offloads=0x8000" * Jeremy Spewockwill try this * For next Wednesday, We are going to have to have discussions for putting together the 24.07 DTS roadmap since Juraj will be on vacation in March and we won’t be able to have the conversation then. * Patrick will put together some ethdev suite ideas which the new DTS employees at UNH can start on * We will also review bugzilla tickets then, assign more tickets if needed * Patch for the testcast blocking: * There is a bug (it does not include the smoke tests in the list of suites to run), so Juraj will be sending a new version * Gregory reached out to see whether his framework’s approach could be used for simple DTS cases. Juraj and Patrick read the code. There are some good ideas we are bringing into the framework, but not the phase based yaml approach which translates scapy and testpmd commands to testsuites. * XMLRPC Server: Jeremy found that there is a python dependency for the TG server which was not known (must be python 3.10+). Or else you will have an issue with a XMLRPC server function not included until verson x. * Should turn this into a bugzilla ticket, and can discuss on Wednesday. * Scapy version on TG node. Need to make sure we are on x version. Should be 2.4.4 or 2.5.0? Any other business ===================================================================== * Next Meeting: March 7, 2024 [-- Attachment #2: Type: text/html, Size: 5817 bytes --]
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --] Hi, This is finalized. The next CI meeting will be next Thursday. Then we go back to every other week. On Wed, Feb 14, 2024 at 4:20 PM Patrick Robb <probb@iol.unh.edu> wrote: > Hello all, > > As discussed in the previous CI testing meeting, it will be advantageous > for us to shift the (every other week) DPDK CI meetings forward or > backwards 1 week to get it onto a different cadence. > > That will allow us to have the DTS meetings 1 week, and the CI meetings on > the off week, instead of both on the same week, which should yield more > valuable conversations. > > So the idea is to have tomorrow's CI meeting, then have another meeting > next Thursday (2/22), then go back to every other week. So the 2/29 meeting > would be cancelled, we would have a 3/7 meeting, a 3/21 meeting, etc. > > I am hoping this will work well for those of you out there who attend > these meetings, but please let me know! If there are no objections, I will > request that Nathan modify the calendar event. Thanks. > > [-- Attachment #2: Type: text/html, Size: 1476 bytes --]
[-- Attachment #1: Type: text/plain, Size: 537 bytes --] https://bugs.dpdk.org/show_bug.cgi?id=1380 paul.szczepanek@arm.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from paul.szczepanek@arm.com --- duplcate *** This bug has been marked as a duplicate of bug 1371 *** -- You are receiving this mail because: You are the assignee for the bug. [-- Attachment #2: Type: text/html, Size: 2753 bytes --]
[-- Attachment #1: Type: text/plain, Size: 796 bytes --] https://bugs.dpdk.org/show_bug.cgi?id=1380 Bug ID: 1380 Summary: launch testpmd with a config struct containing parameters Product: DTS Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: framework Assignee: dts@dpdk.org Reporter: paul.szczepanek@arm.com Target Milestone: --- Config struct should contain sane defaults, user can override any options and pass it in as the parameter to testpmd (if no param passed, defaults used). Testpmd should allow access to all the launch options. -- You are receiving this mail because: You are the assignee for the bug. [-- Attachment #2: Type: text/html, Size: 2660 bytes --]
[-- Attachment #1: Type: text/plain, Size: 797 bytes --] Hello all, As discussed in the previous CI testing meeting, it will be advantageous for us to shift the (every other week) DPDK CI meetings forward or backwards 1 week to get it onto a different cadence. That will allow us to have the DTS meetings 1 week, and the CI meetings on the off week, instead of both on the same week, which should yield more valuable conversations. So the idea is to have tomorrow's CI meeting, then have another meeting next Thursday (2/22), then go back to every other week. So the 2/29 meeting would be cancelled, we would have a 3/7 meeting, a 3/21 meeting, etc. I am hoping this will work well for those of you out there who attend these meetings, but please let me know! If there are no objections, I will request that Nathan modify the calendar event. Thanks. [-- Attachment #2: Type: text/html, Size: 958 bytes --]
[-- Attachment #1: Type: text/plain, Size: 4238 bytes --] February 14, 2024 ##################################################################### Attendees * Patrick Robb * Juraj Linkeš * Thomas Monjalon * Gregory Etelson * Juraj Linkes * Luca Vizzarro * Nicholas Pratte ##################################################################### Agenda * Additions to the agenda * Patch discussions * DTS Developer documentation * Bugzilla discussion ##################################################################### Minutes ===================================================================== General Announcements * Added developers for DTS: Nick from UNH is starting on DTS now, and 1-2 more people from UNH will be starting on this project in the near future. * The first thing Nick will do is build the DTS API docs from Juraj’s patch and provide a review * He will be joining the meetings going forward * Recordings of these meetings can be seen at the below url, by clicking on the meeting date, then the 3 dots, then share meeting recording: https://projectadmin.lfx.linuxfoundation.org/project/a0941000005osNmAAI ===================================================================== Patch discussions * Docs improvements: Luca’s patch was accepted * Thomas noted that the schema for DPDK build options was probably not well thought out, and just imported from old dts. * Noting I remember Juraj mentioned once that cross compile targets probably are not needed 1. This is not a priority - we should wait and see if there is interest later. 2. https://bugs.dpdk.org/show_bug.cgi?id=1360 3. There are some unused values which can be removed 4. Lcores value: change from empty string to “all” (if not specifying a specific list of cores) 5. Port topology: should this be a part of the conf schema? 1. Some testsuites may allow for different port topologies and should be configurable, others may have specific requirements which should be built into the capabilities assessment per testsuite 6. Ports: If we specify port 0 on machine 1 connects to port 0 on machine 2, we don’t then need to specify port 0 on machine 2 connects to port 0 on machine 1 - it’s redundant configuration (and introduces possible setup human error) * Improved error messages: * Intent for Luca’s patch is to improve patch reporting, as well as log errors from remote sessions * Scatter * Per conversation at the previous meeting, adding a 2nd testcase to the testsuite (one will include the rx offload testpmd flag, one will not) * Ran into a type error yesterday from the xmlrpc client when running on one of the community lab’s testbeds, but will continue debugging 1. Error is about a list not being callable? Jeremy Spewock will send the error and latest diff to Juraj on Slack * When running a suite in which testpmd is started for 1 testcase, then stopped, then started again for subsequent testcases, this can lead to a timeout. The timeout comes from paramiko. * Device capabilities: Only source of truth for collecting capabilities should be any information we can gather via testpmd * Needs to build a way to mark testsuites with capabilities * Will build a list of capabilities per device * Dockerfile patch: * Patrick Robbneeds to apply this, run from container on one of our baremetal servers, and ask Thomas to merge * API Docs: * Needs reviews - Nick will provide one * Juraj: Small patch for storing the output from remote commands (strips the whitespace) * Testcase blocking: When a testcase fails, everything under it is blocked. This patch is final from Juraj’s point of view, and Jeremy has provided some comments. * More reviews are needed. Patrick and Nick can do reviews, also Luca possibly. ===================================================================== Bugzilla: * If we can assign configuration file bugzillas to two people, they can provide reviews for one another * We will discuss bugzilla tickets more tomorrow at the CI meeting ##################################################################### Any other business * Juraj is on vacation 4th of March to 29 March. [-- Attachment #2: Type: text/html, Size: 4594 bytes --]
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --] You have been invited to a recurring meeting for Data Plane Development Kit (DPDK) Meeting to guide and oversee the DTS work ramp up in the UNH Community Lab Meeting minutes: https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing <https://www.google.com/url?q=https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp%3Dsharing&sa=D&source=calendar&ust=1708311836680307&usg=AOvVaw1t_Z8NaV1LjgjxiiJb1HNp> Ways to join meeting: 1. Join from PC, Mac, iPad, or Android https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password=66221d21-9c8b-4ccd-bc34-e56f8afafab2 <https://www.google.com/url?q=https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password%3D66221d21-9c8b-4ccd-bc34-e56f8afafab2&sa=D&source=calendar&ust=1708311836680307&usg=AOvVaw1RKQDw89-QaWPmJWyhUzt6> 2. Join via audio One tap mobile: US: +12532158782,,96185056077# or +13462487799,,96185056077 Or dial: US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592 or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free) Canada: +1 647 374 4685 or +1 647 558 0588 or +1 778 907 2071 or +1 204 272 7920 or +1 438 809 7799 or +1 587 328 1099 or 855 703 8985 (Toll Free) Meeting ID: 96185056077 Meeting Passcode: 004462 International numbers: https://zoom.us/u/alwnPIaVT <https://www.google.com/url?q=https://zoom.us/u/alwnPIaVT&sa=D&source=calendar&ust=1708311836680307&usg=AOvVaw3owRH1-640L5QjeuA_CThg> [-- Attachment #2: Type: text/html, Size: 5929 bytes --]
From: Jeremy Spewock <jspewock@iol.unh.edu> As more changes have been merged into DPDK the compilation time has slowly inreased and, on some testbeds, the currently configured timeout is not long enough. This patch increases the timeout by 15 minutes which should be enough time for the foreseeable future. Signed-off-by: Jeremy Spewock <jspewock@iol.unh.edu> --- framework/project_dpdk.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/framework/project_dpdk.py b/framework/project_dpdk.py index 3f34ee02..a2931eb8 100644 --- a/framework/project_dpdk.py +++ b/framework/project_dpdk.py @@ -234,7 +234,7 @@ class DPDKdut(Dut): """ Build DPDK source code on linux use meson """ - build_time = 1800 + build_time = 2700 target_info = target.split("-") arch = target_info[0] machine = target_info[1] -- 2.43.0
In VIRTIO Version 1.2, a non-transitional device (device not supporting legacy interface), has the PCI device ID 0x1041: Virtual I/O Device (VIRTIO) Version 1.2 https://docs.oasis-open.org/virtio/virtio/v1.2/csd01/virtio-v1.2-csd01.html > 4 Virtio Transport Options > 4.1 Virtio Over PCI Bus > 4.1.2 PCI Device Discovery > 4.1.2.1 Device Requirements: PCI Device Discovery > Devices MUST have the PCI Vendor ID 0x1AF4. Devices MUST either have > the PCI Device ID calculated by adding 0x1040 to the Virtio Device ID, > as indicated in section 5 or have the Transitional PCI Device ID > depending on the device type, as follows: > 5 Device Types > 5.1 Network Device > 5.1.1 Device ID > 1 Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com> --- framework/settings.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/framework/settings.py b/framework/settings.py index 1a561dda..be79bc60 100644 --- a/framework/settings.py +++ b/framework/settings.py @@ -46,6 +46,7 @@ NICS = { "IGB_1G-I210_COPPER": "8086:1533", "IXGBE_10G-82599_SFP_SF_QP": "8086:154a", "virtio": "1af4:1000", + "virtio-modern": "1af4:1041", "IGB_1G-I354_SGMII": "8086:1f41", "IGB_2.5G-I354_BACKPLANE_2_5GBPS": "8086:1f45", "IGB_1G-PCH_LPT_I217_V": "8086:153b", @@ -141,6 +142,7 @@ DRIVERS = { "IGB_1G-I210_COPPER": "igb", "IXGBE_10G-82599_SFP_SF_QP": "ixgbe", "virtio": "virtio-pci", + "virtio-modern": "virtio-pci", "IGB_1G-I354_SGMII": "igb", "IGB_2.5G-I354_BACKPLANE_2_5GBPS": "igb", "IGB_1G-PCH_LPT_I217_V": "igb", --- base-commit: 427e7c3f37bbb1263d81c466d7a83e9193013321 change-id: 20240203-virtio-1020822e7344 Best regards, -- Akihiko Odaki <akihiko.odaki@daynix.com>
GNU grep 3.8 outputs: > egrep: warning: egrep is obsolescent; using grep -E This makes self.send_expect() fail. Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com> --- framework/crb.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/framework/crb.py b/framework/crb.py index 9e3b0a58..9b7688c7 100644 --- a/framework/crb.py +++ b/framework/crb.py @@ -1069,7 +1069,7 @@ class Crb(object): elif self.get_os_type() == "freebsd": return False elif self.send_expect( - "systemd-detect-virt -c|egrep '(systemd-nspawn|lxc|docker|podman|rkt|wsl|container-other)$' ", + "systemd-detect-virt -c|grep -E '(systemd-nspawn|lxc|docker|podman|rkt|wsl|container-other)$' ", "# ", ): return True --- base-commit: 427e7c3f37bbb1263d81c466d7a83e9193013321 change-id: 20240203-crb-131f32522af5 Best regards, -- Akihiko Odaki <akihiko.odaki@daynix.com>
README of bridge-utils v1.7.1 says: > This utility is DEPRECATED. No new features will ever be added. > Instead use the bridge command from the iproute2 package which > supports more features. https://git.kernel.org/pub/scm/network/bridge/bridge-utils.git/tree/README?h=v1.7.1 Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com> --- framework/qemu_kvm.py | 2 +- framework/qemu_libvirt.py | 2 +- test_plans/sriov_kvm_test_plan.rst | 2 +- test_plans/vf_port_start_stop_test_plan.rst | 2 +- tests/TestSuite_ip_pipeline.py | 6 +++--- 5 files changed, 7 insertions(+), 7 deletions(-) diff --git a/framework/qemu_kvm.py b/framework/qemu_kvm.py index b656675c..7f6df7c2 100644 --- a/framework/qemu_kvm.py +++ b/framework/qemu_kvm.py @@ -68,7 +68,7 @@ class QEMUKvm(VirtBase): + " tunctl -t $1\n" + " ip link set $1 up\n" + " sleep 0.5s\n" - + " brctl addif $switch $1\n" + + " ip link set $1 master $switch\n" + " exit 0\n" + "else\n" + " echo 'Error: no interface specified'\n" diff --git a/framework/qemu_libvirt.py b/framework/qemu_libvirt.py index e99ce8fb..22214481 100644 --- a/framework/qemu_libvirt.py +++ b/framework/qemu_libvirt.py @@ -30,7 +30,7 @@ class LibvirtKvm(VirtBase): + " tunctl -t $1\n" + " ip link set $1 up\n" + " sleep 0.5s\n" - + " brctl addif $switch $1\n" + + " ip link set $1 master $switch\n" + " exit 0\n" + "else\n" + " echo 'Error: no interface specified'\n" diff --git a/test_plans/sriov_kvm_test_plan.rst b/test_plans/sriov_kvm_test_plan.rst index c9085dd9..42d3c059 100644 --- a/test_plans/sriov_kvm_test_plan.rst +++ b/test_plans/sriov_kvm_test_plan.rst @@ -47,7 +47,7 @@ The /etc/qemu-ifup can be below script, need you to create first:: /usr/sbin/tunctl -u `whoami` -t $1 /sbin/ip link set $1 up sleep 0.5s - /usr/sbin/brctl addif $switch $1 + /sbin/ip link set $1 master $switch exit 0 else echo "Error: no interface specified" diff --git a/test_plans/vf_port_start_stop_test_plan.rst b/test_plans/vf_port_start_stop_test_plan.rst index 502afa6c..618fcb99 100644 --- a/test_plans/vf_port_start_stop_test_plan.rst +++ b/test_plans/vf_port_start_stop_test_plan.rst @@ -72,7 +72,7 @@ Create Two VF interfaces from two kernel PF interfaces, and then attach them to /usr/sbin/tunctl -u `whoami` -t $1 /sbin/ip link set $1 up sleep 0.5s - /usr/sbin/brctl addif $switch $1 + /sbin/ip link set $1 master $switch exit 0 else echo "Error: no interface specified" diff --git a/tests/TestSuite_ip_pipeline.py b/tests/TestSuite_ip_pipeline.py index 19b297de..44dfaf5f 100644 --- a/tests/TestSuite_ip_pipeline.py +++ b/tests/TestSuite_ip_pipeline.py @@ -832,9 +832,9 @@ class TestIpPipeline(TestCase): self.dut.send_expect(cmd, "fwd port 3", 60) tap_session = self.dut.new_session() - cmd = "ip link set br1 down; brctl delbr br1" + cmd = "ip link set br1 down; ip link delete br1" tap_session.send_expect(cmd, "# ", 20) - cmd = "brctl addbr br1; brctl addif br1 TAP0; brctl addif br1 TAP1" + cmd = "ip link add br1 type bridge; ip link set TAP0 master br1; ip link set TAP1 master br1" tap_session.send_expect(cmd, "# ", 20) cmd = "ifconfig TAP0 up; ifconfig TAP1 up; ifconfig br1 up" tap_session.send_expect(cmd, "# ", 20) @@ -874,7 +874,7 @@ class TestIpPipeline(TestCase): cmd = "^C" self.dut.send_expect(cmd, "# ", 20) - cmd = "ip link set br1 down; brctl delbr br1" + cmd = "ip link set br1 down; ip link delete br1" tap_session.send_expect(cmd, "# ", 20) self.dut.close_session(tap_session) --- base-commit: 427e7c3f37bbb1263d81c466d7a83e9193013321 change-id: 20240203-brctl-8fdbef4c69be Best regards, -- Akihiko Odaki <akihiko.odaki@daynix.com>
[-- Attachment #1: Type: text/plain, Size: 3871 bytes --] February 1, 2024 ##################################################################### Attendees 1. Patrick Robb 2. Paul Szczepanek 3. Thomas Monjalon 4. Juraj Linkes 5. Ali Alnubani 6. Aaron Conole ##################################################################### Minutes ===================================================================== General Announcements * Per mailing list/slack conversation, an important feature to add for the email based retest framework is to trigger a retest, but instead of retesting the original DPDK artifact created for the patchseries, re-apply on latest and retest. Ferruh suggests we include an optional argument “pull”, so if “pull=true” we re-apply on latest, if the argument is omitted or pull=false we do the normal behavior. * Some community members running automation are still pulling from the dpdk.org git server and need to move to github. People who don’t move will get blacklisted, and then they will move quickly. * Making periodic test results more visible: * Would be helpful to list the testing labels matrix for periodic “main” testing on the dpdk.org testing page (or a page under testing). * After main, we should add all branches, and should display datetime of test and branch name * Can also extend this to per patch testing. If we only include the latest patch tested, at least that shows all the labels tested. * Would be helpful to have a more detailed description. * We can do this in small steps, and just start with periodic testing. * Is there a problem with testing RFCs? UNH and GHA are not doing it, but should start. It does present a value to maintainers/developers and it probably does not present a testing capacity problem (most come early in a release cycle.) ===================================================================== CI Status --------------------------------------------------------------------- UNH-IOL Community Lab * Automation for TS-Factory testing is now online at UNH * Runs on ARM servers, for the XL710 NIC and MLNX CX5 * Runs 1x/month * Posts results to https://ts-factory.io/bublik/v2/runs * UNH team is still working on provisioning the new server donated by Intel * Requesting reviews/comments on Adam’s create artifact script (can be used in ci to leverage the pw_maintainers_cli.py tool for creating DPDK artifacts from new patchseries): https://inbox.dpdk.org/ci/20240118234120.29256-1-ahassick@iol.unh.edu/ * Rebuilding containers for all testing which has an ipsec-mb library dependency (fips, zuc, snow3g) due to the minimal version increasing to 1.4: https://inbox.dpdk.org/dev/20240130142412.2047550-1-venkatx.sivaramakrishnan@intel.com/ --------------------------------------------------------------------- Intel Lab * No updates from John --------------------------------------------------------------------- Github Actions * Will be (within the next week) migrating the VM which runs the robot. The disruption should be about one half day. --------------------------------------------------------------------- Loongarch Lab * None ===================================================================== DTS Improvements & Test Development * We held a meeting yesterday for this. * We have someone at UNH starting now on this project (Nicholas Pratte), so we will see if he can start joining these meetings * Should update the bugzilla query for DTS to include the priority column so we can sort by that ===================================================================== Any other business * In the near future, we should change the week which ci meetings fall on, so that they are on the off week of the DTS meetings * Thomas will start saving the ci meeting minutes on the website * Next Meeting: February 15, 2024 [-- Attachment #2: Type: text/html, Size: 4314 bytes --]
[-- Attachment #1: Type: text/plain, Size: 8423 bytes --] January 31, 2024 ##################################################################### Attendees * Patrick Robb * Juraj Linkeš * Paul Szczepanek * Jeremy Spewock * Luca Vizzarro * Thomas Monjalon ##################################################################### Agenda * Additions to the agenda * Patch discussions * DTS Developer documentation * 24.03 roadmap ##################################################################### Minutes ===================================================================== General Announcements * Added developers for DTS: Nick from UNH is starting on DTS now, and 1-2 more people from UNH will be starting on this project in the near future. ===================================================================== Patch discussions * Dockerfile patch is updated to fix poetry installation and add documentation for using SSH keys. * We are not going to COPY in the keys to the image from the Dockerfile. New approach is volume mounting ~/.ssh to the container at Docker run, and readme is provided explaining this process * Patrick Robb will run this, add a tag on the patch, and request a merge from Thomas * Scatter is submitted and has been reviewed by Juraj, looking for more reviews from community members to get that patch moving. * Can have 1 test for no offload, and 1 test for including offload 1. If scatter is not available, we should expect a failure in the second case. 2. Feature is underdocumented currently 3. We can add a patch adding comments documenting the feature. All lines in ethdev.h should be commented, so it is a “bug” that additions from early dpdk days are not well documented. (RTE_ETH_RX_OFFLOAD_SCATTER) 4. doc/guides/nics/features.rst - this file documents the feature matrix, what the feature does and how we determine if the feature is available. * Docstring patch: What is the latest status of the needed meson changes? Has Bruce provided any feedback? * Bruce said he was OK with the patch, but Juraj is not * The docs don't look as good as they probably could. * The current process generates the docs in two steps: one generates the .rst inputs for Sphinx (using the sphinx-apidoc tool), the second step then generates the actual html docs from the .rst file. * Juraj is looking into removing the sphinx-apidoc step from meson and having a semi-manual way to produce the .rst files: running the sphinx-apidoc locally the first time (or when there's a big change to file structure) and adding new files manually (which is very easy copy-paste with just a few changes). * The second approach gives us much better control over how the docs look and how we structure the pages. * Do we want to generate docs from test suites? This is likely an item for the future. * Action item: Try to generate the docs, give feedback on how it looks, give feedback on maintenance. * Blocked test case results recording: In progress, needs rebase on top of docstrings and finishing touches. * DTS Documentation from Luca. * Has been merged by Thomas now. * We might want to move around some documentation so it is more logically partitioned for readers. * Juraj is ok with the patch, but Thomas wants bigger changes. We need to agree on what we do in this patch and what in other patches. * Possibly related are these bugzilla items: 1. DTS: Split testbed and test configuration 2. DTS: Rename the execution section/stage 3. DTS Config improvements * On one more item that came up during the review: 1. DTS: add support for externally compiled DPDK ===================================================================== The original DTS patches * Thomas pinged Intel people to check whether there can be a final round of DTS patches merged, or some minimal support for that repo going forward. There are some tens or hundreds of patches which were submitted after Lijuan Tu (old maintainer) left Intel, which are just languishing in the dts mailing list. * Jeremy has a patch extending timeout for DTS which he can submit, but only if there will be more merging coming up * Patrick has some patch(es) adding cx6 and cx7 NICs to old DTS. Technically our testbeds running now are forked. When setup is 100% done for both NICs, intending to circle back and add these NICs to upstream DTS if merging is a possibility. New/Open feature requests * How do we want to handle feature requests for the framework going forward? We have a lot of needed features dumped into bugzilla now (thank you Juraj), but how do we prioritize, filter through what is most important for each release? * Patrick suggests: incorporate bugzilla tickets into release roadmaps, assign them to individuals, and set action items at each DTS meeting for bugzilla tickets. https://bugs.dpdk.org/buglist.cgi?bug_status=__open__&component=dts&product=DPDK * We can also run through all the tickets during meetings, and set the “importance” value for any new tickets ===================================================================== 24.03 Roadmap * Can we extend this? * Should we add another ethdev suite to work on? 1. Mtu update is running in the lab currently and seems like it would be a good candidate. Only thing to consider with this suite is that the old DTS version is broken on all non-intel NICs due to a mismatched assumption about VLAN headers, so that could lead to some getting stuck in the weeds. This suite could also be done in two main ways that I can think of, either we verify that the packet was forwarded or not by checking the number of packets sent and received on the port, or we could instead just see if we get anything back on the tg side. Checking if we received a packet on the tg side would be more seamless with what we have but either way could lead to false positives. 2. Jumboframes would also be a reasonable option, the only thing to consider with this suite is one of the cases is a “didn’t receive anything” case currently which could easily lead to both false positives if something went wrong, or false negatives with the lack of bullet-proof packet filtering. 3. Mac-filter would force us to introduce something new to the framework which is verification using the number of packets received. Could be difficult if there is any other noise on the interface. ===================================================================== Action Items * Jeremy Spewock will be working on https://bugs.dpdk.org/show_bug.cgi?id=1359 bugzilla ticket * Juraj Linkeš will be taking this ticket: https://bugs.dpdk.org/show_bug.cgi?id=1365 ===================================================================== Any other business * What should be the deadline for DTS changes in the release cycle? DTS changes will never break DPDK functionality, but we want some reasonable buffer between changing a test and a release. * Proposal: RC2 deadline for modifying an existing test or modifying the DTS framework, RC3 for adding a new test * Please read Gregory’s email about writing testsuites in his “unit test” app, for the flow API, creating flow rules and how he validates for sending packets with a certain VLAN id, etc. * Packet filtering is something that has been tossed around and discussed here and there but one idea that was mentioned was just adding a few bytes to the end of every packet as a sort of “DTS header” that we could check for the presence of to ensure that the packets are relevant. * Could this cause issues with suites that require certain MTU sizes? If so it doesn’t seem difficult to account for when setting packet lengths. * Are there any test suites where a packet would get sent to the SUT and in getting forwarded back these extra bytes get stripped? Is there a test case where you send one packet to the SUT and the SUT forwards multiple packets back? ===================================================================== Notes on gathering device capabilities: * In the short term we should move to gathering device and queue capabilities as a preliminary step for a testsuite, and execution the testsuite (or specific testcases) based on information gathered. Then we also use testpmd for configuring. [-- Attachment #2: Type: text/html, Size: 8877 bytes --]
[-- Attachment #1: Type: text/plain, Size: 1536 bytes --] You have been invited to a recurring meeting for Data Plane Development Kit (DPDK) Meeting to guide and oversee the DTS work ramp up in the UNH Community Lab Meeting minutes: https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing <https://www.google.com/url?q=https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp%3Dsharing&sa=D&source=calendar&ust=1707111597318791&usg=AOvVaw30uNAui7RHYCioE1kmeyrR> Ways to join meeting: 1. Join from PC, Mac, iPad, or Android https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password=66221d21-9c8b-4ccd-bc34-e56f8afafab2 <https://www.google.com/url?q=https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password%3D66221d21-9c8b-4ccd-bc34-e56f8afafab2&sa=D&source=calendar&ust=1707111597318791&usg=AOvVaw23t7_lc9I5MMsNR_8h7Ttq> 2. Join via audio One tap mobile: US: +12532158782,,96185056077# or +13462487799,,96185056077 Or dial: US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592 or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free) Canada: +1 647 374 4685 or +1 647 558 0588 or +1 778 907 2071 or +1 204 272 7920 or +1 438 809 7799 or +1 587 328 1099 or 855 703 8985 (Toll Free) Meeting ID: 96185056077 Meeting Passcode: 004462 International numbers: https://zoom.us/u/alwnPIaVT <https://www.google.com/url?q=https://zoom.us/u/alwnPIaVT&sa=D&source=calendar&ust=1707111597318791&usg=AOvVaw0_AN_DTodLzQ6cX4rM3mWx> [-- Attachment #2: Type: text/html, Size: 6022 bytes --]
[-- Attachment #1: Type: text/plain, Size: 7051 bytes --] January 18, 2024 ##################################################################### Attendees 1. Lincoln Lavoie 2. Thomas Monjalon 3. Aaron Conole 4. Jeremy Spewock 5. Paul Szczepanek 6. Ali Alnubani 7. Juraj Linkeš ##################################################################### Minutes ===================================================================== General Announcements * First 2024 DTS WG meeting was held yesterday, and the minutes are here: https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing * Patrick Robb will publish the meeting minutes ===================================================================== CI Status --------------------------------------------------------------------- UNH-IOL Community Lab * Octeon CN106XX: Patrick worked with Hiral this week about the process for SDK rebuild. This will have to happen regularly, but we now have a VM setup which will serve as the place to rebuild SDK and act as TFTP server for the Octeon board. * After that we need to iron out switching rootfs to ubuntu, setting up DTS on the tester, validating this works fine in a CI context (Phanendra from Marvell has approved of the concept). * The Intel server arrived in the mail yesterday. We will mount the system this week and begin setup. As a reminder this now unblocks: * E810 testing for Intel * Traffic gen for the CX7 testing (this server will act as TG) * Traffic gen for the Octeon CN106xx board * The new create dpdk artifact for ci testing script is in production at UNH, and Adam is submitting the V3 patchseries for this to dpdk-ci today * There is an update from the patchwork maintainer about supporting Depends-on via patchwork. I encourage everyone to read his full thoughts on the issue below, but shorthand conclusions are: * He prefers to only support Depends-on on a series basis, not a series or patch basis. * Patrick will update the CI testing thread on this topic, but this may require the DPDK community agreeing to a new approach. From looking through the dev mailing list, it seems that series dependency is the typical use, but there are also some examples of developers using patch dependency. * Keep the same syntax which allows for depends-on: patch, but in reality translate this to depends on that patch’s series * He will need some help for the effort. We can ping the DPDK community to look for volunteers. Or, it can possibly become a community ask for development at the DPDK Community Lab. Looking at it at a high level I don’t think the scope will be too bad. * Full thread: https://github.com/getpatchwork/git-pw/issues/71 * Arm-Ampere still needs a kernel rebuild for the QAT card * Standing up ts-factory testing framework * Adam did the first cx-5 run on an ARM system, and will do an Intel XL710 run on an ARM system today. Both will be published on Oktet Lab’s Bublik for review. * Unlike our ARM testbeds, our x86 servers are single server TG/DUT testbeds, which breaks an assumption in ts-factory. My view on how to proceed is bring testing online with what works now (arm), then review the value with the community, and choose a strategy for x86 based on what we learn from running this at the lab. * Andrew from Oktet labs has added some missing components to GitHub for the data visualization tool (Bublik), and has finished categorizing the tests for the XL710 and the expected results for that NIC * Old DTS patches: * We noticed that as DPDK has grown, the compile time also increases and the old compile timeout for the DUT is no longer valid on some slower systems. Jeremy will submit a patch extending the timeout. * Once the cx7 is online, patrick will submit the patch adding the cx6 and cx7 to the NIC registry in DTS * Lincoln saw the email thread about DPDK failing to build on FreeBSD 14. We are only testing FreeBSD 13 in the lab right now, so we will add coverage for 14. --------------------------------------------------------------------- Intel Lab * John says there is still no new person who can act as a contact. There have been further staffing changes at Intel, so it may be hard to get a contact soon, but Patrick will keep asking. --------------------------------------------------------------------- Github Actions * Cirrus CI: Adding support for this to the 0 day robot. Aaron submitted a patch for polling for Cirrus ci status in ovs. * They are getting a server to migrate the VM over to, so there should be minimal downtime associated with the hardware moving from Westford to another state. --------------------------------------------------------------------- Loongarch Lab * None ===================================================================== DTS Improvements & Test Development * scapy/templated yaml for tests: * One motivation is for making writing simple tests in minimal time (like 3 minutes). Should we aim for a target of writing a testsuite in minutes, not hours? * Testing is broken down into phases, and you simply write in the raw scapy commands or values to pass to testpmd * At the end, compare output string to an expected output string written in the YAML * Is it possible to get the best of both worlds? We can try to remain with python only, but use python annotations and assign python to TG, DUT commands etc. * Gregory also splits the configuration of platform and test configuration. * We should draw up a “pseudo” version of this structured test setup via python, and review as a group * If we can draw this up we can compare against a currently written test (like Jeremy’s scatter test), and then we will have a practical example of the effort difference between the two approaches. * The API will evolve over time - for drawing up an example, we can make up whatever we want * By using a templating system (or some python “syntactic sugar”), we may remove some of the boilerplate overhead form writing a suite - possibly a major value for making writing testsuites easier. * Obviously this all needs to be documented. * Paul: It may be a good approach to have a few more people write at least one testsuite according to the current approach. Then, we use these new tests to guide the creation of the “new” approach. Hopefully we learn what works, what needs to be improved and refactored out into the framework - pre-proving the validity of the new approach. * All DTS people will try to workshop next week to investigate what a new approach would look like in concrete terms. * DTS group will go through all the new Bugzilla tickets at the next DTS meeting. * Jeremy has volunteered to at least one during this release: * https://bugs.dpdk.org/show_bug.cgi?id=1359 ===================================================================== Any other business * Next Meeting: February 1, 2024 [-- Attachment #2: Type: text/html, Size: 7507 bytes --]
[-- Attachment #1: Type: text/plain, Size: 2643 bytes --] January 17, 2024 ##################################################################### Attendees * Juraj Linkeš * Gregory Etelson * Honnappa Nagarahalli * Jeremy Spewock * Luca Vizzarro * Paul Szczepanek ##################################################################### Agenda * Additions to the agenda * Patch discussions * DTS Developer documentation * 24.03 roadmap ##################################################################### Minutes ===================================================================== Additions to the agenda * Nothing ===================================================================== YAML test suites * Greg wanted to automate his testing; started with test writtens in Python, but was not scalable; easily understandable by newcomers. * The idea is to take an application, send commands (interactive input), collect output and compare with expected strings. * The code was available as of two months ago, but no longer is (private on GitHub). Greg may be able to share it once taking care of it in his company. * Gregory submitted an idea for writing test suites in yaml, which just passes values into a templated testpmd testsuite. * Do we want to support a secondary way of writing test suites? * Will this be usable for both functional and performance testing? * Will this coexist well with the current method? * The current method also aims to be minimalistic and intuitive * Coexistence makes sense as the yaml approach may not be able to cover more complicated cases * What are any limitations which this places on the testing framework? If there aren’t major downsides, then the benefits in terms of quickly adding new testpmd testsuites seems significant. * The traffic generator can't be configured here, we need an abstraction that works for all traffic generators; we can mark the test cases as functional/performance though, which could be enough * We can only specify test-specific testpmd cmdline options; shouldn't be a problem, but we have to keep in mind that configuration such as cores and pci addresses are configured elsewhere (the testbed configuration) * Using specific strings in testpmd is harder to maintain (if the same config is used in multiple places) * Are the phases for both setup/teardown and test cases? This could complicate results recording * Can we easily specify multiple test cases? I.e. we have a test method and we want to test different input combinations (the inputs could just be the number of cores/packet size for performance tests) [-- Attachment #2: Type: text/html, Size: 2768 bytes --]
[-- Attachment #1: Type: text/plain, Size: 8072 bytes --] Sorry, false alarm! He just needed the passcode. Thanks! On Wed, Jan 17, 2024 at 10:10 AM Patrick Robb <probb@iol.unh.edu> wrote: > Hi Nathan, > > Hi Nathan. Jeremy is saying that the DTS meeting is private/invite only > and won't let him join. Is his email added? Or do meeting settings need to > be modified? jspewock@iol.unh.edu > > I can't test it myself as I am in another Zoom currently. > > On Tue, Jan 16, 2024 at 6:08 PM Patrick Robb <probb@iol.unh.edu> wrote: > >> This is just a reminder that the first meeting is tomorrow at 15:00 UTC. >> I have a one time conflict and won't be there, but I'll see yall at the >> subsequent meetings! Let me know if anyone wasn't included on the invite >> list. And I'll include the meeting info below for anyone without an invite. >> I asked Juraj if he would drive the topics and transcribe minutes, but if >> anyone else wants to volunteer that works too! >> >> You have been invited to a recurring meeting for Data Plane Development >> Kit (DPDK) Meeting to guide and oversee the DTS work ramp up in the UNH >> Community Lab Meeting minutes: >> https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing >> <https://www.google.com/url?q=https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp%3Dsharing&sa=D&source=calendar&ust=1705876800213036&usg=AOvVaw0_8FVnCEhKsKvt1hhQZ1kg> >> Ways to join meeting: 1. Join from PC, Mac, iPad, or Android >> https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password=66221d21-9c8b-4ccd-bc34-e56f8afafab2 >> <https://www.google.com/url?q=https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password%3D66221d21-9c8b-4ccd-bc34-e56f8afafab2&sa=D&source=calendar&ust=1705876800213036&usg=AOvVaw3qMfnso6MRPRbMDWld4GO7> >> 2. Join via audio One tap mobile: US: +12532158782,,96185056077# or >> +13462487799,,96185056077 Or dial: US: +1 253 215 8782 or +1 346 248 7799 >> or +1 669 900 6833 or +1 301 715 8592 or +1 312 626 6799 or +1 646 374 8656 >> or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free) Canada: +1 647 374 >> 4685 or +1 647 558 0588 or +1 778 907 2071 or +1 204 272 7920 or +1 438 809 >> 7799 or +1 587 328 1099 or 855 703 8985 (Toll Free) Meeting ID: 96185056077 >> Meeting Passcode: 004462 >> >> On Tue, Jan 9, 2024 at 10:13 AM Patrick Robb <probb@iol.unh.edu> wrote: >> >>> So that's 15:00 UTC on Wednesday on the same week as CI meetings, so it >>> should start 1/17. I'll have Nathan use the same invite list as he is using >>> for CI testing. I can typically make that time, but have a conflict for >>> next Wednesday specifically, so I won't be able to take notes for the >>> minutes. Someone else will have to volunteer. We can start using the doc >>> below. >>> >>> >>> https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing >>> >>> On Tue, Jan 9, 2024 at 9:59 AM Patrick Robb <probb@iol.unh.edu> wrote: >>> >>>> Okay, so it sounds like 15:00 UTC on the off week of the tech board >>>> meetings is one decent option, as most people can make that one. Sorry >>>> Honnappa, I know the 15:00-16:00 timeslot doesn't work for at least 1 >>>> person already without having polled people on it, so I don't think that's >>>> worth pursuing. >>>> >>>> So the meeting should be happening in the same week as CI testing >>>> calls. Hopefully that will free up some time on those meetings and we will >>>> stop going over time every time, hah. >>>> >>>> I will message Nathan asking him to set this regular meeting up via LF >>>> so it's official. >>>> >>>> Best, >>>> Patrick >>>> >>>> >>>> On Wed, Jan 3, 2024 at 5:56 AM Juraj Linkeš <juraj.linkes@pantheon.tech> >>>> wrote: >>>> >>>>> The best times for me are 14:00 UTC either on Monday or Wednesday. The >>>>> 15:00 UTC times collide with my calls, but it's not a big deal if I miss >>>>> them every other week. >>>>> >>>>> Juraj >>>>> >>>>> On Wed, Jan 3, 2024 at 12:08 AM Patrick Robb <probb@iol.unh.edu> >>>>> wrote: >>>>> >>>>>> +Lincoln Lavoie <lylavoie@iol.unh.edu> >>>>>> >>>>>> Thanks for the feedback all. Adding Lincoln who I accidentally left >>>>>> off the original email. I am on vacation this week but will let anyone else >>>>>> respond this week and then set the regular meeting time next Monday. >>>>>> >>>>>> On Tue, Jan 2, 2024 at 4:56 PM Honnappa Nagarahalli < >>>>>> Honnappa.Nagarahalli@arm.com> wrote: >>>>>> >>>>>>> 15:00 – 16:00 UTC Tuesdays works better for me. >>>>>>> >>>>>>> >>>>>>> >>>>>>> *From:* Paul Szczepanek <Paul.Szczepanek@arm.com> >>>>>>> *Sent:* Tuesday, January 2, 2024 3:27 AM >>>>>>> *To:* Patrick Robb <probb@iol.unh.edu>; Juraj Linkeš >>>>>>> <juraj.linkes@pantheon.tech>; Honnappa Nagarahalli < >>>>>>> Honnappa.Nagarahalli@arm.com>; Luca Vizzarro <Luca.Vizzarro@arm.com>; >>>>>>> Yoan Picchi <yoan.picchi@foss.arm.com>; Jeremy Spewock < >>>>>>> jspewock@iol.unh.edu>; thomas@monjalon.net; getelson@nvidia.com >>>>>>> *Cc:* ci@dpdk.org >>>>>>> *Subject:* Re: Regular DTS meeting scheduling >>>>>>> >>>>>>> >>>>>>> >>>>>>> 14:00-15:00 UTC Wednesdays looks great but all the times listed work >>>>>>> for me, Yoan and Luca. >>>>>>> >>>>>>> >>>>>>> ------------------------------ >>>>>>> >>>>>>> *From:* Patrick Robb <probb@iol.unh.edu> >>>>>>> *Sent:* 22 December 2023 18:33 >>>>>>> *To:* Juraj Linkeš <juraj.linkes@pantheon.tech>; Honnappa >>>>>>> Nagarahalli <Honnappa.Nagarahalli@arm.com>; Paul Szczepanek < >>>>>>> Paul.Szczepanek@arm.com>; Luca Vizzarro <Luca.Vizzarro@arm.com>; >>>>>>> Yoan Picchi <yoan.picchi@foss.arm.com>; Jeremy Spewock < >>>>>>> jspewock@iol.unh.edu>; thomas@monjalon.net <thomas@monjalon.net>; >>>>>>> getelson@nvidia.com <getelson@nvidia.com> >>>>>>> *Cc:* ci@dpdk.org <ci@dpdk.org> >>>>>>> *Subject:* Regular DTS meeting scheduling >>>>>>> >>>>>>> >>>>>>> >>>>>>> Hello all DTS interested people, >>>>>>> >>>>>>> >>>>>>> >>>>>>> I'm looking to find a good timeslot for having DTS sync calls >>>>>>> this Spring. Obviously we want to do it on the off weeks from the CI >>>>>>> meetings, and we want to do it in the morning USA time so that it works for >>>>>>> EU people too. >>>>>>> >>>>>>> >>>>>>> >>>>>>> Right now the timeslots I'm looking at are: >>>>>>> >>>>>>> >>>>>>> >>>>>>> 14:00-15:00 UTC Mondays >>>>>>> >>>>>>> 15:00-16:00 UTC Mondays >>>>>>> >>>>>>> 14:00-15:00 UTC Wednesdays >>>>>>> >>>>>>> 15:00-16:00 UTC Wednesdays >>>>>>> >>>>>>> >>>>>>> >>>>>>> All else being equal, Wednesdays are probably best, as it allows for >>>>>>> better spacing between CI meetings, but we'll do whatever works for the >>>>>>> most people. Please feel free to indicate your availability! >>>>>>> >>>>>>> >>>>>>> >>>>>>> Best, >>>>>>> >>>>>>> Patrick >>>>>>> IMPORTANT NOTICE: The contents of this email and any attachments are >>>>>>> confidential and may also be privileged. If you are not the intended >>>>>>> recipient, please notify the sender immediately and do not disclose the >>>>>>> contents to any other person, use it for any purpose, or store or copy the >>>>>>> information in any medium. Thank you. >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> Patrick Robb >>>>>> >>>>>> Technical Service Manager >>>>>> >>>>>> UNH InterOperability Laboratory >>>>>> >>>>>> 21 Madbury Rd, Suite 100, Durham, NH 03824 >>>>>> >>>>>> www.iol.unh.edu >>>>>> >>>>>> >>>>>> >>>> >>>> >>> >> >> -- >> >> Patrick Robb >> >> Technical Service Manager >> >> UNH InterOperability Laboratory >> >> 21 Madbury Rd, Suite 100, Durham, NH 03824 >> >> www.iol.unh.edu >> >> >> > > -- > > Patrick Robb > > Technical Service Manager > > UNH InterOperability Laboratory > > 21 Madbury Rd, Suite 100, Durham, NH 03824 > > www.iol.unh.edu > > > -- Patrick Robb Technical Service Manager UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 www.iol.unh.edu [-- Attachment #2: Type: text/html, Size: 21361 bytes --]
[-- Attachment #1: Type: text/plain, Size: 7550 bytes --] Hi Nathan, Hi Nathan. Jeremy is saying that the DTS meeting is private/invite only and won't let him join. Is his email added? Or do meeting settings need to be modified? jspewock@iol.unh.edu I can't test it myself as I am in another Zoom currently. On Tue, Jan 16, 2024 at 6:08 PM Patrick Robb <probb@iol.unh.edu> wrote: > This is just a reminder that the first meeting is tomorrow at 15:00 UTC. I > have a one time conflict and won't be there, but I'll see yall at the > subsequent meetings! Let me know if anyone wasn't included on the invite > list. And I'll include the meeting info below for anyone without an invite. > I asked Juraj if he would drive the topics and transcribe minutes, but if > anyone else wants to volunteer that works too! > > You have been invited to a recurring meeting for Data Plane Development > Kit (DPDK) Meeting to guide and oversee the DTS work ramp up in the UNH > Community Lab Meeting minutes: > https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing > <https://www.google.com/url?q=https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp%3Dsharing&sa=D&source=calendar&ust=1705876800213036&usg=AOvVaw0_8FVnCEhKsKvt1hhQZ1kg> > Ways to join meeting: 1. Join from PC, Mac, iPad, or Android > https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password=66221d21-9c8b-4ccd-bc34-e56f8afafab2 > <https://www.google.com/url?q=https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password%3D66221d21-9c8b-4ccd-bc34-e56f8afafab2&sa=D&source=calendar&ust=1705876800213036&usg=AOvVaw3qMfnso6MRPRbMDWld4GO7> > 2. Join via audio One tap mobile: US: +12532158782,,96185056077# or > +13462487799,,96185056077 Or dial: US: +1 253 215 8782 or +1 346 248 7799 > or +1 669 900 6833 or +1 301 715 8592 or +1 312 626 6799 or +1 646 374 8656 > or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free) Canada: +1 647 374 > 4685 or +1 647 558 0588 or +1 778 907 2071 or +1 204 272 7920 or +1 438 809 > 7799 or +1 587 328 1099 or 855 703 8985 (Toll Free) Meeting ID: 96185056077 > Meeting Passcode: 004462 > > On Tue, Jan 9, 2024 at 10:13 AM Patrick Robb <probb@iol.unh.edu> wrote: > >> So that's 15:00 UTC on Wednesday on the same week as CI meetings, so it >> should start 1/17. I'll have Nathan use the same invite list as he is using >> for CI testing. I can typically make that time, but have a conflict for >> next Wednesday specifically, so I won't be able to take notes for the >> minutes. Someone else will have to volunteer. We can start using the doc >> below. >> >> >> https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing >> >> On Tue, Jan 9, 2024 at 9:59 AM Patrick Robb <probb@iol.unh.edu> wrote: >> >>> Okay, so it sounds like 15:00 UTC on the off week of the tech board >>> meetings is one decent option, as most people can make that one. Sorry >>> Honnappa, I know the 15:00-16:00 timeslot doesn't work for at least 1 >>> person already without having polled people on it, so I don't think that's >>> worth pursuing. >>> >>> So the meeting should be happening in the same week as CI testing calls. >>> Hopefully that will free up some time on those meetings and we will stop >>> going over time every time, hah. >>> >>> I will message Nathan asking him to set this regular meeting up via LF >>> so it's official. >>> >>> Best, >>> Patrick >>> >>> >>> On Wed, Jan 3, 2024 at 5:56 AM Juraj Linkeš <juraj.linkes@pantheon.tech> >>> wrote: >>> >>>> The best times for me are 14:00 UTC either on Monday or Wednesday. The >>>> 15:00 UTC times collide with my calls, but it's not a big deal if I miss >>>> them every other week. >>>> >>>> Juraj >>>> >>>> On Wed, Jan 3, 2024 at 12:08 AM Patrick Robb <probb@iol.unh.edu> wrote: >>>> >>>>> +Lincoln Lavoie <lylavoie@iol.unh.edu> >>>>> >>>>> Thanks for the feedback all. Adding Lincoln who I accidentally left >>>>> off the original email. I am on vacation this week but will let anyone else >>>>> respond this week and then set the regular meeting time next Monday. >>>>> >>>>> On Tue, Jan 2, 2024 at 4:56 PM Honnappa Nagarahalli < >>>>> Honnappa.Nagarahalli@arm.com> wrote: >>>>> >>>>>> 15:00 – 16:00 UTC Tuesdays works better for me. >>>>>> >>>>>> >>>>>> >>>>>> *From:* Paul Szczepanek <Paul.Szczepanek@arm.com> >>>>>> *Sent:* Tuesday, January 2, 2024 3:27 AM >>>>>> *To:* Patrick Robb <probb@iol.unh.edu>; Juraj Linkeš >>>>>> <juraj.linkes@pantheon.tech>; Honnappa Nagarahalli < >>>>>> Honnappa.Nagarahalli@arm.com>; Luca Vizzarro <Luca.Vizzarro@arm.com>; >>>>>> Yoan Picchi <yoan.picchi@foss.arm.com>; Jeremy Spewock < >>>>>> jspewock@iol.unh.edu>; thomas@monjalon.net; getelson@nvidia.com >>>>>> *Cc:* ci@dpdk.org >>>>>> *Subject:* Re: Regular DTS meeting scheduling >>>>>> >>>>>> >>>>>> >>>>>> 14:00-15:00 UTC Wednesdays looks great but all the times listed work >>>>>> for me, Yoan and Luca. >>>>>> >>>>>> >>>>>> ------------------------------ >>>>>> >>>>>> *From:* Patrick Robb <probb@iol.unh.edu> >>>>>> *Sent:* 22 December 2023 18:33 >>>>>> *To:* Juraj Linkeš <juraj.linkes@pantheon.tech>; Honnappa >>>>>> Nagarahalli <Honnappa.Nagarahalli@arm.com>; Paul Szczepanek < >>>>>> Paul.Szczepanek@arm.com>; Luca Vizzarro <Luca.Vizzarro@arm.com>; >>>>>> Yoan Picchi <yoan.picchi@foss.arm.com>; Jeremy Spewock < >>>>>> jspewock@iol.unh.edu>; thomas@monjalon.net <thomas@monjalon.net>; >>>>>> getelson@nvidia.com <getelson@nvidia.com> >>>>>> *Cc:* ci@dpdk.org <ci@dpdk.org> >>>>>> *Subject:* Regular DTS meeting scheduling >>>>>> >>>>>> >>>>>> >>>>>> Hello all DTS interested people, >>>>>> >>>>>> >>>>>> >>>>>> I'm looking to find a good timeslot for having DTS sync calls >>>>>> this Spring. Obviously we want to do it on the off weeks from the CI >>>>>> meetings, and we want to do it in the morning USA time so that it works for >>>>>> EU people too. >>>>>> >>>>>> >>>>>> >>>>>> Right now the timeslots I'm looking at are: >>>>>> >>>>>> >>>>>> >>>>>> 14:00-15:00 UTC Mondays >>>>>> >>>>>> 15:00-16:00 UTC Mondays >>>>>> >>>>>> 14:00-15:00 UTC Wednesdays >>>>>> >>>>>> 15:00-16:00 UTC Wednesdays >>>>>> >>>>>> >>>>>> >>>>>> All else being equal, Wednesdays are probably best, as it allows for >>>>>> better spacing between CI meetings, but we'll do whatever works for the >>>>>> most people. Please feel free to indicate your availability! >>>>>> >>>>>> >>>>>> >>>>>> Best, >>>>>> >>>>>> Patrick >>>>>> IMPORTANT NOTICE: The contents of this email and any attachments are >>>>>> confidential and may also be privileged. If you are not the intended >>>>>> recipient, please notify the sender immediately and do not disclose the >>>>>> contents to any other person, use it for any purpose, or store or copy the >>>>>> information in any medium. Thank you. >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Patrick Robb >>>>> >>>>> Technical Service Manager >>>>> >>>>> UNH InterOperability Laboratory >>>>> >>>>> 21 Madbury Rd, Suite 100, Durham, NH 03824 >>>>> >>>>> www.iol.unh.edu >>>>> >>>>> >>>>> >>> >>> >> > > -- > > Patrick Robb > > Technical Service Manager > > UNH InterOperability Laboratory > > 21 Madbury Rd, Suite 100, Durham, NH 03824 > > www.iol.unh.edu > > > -- Patrick Robb Technical Service Manager UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 www.iol.unh.edu [-- Attachment #2: Type: text/html, Size: 18824 bytes --]
[-- Attachment #1: Type: text/plain, Size: 1901 bytes --] Hello, This is a reminder that the new DTS Meeting Series for DPDK begins today, Wed. Jan 17, 2024 at 7am Pacific/10am Eastern. LFX login information is listed below. We hope to see you there. Thanks, Nathan Nathan C. Southern, Senior Project Coordinator Data Plane Development Kit The Linux Foundation 248.835.4812 (mobile) nsouthern@linuxfoundation.org You have been invited to a recurring meeting for Data Plane Development Kit (DPDK) Meeting to guide and oversee the DTS work ramp up in the UNH Community Lab Meeting minutes: https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing <https://www.google.com/url?q=https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp%3Dsharing&sa=D&source=calendar&ust=1705901867879192&usg=AOvVaw2fDoUTKVv6NBvElRxESm7R> Ways to join meeting: 1. Join from PC, Mac, iPad, or Android https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password=66221d21-9c8b-4ccd-bc34-e56f8afafab2 <https://www.google.com/url?q=https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password%3D66221d21-9c8b-4ccd-bc34-e56f8afafab2&sa=D&source=calendar&ust=1705901867879192&usg=AOvVaw3LvFcx7ulRAjW-dl3kBkRC> 2. Join via audio One tap mobile: US: +12532158782,,96185056077# or +13462487799,,96185056077 Or dial: US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592 or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free) Canada: +1 647 374 4685 or +1 647 558 0588 or +1 778 907 2071 or +1 204 272 7920 or +1 438 809 7799 or +1 587 328 1099 or 855 703 8985 (Toll Free) Meeting ID: 96185056077 Meeting Passcode: 004462 International numbers: https://zoom.us/u/alwnPIaVT <https://www.google.com/url?q=https://zoom.us/u/alwnPIaVT&sa=D&source=calendar&ust=1705901867879192&usg=AOvVaw2jCkpckQ2207VhbtmF_wfH> [-- Attachment #2: Type: text/html, Size: 8664 bytes --]
[-- Attachment #1: Type: text/plain, Size: 6844 bytes --] This is just a reminder that the first meeting is tomorrow at 15:00 UTC. I have a one time conflict and won't be there, but I'll see yall at the subsequent meetings! Let me know if anyone wasn't included on the invite list. And I'll include the meeting info below for anyone without an invite. I asked Juraj if he would drive the topics and transcribe minutes, but if anyone else wants to volunteer that works too! You have been invited to a recurring meeting for Data Plane Development Kit (DPDK) Meeting to guide and oversee the DTS work ramp up in the UNH Community Lab Meeting minutes: https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing <https://www.google.com/url?q=https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp%3Dsharing&sa=D&source=calendar&ust=1705876800213036&usg=AOvVaw0_8FVnCEhKsKvt1hhQZ1kg> Ways to join meeting: 1. Join from PC, Mac, iPad, or Android https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password=66221d21-9c8b-4ccd-bc34-e56f8afafab2 <https://www.google.com/url?q=https://zoom-lfx.platform.linuxfoundation.org/meeting/96185056077?password%3D66221d21-9c8b-4ccd-bc34-e56f8afafab2&sa=D&source=calendar&ust=1705876800213036&usg=AOvVaw3qMfnso6MRPRbMDWld4GO7> 2. Join via audio One tap mobile: US: +12532158782,,96185056077# or +13462487799,,96185056077 Or dial: US: +1 253 215 8782 or +1 346 248 7799 or +1 669 900 6833 or +1 301 715 8592 or +1 312 626 6799 or +1 646 374 8656 or 877 369 0926 (Toll Free) or 855 880 1246 (Toll Free) Canada: +1 647 374 4685 or +1 647 558 0588 or +1 778 907 2071 or +1 204 272 7920 or +1 438 809 7799 or +1 587 328 1099 or 855 703 8985 (Toll Free) Meeting ID: 96185056077 Meeting Passcode: 004462 On Tue, Jan 9, 2024 at 10:13 AM Patrick Robb <probb@iol.unh.edu> wrote: > So that's 15:00 UTC on Wednesday on the same week as CI meetings, so it > should start 1/17. I'll have Nathan use the same invite list as he is using > for CI testing. I can typically make that time, but have a conflict for > next Wednesday specifically, so I won't be able to take notes for the > minutes. Someone else will have to volunteer. We can start using the doc > below. > > > https://docs.google.com/document/d/1pG_NGuwYgPuovwIfhvcs9u8PNYIJuInsFr0GeTUIU4k/edit?usp=sharing > > On Tue, Jan 9, 2024 at 9:59 AM Patrick Robb <probb@iol.unh.edu> wrote: > >> Okay, so it sounds like 15:00 UTC on the off week of the tech board >> meetings is one decent option, as most people can make that one. Sorry >> Honnappa, I know the 15:00-16:00 timeslot doesn't work for at least 1 >> person already without having polled people on it, so I don't think that's >> worth pursuing. >> >> So the meeting should be happening in the same week as CI testing calls. >> Hopefully that will free up some time on those meetings and we will stop >> going over time every time, hah. >> >> I will message Nathan asking him to set this regular meeting up via LF so >> it's official. >> >> Best, >> Patrick >> >> >> On Wed, Jan 3, 2024 at 5:56 AM Juraj Linkeš <juraj.linkes@pantheon.tech> >> wrote: >> >>> The best times for me are 14:00 UTC either on Monday or Wednesday. The >>> 15:00 UTC times collide with my calls, but it's not a big deal if I miss >>> them every other week. >>> >>> Juraj >>> >>> On Wed, Jan 3, 2024 at 12:08 AM Patrick Robb <probb@iol.unh.edu> wrote: >>> >>>> +Lincoln Lavoie <lylavoie@iol.unh.edu> >>>> >>>> Thanks for the feedback all. Adding Lincoln who I accidentally left off >>>> the original email. I am on vacation this week but will let anyone else >>>> respond this week and then set the regular meeting time next Monday. >>>> >>>> On Tue, Jan 2, 2024 at 4:56 PM Honnappa Nagarahalli < >>>> Honnappa.Nagarahalli@arm.com> wrote: >>>> >>>>> 15:00 – 16:00 UTC Tuesdays works better for me. >>>>> >>>>> >>>>> >>>>> *From:* Paul Szczepanek <Paul.Szczepanek@arm.com> >>>>> *Sent:* Tuesday, January 2, 2024 3:27 AM >>>>> *To:* Patrick Robb <probb@iol.unh.edu>; Juraj Linkeš >>>>> <juraj.linkes@pantheon.tech>; Honnappa Nagarahalli < >>>>> Honnappa.Nagarahalli@arm.com>; Luca Vizzarro <Luca.Vizzarro@arm.com>; >>>>> Yoan Picchi <yoan.picchi@foss.arm.com>; Jeremy Spewock < >>>>> jspewock@iol.unh.edu>; thomas@monjalon.net; getelson@nvidia.com >>>>> *Cc:* ci@dpdk.org >>>>> *Subject:* Re: Regular DTS meeting scheduling >>>>> >>>>> >>>>> >>>>> 14:00-15:00 UTC Wednesdays looks great but all the times listed work >>>>> for me, Yoan and Luca. >>>>> >>>>> >>>>> ------------------------------ >>>>> >>>>> *From:* Patrick Robb <probb@iol.unh.edu> >>>>> *Sent:* 22 December 2023 18:33 >>>>> *To:* Juraj Linkeš <juraj.linkes@pantheon.tech>; Honnappa Nagarahalli >>>>> <Honnappa.Nagarahalli@arm.com>; Paul Szczepanek < >>>>> Paul.Szczepanek@arm.com>; Luca Vizzarro <Luca.Vizzarro@arm.com>; Yoan >>>>> Picchi <yoan.picchi@foss.arm.com>; Jeremy Spewock < >>>>> jspewock@iol.unh.edu>; thomas@monjalon.net <thomas@monjalon.net>; >>>>> getelson@nvidia.com <getelson@nvidia.com> >>>>> *Cc:* ci@dpdk.org <ci@dpdk.org> >>>>> *Subject:* Regular DTS meeting scheduling >>>>> >>>>> >>>>> >>>>> Hello all DTS interested people, >>>>> >>>>> >>>>> >>>>> I'm looking to find a good timeslot for having DTS sync calls >>>>> this Spring. Obviously we want to do it on the off weeks from the CI >>>>> meetings, and we want to do it in the morning USA time so that it works for >>>>> EU people too. >>>>> >>>>> >>>>> >>>>> Right now the timeslots I'm looking at are: >>>>> >>>>> >>>>> >>>>> 14:00-15:00 UTC Mondays >>>>> >>>>> 15:00-16:00 UTC Mondays >>>>> >>>>> 14:00-15:00 UTC Wednesdays >>>>> >>>>> 15:00-16:00 UTC Wednesdays >>>>> >>>>> >>>>> >>>>> All else being equal, Wednesdays are probably best, as it allows for >>>>> better spacing between CI meetings, but we'll do whatever works for the >>>>> most people. Please feel free to indicate your availability! >>>>> >>>>> >>>>> >>>>> Best, >>>>> >>>>> Patrick >>>>> IMPORTANT NOTICE: The contents of this email and any attachments are >>>>> confidential and may also be privileged. If you are not the intended >>>>> recipient, please notify the sender immediately and do not disclose the >>>>> contents to any other person, use it for any purpose, or store or copy the >>>>> information in any medium. Thank you. >>>>> >>>> >>>> >>>> -- >>>> >>>> Patrick Robb >>>> >>>> Technical Service Manager >>>> >>>> UNH InterOperability Laboratory >>>> >>>> 21 Madbury Rd, Suite 100, Durham, NH 03824 >>>> >>>> www.iol.unh.edu >>>> >>>> >>>> >> >> > -- Patrick Robb Technical Service Manager UNH InterOperability Laboratory 21 Madbury Rd, Suite 100, Durham, NH 03824 www.iol.unh.edu [-- Attachment #2: Type: text/html, Size: 16047 bytes --]
[-- Attachment #1: Type: text/plain, Size: 1333 bytes --] Hi all, On the Community Lab test beds I have noticed something interesting about the (old) DTS framework (NOTE: NOT the current dts framework rewrite effort). We have begun seeing intermittent timeouts during the DTS execution (specifically the DPDK compile command) on the DUT, almost exclusively when doing 22.11 LTS testing, but also intermittently on main. I'm not sure what the cause is, but most likely the timeout was set some time ago and additions to DPDK and backporting to LTS releases has gradually increased the compile time over time making the old timeout value insufficient on some slower systems. For context, the current timeout for compiling DPDK is set to be 30 minutes, but we have started to see builds on some systems consistently require a few minutes more than that for the compilation to complete. Does this sound reasonable to you all? The compile timeout is not provided via config file, but is rather hard-coded in /framework/dpdk_project.py. So, for now we have patched the DTS we are running. I am willing to submit a patch to the DTS project making this change, but I know the DTS project is without a maintainer right now. Does anyone know whether (as discussed at the previous DPDK-CI meeting) there will be a final round(s) of patches merged for the old DTS project? Thank you, Jeremy Spewock [-- Attachment #2: Type: text/html, Size: 1694 bytes --]