From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 980DC42355; Thu, 12 Oct 2023 16:47:01 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 90C31402BA; Thu, 12 Oct 2023 16:47:01 +0200 (CEST) Received: from mail-oo1-f50.google.com (mail-oo1-f50.google.com [209.85.161.50]) by mails.dpdk.org (Postfix) with ESMTP id 3E8BB4029F for ; Thu, 12 Oct 2023 16:47:00 +0200 (CEST) Received: by mail-oo1-f50.google.com with SMTP id 006d021491bc7-57b64731334so570068eaf.1 for ; Thu, 12 Oct 2023 07:47:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1697122019; x=1697726819; darn=dpdk.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=PgrKFqNfrVhnR55pf14iaP/ogcxnS6DYkTMmP0JuxEw=; b=ZAsNZQ/9ZUJs0gIV7okvKWqFmmaDnVOwc4+pDpUwPFF19FNrLoXkwqDsFNSyZWN5Et 4OpsbKPu3A1ElG2yLnqmNp83WcA5X2URR/wEZbCKcUjWi828YuNvhcFqOiH42Ycpufu6 1F+m6xABckm3hGZbRqtZ7Yv43EABGJo5zUIGw= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697122019; x=1697726819; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=PgrKFqNfrVhnR55pf14iaP/ogcxnS6DYkTMmP0JuxEw=; b=FS3V++WnVbASPpT+MENRnDVZI3I2WCkPcfHIxAHsOkeTYrHAG9QQvzIIPpHI0dH5EE e+yjcNwMJ+Dk/9BJNEF948sT/0DNGg0NPcCr38B4kZJq0M3Qu3AKGZRitIVBN682qA1A i31jTAU1nZuoB/Z7RU/xYSLIEaRzcGITYhUsmkAFPHVC4Lr16+d+BybCzXAMZp8Dpliz wrTBeVxBiL25P+LfcufFykQ9a+HzSXvxzpaFbtIgHsALPNVNwbn3BfeRiCznkdwT3XRp 2VCOJ5m8LTJAE3C5RqYMHXqVfT3MVfzI5pDCRcvTK1qciSRCg4clNyiRueTnIC9WRD+W nobg== X-Gm-Message-State: AOJu0Yy9IJW5TKXJ/EOhjZloK5unOiEvdNFChPeFo9Tl7Y9hvoO2vl6p 3vAGqDp5UOftf4/1mkfilX7T/ZkobPbQqy9SvB104HHlRf1E/pJrmwE= X-Google-Smtp-Source: AGHT+IEa/1M3XfyPJH7E0iRUUEiXafjKvawTIpFj/Q31Zg5B4q8QUVmtMx/ZplstUue4S7oegz1uNi490Dm1hTqj9S8= X-Received: by 2002:a4a:e5d2:0:b0:57d:e5e7:6d00 with SMTP id r18-20020a4ae5d2000000b0057de5e76d00mr21590611oov.6.1697122019295; Thu, 12 Oct 2023 07:46:59 -0700 (PDT) MIME-Version: 1.0 From: Patrick Robb Date: Thu, 12 Oct 2023 10:46:48 -0400 Message-ID: Subject: Community CI Meeting Minutes - October 12, 2023 To: ci@dpdk.org Cc: dts@dpdk.org Content-Type: multipart/alternative; boundary="00000000000019daa60607860384" X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org --00000000000019daa60607860384 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable October 12, 2023 ##################################################################### Attendees 1. Patrick Robb 2. David Marchand 3. Lincoln Lavoie 4. Aaron Conole 5. Paul Szczepanek 6. Ali Alnubani 7. Thomas Monjalon 8. Adam Hassick 9. Honnappa Nagarahalli 10. Juraj Linke=C5=A1 ##################################################################### Agenda 1. General Announcements 2. CI Status 3. DTS Improvements & Test Development 4. Any other business ##################################################################### Minutes =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D General Announcements * There will be a joint governing board and tech board meeting next Tuesday, related to 2024 work and contracts * There will be a section devoted to discussion about the proposal of adding an additional dedicated DTS developer at the Community Lab * This would entail improving the actual testing framework and integrating it into the DPDK repo, and also porting over testsuites/writing over testsuites * Aaron did merge some patches from UNH to the dpdk-ci repo: * Container template engine from Adam Hassick * Get_reruns.py regex script for collecting retest request labels from comments on patchwork API has been merged * Pw_maintainers_cli.py: There has been a v2 of this patch submitted, which resolves the initial concerns from Aaron and David * The patch from Bruce which allows you to set an env variable and skip a particular unit test from a suite is merged * Short term boon: unh can re-enable it=E2=80=99s arm64 unit testing * This arm64 EAL unit test issue has probably been fixed by David=E2= =80=99s patch (merged yesterday to mainline) which cleans up between unit tests. This has not likely hit subtrees yet, but subtree maintainers will likely rebase from main very soon because of rc1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D CI Status --------------------------------------------------------------------- UNH-IOL Community Lab * Nvidia testing: * Hardware Refresh * cx6-Lx NIC is now in production for performance testing, reporting to patchwork: https://mails.dpdk.org/archives/test-report/2023-October/477804.html * UNH is going to order an additional cx6-lx nic so that we can have 2 nics on the DUT and utilize only 1 port per nic instead of 2 (current approach) * CX7: installed in NVIDIA DUT server, and Intel tester TG server. * Need to aggregate info regarding any changes required for the system and send to Intel contacts * Do NOT install OFED - just need to use most recent distribution * Trex can run without ofed, but we will need to include a flag indicating we should run without ofed * This is ideal in Patrick=E2=80=99s opinion, since the TG nic = is on an Intel donated server, and I don=E2=80=99t want to disrupt their testing * Required TREX arg: --no-ofed-check * Are there functional testsuites which should be run on these cards? * There are internal conversations about what is most important to be tested, we will circle back on this later * Intel 8970 QAT Accelerator card: Dharmik from ARM is providing feedback on our setup so we can align with his * TS-Factory: * Does run on arm, so x86 and arm parity in testing should be achievable * Our setup =E2=80=9Cts-rig=E2=80=9D seems sound, and our results in ali= gnment with oktetlabs * Still need to setup the Jenkins scripts and Dashboard page (run on periodic basis) * We will deploy 4 environments (x86: xl710, cx5) and (ARM: xl710, cx5) * Apply patchset script: * We have a draft script which should be generic and can be upstreamed to dpdk-ci * Includes a small config file to track basic git-pw info needed for dpdk (pw api url, repo syntax (main vs /next/ trees), etc. * Tries to apply on the =E2=80=9Cpredicted tree=E2=80=9D from the scr= ipt first, then tries to apply on main * Depends on: not implemented yet, but we will try to implement via git-pw itself so we can contribute to that project. Or, if we run into any trouble we will fall back on implementing it directly in our apply script. * If there is more than one depends on patch in the commit message, we will attempt to apply =E2=80=9Ctop to bottom=E2=80=9D * Apply failures will be reported if we fail here * Marvell Octeon board: Still working with their support to get documentation, but they have approved our account request * We have a contact which runs DTS at their company now, who will help us on setup * John McNamara is the new Intel contact for UNH stuff * There is a new validation manager being onboarded who will be the contact long term --------------------------------------------------------------------- Intel Lab * Small hiccup recently over a testbed being powered off for a couple days --------------------------------------------------------------------- Loongarch Lab * Still working fine but no news --------------------------------------------------------------------- Github Actions * Still working on server migration plan, waiting on security audit internally. There is a testing environment up for the migration. There have been some delays on the systems getting moved, which has extended the timeline. * Final testing needed on the robot email based retesting framework support =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D DTS Improvements & Test Development * Dperf: We are asking him about L2 traffic * Scatter: Jeremy is bugfixing for this, and running it across a few NICs to verify the implementation is correct * He noticed that there wasn=E2=80=99t a step in the execution setup reb= inding the SUT interfaces from the os_driver to the dpdk driver, so he is going to submit a separate patch along with the scatter patch adding in this step * 23.11 patches are looking good, should be ready by the deadline * What should we work on for 24.03? * Paul: Before asking developers/maintainers to write testsuites we need to verify the framework is ready and tools in place to facilitate this (and it should be easy for developers) * The testpmd handler needs to be extended to facilitate the writing of all testsuites which will be required in dpdk * Need to make sure that we don=E2=80=99t need to explicitly update t= he python wrapper to support every new testpmd feature every time testpmd is updated. But we also need to facilitate easy of use for the wrapper, which might not mean directly passing to testpmd. It should be possible to support both (maybe override the level of abstraction only when needed). We can make this as dynamic as is needed to allow for complete use of testpmd features. * Currently EAL parameters and testpmd parameters are passed separately from the wrapper. * We need to verify logging/error reporting is up to snuff * Juraj wants to spend time researching what might we be missing in terms of what needs to be added before we are ready to go to the broader community and have them write testsuites. He will work on this once all 23.11 work is done. * Work on 1 testsuites per module in dpdk * Jeremy and Patrick will discuss what are some testsuites which could be ported over for the next release * Patrick will aggregate the dpdk testsuites run in the lab, and what we would like to run but does not work * Testbed config: we have a few values which we are not currently used * Build target has 5 values, only 2 are being used * Not using arch, os, and cpu. Having these values included comes from old DTS, but it may no longer be needed. They could be useful for cross compilation in the future, but we can remove now and re-add later if needed. We still probably won=E2=80=99t even need these values for cross compilation, since all we will need is to be able to reference the cross file. * Use_first_core: eliminate this option. New process should be like - if no lcore list is explicitly stated, dynamically select the cores, but always skip the first core. If lcore list is explicitly states, use the list! * Interactive session: currently only supporting ssh, do we want to support anything else (telnet?) * This might be required for IXIA TG * We can do this later if the community needs * How we use the word =E2=80=9Cexecution=E2=80=9D in DTS is confusing * When we say DTS execution, people will typically think of the entire dts run, but there are actually multiple dts executions within one DTS run, and this terminology is not intuitive for people coming in =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Any other business * Testing DPDK use in cloud platforms (aws, google cloud, etc) * Governing board has asked about the Community Lab setting this up, running it in 2024 * What use cases should be covered? Does anyone have any insight from cloud usage at your companies? * Honnappa: single core performance test would be good to run for cloud platforms * Honnappa: Running unit test cases in the cloud. In his experience he ran into issues running in the cloud due to race conditions in the unit tests. * Scalability testing. We focus on single core performance, but we need to move beyond that. Can we run l2/l3fwd on many cores * Virtio testcases (obviously important in cloud environments) * Next meeting is October 26, 2023 --00000000000019daa60607860384 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
October 12, 2023

