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 B724B45506; Thu, 27 Jun 2024 22:43:07 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id AF7CC40E28; Thu, 27 Jun 2024 22:43:07 +0200 (CEST) Received: from mail-oa1-f49.google.com (mail-oa1-f49.google.com [209.85.160.49]) by mails.dpdk.org (Postfix) with ESMTP id 850B84067A for ; Thu, 27 Jun 2024 22:43:06 +0200 (CEST) Received: by mail-oa1-f49.google.com with SMTP id 586e51a60fabf-2598abc6848so969814fac.0 for ; Thu, 27 Jun 2024 13:43:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1719520986; x=1720125786; darn=dpdk.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=pwrvL9JV3TU17Wt6C4T7HVcu5jgztSM/Pkd63k0vlxc=; b=KbSzxNCfUpdWVS4uB3SNmdEEA/ruueH8R2Pqeoft5CPWNtAikNLdew3aQwrL9s4G2+ 4obkvRaFIwS5Ak2s4kvqxZfgxWRPfSZD+NLjwgao0U8oOfuqERxIITXAL6/MEjPTibVD ySVo2NhgZVPMXXuEFEysFRomEzkV6NOe/yzbE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719520986; x=1720125786; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=pwrvL9JV3TU17Wt6C4T7HVcu5jgztSM/Pkd63k0vlxc=; b=n3SJ/z+lwgxw91cEYN7H2ZLy1JeQaONIgDPzkWTKp8dJx6GQ+u+5dSnbvJSdGmQ62+ oBVpDJknOyUlKE/tOEzDWtEeWGUUOxB+mLqQo332cTKP46GIdBS6ExteTR6+gOoU7rWM cqDvtA2RSLM8RN/7+ZxzAR4eYFncpmp+e6m/IQErkMmngkmXoXkMmAufXe2co2OzT7dE rjfqoNVE+OidsQb2DnkWlKSNjeniu2eCAcsWuVL88IRpk+6L7sYF9zs+2hv2PCfgPOMF 2HaB+rH3qMCLZoGSSlRcm4tXfYqBBq78wLdO2mmUDAyR81WYHZnPJ+2ljbpYoPexmhXt tU9Q== X-Gm-Message-State: AOJu0YwFQvL1RqWfOrAo/RkGJWcwczjN8vP4IXwTrhwG5bbkExH+xWsV JieaI14tZ95ZHaxLmKmjHVjGuI28SJZWbBd+UoqsPbPkpIMqL2/YA97NBcH0wXztUEmKgZtZ8Rj N9orsm1PytL6sJit5qaWDnKB6KV//rJeW2r6Pug== X-Google-Smtp-Source: AGHT+IHIMY3XXlPmrBXWDhEG/QsfxSQSlqHC1zDOEUS2XBeXLq+AZnPo90dcLuz7hYYydyLYft+gPns4OMngkQZbz50= X-Received: by 2002:a05:6870:9a0b:b0:25c:b030:d07e with SMTP id 586e51a60fabf-25d731a0460mr1312974fac.3.1719520985823; Thu, 27 Jun 2024 13:43:05 -0700 (PDT) MIME-Version: 1.0 From: Patrick Robb Date: Thu, 27 Jun 2024 16:42:55 -0400 Message-ID: Subject: Testpmd usage in new DTS To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" Cc: dts@dpdk.org, dev , Luca Vizzarro , Paul Szczepanek , Jeremy Spewock , Dean Marx , Nicholas Pratte , =?UTF-8?Q?Juraj_Linke=C5=A1?= , David Marchand Content-Type: text/plain; charset="UTF-8" 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 Hi Thomas, Last November when we chatted in tech board about 2024 DTS goals, you said testpmd should be the primary tool used to drive the testsuites, and that if testpmd was missing some support for any DPDK features we want to test in DTS, then the support should be added into testpmd. So, we have recently been ramping up writing Ethernet API tests, and have done it only with testpmd so far based on this understanding. It seems like a good approach. Today we discussed in the CI meeting whether we should port over the l2fwd test, which is a test existing in the "old" DTS framework, based on the l2fwd sample app. For bringing this test coverage to new DTS, I think the correct approach is to write a testsuite which validates the same l2 forwarding functions, but using testpmd app instead of l2fwd app. I think this aligns with your expectation of driving testpmd usage in new DTS, but let me know if I have the wrong idea. So does this sound fine to you? And a second thing I want to raise which is tangentially related is I guess in the future we will have to determine what other apps can be used for tests which can't run from testpmd. I.e. right now at UNH lab we are running cryptodev tests on an Intel Quickassist 8970 card on our ARM server, and that test runs from an old DTS testsuite based on dpdk-test-cryptodev-perf. I'm guessing usage of such applications which have extensive support not existing in testpmd will be permitted at some point. It's fairly forward looking as we are really focused on ethdev work currently, but I figured I'd bring it up now.