##################################= ###################################
Attendees
1. Patrick Robb
2. D= avid Marchand
3. Lincoln Lavoie
4. Aaron Conole
5. Paul Szczepanek=
6. Ali Alnubani
7. Thomas Monjalon
8. Adam Hassick
9. Honnappa= Nagarahalli
10. Juraj Linke=C5=A1

##############################= #######################################
Agenda
1. General Announcemen= ts
2. CI Status
3. DTS Improvements & Test Development
4. Any = other business

#####################################################= ################
Minutes

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D
General Announcements
* There will be a joint gove= rning board and tech board meeting next Tuesday, related to 2024 work and c= ontracts
=C2=A0 =C2=A0* There will be a section devoted to discussion ab= out the proposal of adding an additional dedicated DTS developer at the Com= munity Lab
=C2=A0 =C2=A0* This would entail improving the actual testing= framework and integrating it into the DPDK repo, and also porting over tes= tsuites/writing over testsuites
* Aaron did merge some patches from UNH = to the dpdk-ci repo:
=C2=A0 =C2=A0* Container template engine from Adam = Hassick
=C2=A0 =C2=A0* Get_reruns.py regex script for collecting retest = request labels from comments on patchwork API has been merged
* Pw_maint= ainers_cli.py: There has been a v2 of this patch submitted, which resolves = the initial concerns from Aaron and David
* The patch from Bruce which a= llows you to set an env variable and skip a particular unit test from a sui= te is merged
=C2=A0 =C2=A0* Short term boon: unh can re-enable it=E2=80= =99s arm64 unit testing
=C2=A0 =C2=A0 =C2=A0 * This arm64 EAL unit test = issue has probably been fixed by David=E2=80=99s patch (merged yesterday to= mainline) which cleans up between unit tests. This has not likely hit subt= rees yet, but subtree maintainers will likely rebase from main very soon be= cause of rc1

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
CI Status

---------------------------------------------------= ------------------
UNH-IOL Community Lab
* Nvidia testing:
=C2=A0 = =C2=A0* Hardware Refresh
=C2=A0 =C2=A0 =C2=A0 * cx6-Lx NIC is now in pro= duction for performance testing, reporting to patchwork: https://mail= s.dpdk.org/archives/test-report/2023-October/477804.html
=C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0* UNH is going to order an additional cx6-lx nic so= that we can have 2 nics on the DUT and utilize only 1 port per nic instead= of 2 (current approach)
=C2=A0 =C2=A0 =C2=A0 * CX7: installed in NVIDIA= DUT server, and Intel tester TG server.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0* Need to aggregate info regarding any changes required for the syste= m and send to Intel contacts
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Do NOT = install OFED - just need to use most recent distribution
=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0* Trex can run without ofed, but we will need to includ= e a flag indicating we should run without ofed
=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 * This is ideal in Patrick=E2=80=99s opinion, since the T= G nic is on an Intel donated server, and I don=E2=80=99t want to disrupt th= eir testing
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 * Required TREX ar= g: --no-ofed-check
=C2=A0 =C2=A0 =C2=A0 * Are there functional testsuite= s which should be run on these cards?
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= * There are internal conversations about what is most important to be teste= d, we will circle back on this later
* Intel 8970 QAT Accelerator card: = Dharmik from ARM is providing feedback on our setup so we can align with hi= s
* TS-Factory:
=C2=A0 =C2=A0* Does run on arm, so x86 and arm parity= in testing should be achievable
=C2=A0 =C2=A0* Our setup =E2=80=9Cts-ri= g=E2=80=9D seems sound, and our results in alignment with oktetlabs
=C2= =A0 =C2=A0* Still need to setup the Jenkins scripts and Dashboard page (run= on periodic basis)
=C2=A0 =C2=A0* We will deploy 4 environments (x86: x= l710, cx5) and (ARM: xl710, cx5)
* Apply patchset script:
=C2=A0 =C2= =A0* We have a draft script which should be generic and can be upstreamed t= o dpdk-ci
=C2=A0 =C2=A0 =C2=A0 * Includes a small config file to track b= asic git-pw info needed for dpdk (pw api url, repo syntax (main vs /next/ t= rees), etc.
=C2=A0 =C2=A0 =C2=A0 * Tries to apply on the =E2=80=9Cpredi= cted tree=E2=80=9D from the script first, then tries to apply on main
= =C2=A0 =C2=A0 =C2=A0 * Depends on: not implemented yet, but we will try to = implement via git-pw itself so we can contribute to that project. Or, if we= run into any trouble we will fall back on implementing it directly in our = apply script.
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* If there is more than= one depends on patch in the commit message, we will attempt to apply =E2= =80=9Ctop to bottom=E2=80=9D
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Apply = failures will be reported if we fail here
* Marvell Octeon board: Still = working with their support to get documentation, but they have approved our= account request
=C2=A0 =C2=A0* We have a contact which runs DTS at thei= r company now, who will help us on setup
* John McNamara is the new Inte= l contact for UNH stuff
=C2=A0 =C2=A0* There is a new validation manager= being onboarded who will be the contact long term
=C2=A0 =C2=A0
----= -----------------------------------------------------------------
Intel = Lab
* Small hiccup recently over a testbed being powered off for a coupl= e days

-------------------------------------------------------------= --------
Loongarch Lab
* Still working fine but no news

------= ---------------------------------------------------------------
Github A= ctions
* Still working on server migration plan, waiting on security aud= it internally. There is a testing environment up for the migration. There h= ave been some delays on the systems getting moved, which has extended the t= imeline.
* Final testing needed on the robot email based retesting frame= work support

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D
DTS Improvements & Test Development
* Dperf: We are asking hi= m about L2 traffic
* Scatter: Jeremy is bugfixing for this, and running = it across a few NICs to verify the implementation is correct
=C2=A0 =C2= =A0* He noticed that there wasn=E2=80=99t a step in the execution setup reb= inding the SUT interfaces from the os_driver to the dpdk driver, so he is g= oing to submit a separate patch along with the scatter patch adding in this= step
* 23.11 patches are looking good, should be ready by the deadline<= br>* What should we work on for 24.03?
=C2=A0 =C2=A0* Paul: Before askin= g developers/maintainers to write testsuites we need to verify the framewor= k is ready and tools in place to facilitate this (and it should be easy for= developers)
=C2=A0 =C2=A0* The testpmd handler needs to be extended to = facilitate the writing of all testsuites which will be required in dpdk
= =C2=A0 =C2=A0 =C2=A0 * Need to make sure that we don=E2=80=99t need to expl= icitly update the python wrapper to support every new testpmd feature every= time testpmd is updated. But we also need to facilitate easy of use for th= e wrapper, which might not mean directly passing to testpmd. It should be p= ossible to support both (maybe override the level of abstraction only when = needed). We can make this as dynamic as is needed to allow for complete use= of testpmd features.
=C2=A0 =C2=A0 =C2=A0 * Currently EAL parameters an= d testpmd parameters are passed separately from the wrapper.
=C2=A0 =C2= =A0* We need to verify logging/error reporting is up to snuff
=C2=A0 =C2= =A0* Juraj wants to spend time researching what might we be missing in term= s of what needs to be added before we are ready to go to the broader commun= ity and have them write testsuites. He will work on this once all 23.11 wor= k is done.
=C2=A0 =C2=A0* Work on 1 testsuites per module in dpdk
=C2= =A0 =C2=A0 =C2=A0 * Jeremy and Patrick will discuss what are some testsuite= s which could be ported over for the next release
=C2=A0 =C2=A0 =C2=A0 *= Patrick will aggregate the dpdk testsuites run in the lab, and what we wou= ld like to run but does not work
=C2=A0 =C2=A0* Testbed config: we have = a few values which we are not currently used
=C2=A0 =C2=A0 =C2=A0 * Buil= d target has 5 values, only 2 are being used
=C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0* Not using arch, os, and cpu. Having these values included comes fr= om old DTS, but it may no longer be needed. They could be useful for cross = compilation in the future, but we can remove now and re-add later if needed= . We still probably won=E2=80=99t even need these values for cross compilat= ion, since all we will need is to be able to reference the cross file.
= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0* Use_first_core: eliminate this option. = New process should be like - if no lcore list is explicitly stated, dynamic= ally select the cores, but always skip the first core. If lcore list is exp= licitly states, use the list!
=C2=A0 =C2=A0* Interactive session: curren= tly only supporting ssh, do we want to support anything else (telnet?)
= =C2=A0 =C2=A0 =C2=A0 * This might be required for IXIA TG
=C2=A0 =C2=A0 = =C2=A0 * We can do this later if the community needs
=C2=A0 =C2=A0* How = we use the word =E2=80=9Cexecution=E2=80=9D in DTS is confusing
=C2=A0 = =C2=A0 =C2=A0 * When we say DTS execution, people will typically think of t= he entire dts run, but there are actually multiple dts executions within on= e DTS run, and this terminology is not intuitive for people coming in
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Any other b= usiness
* Testing DPDK use in cloud platforms (aws, google cloud, etc)=C2=A0 =C2=A0* Governing board has asked about the Community Lab setting = this up, running it in 2024
=C2=A0 =C2=A0* What use cases should be cove= red? Does anyone have any insight from cloud usage at your companies?
= =C2=A0 =C2=A0 =C2=A0 * Honnappa: single core performance test would be good= to run for cloud platforms
=C2=A0 =C2=A0 =C2=A0 * Honnappa: Running uni= t test cases in the cloud. In his experience he ran into issues running in = the cloud due to race conditions in the unit tests.
=C2=A0 =C2=A0 =C2=A0= * Scalability testing. We focus on single core performance, but we need to= move beyond that. Can we run l2/l3fwd on many cores
=C2=A0 =C2=A0 =C2= =A0 * Virtio testcases (obviously important in cloud environments)
* Nex= t meeting is October 26, 2023
--00000000000019daa60607860384--