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 6510F438E7; Wed, 17 Jan 2024 00:03:41 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id DA44440A4B; Wed, 17 Jan 2024 00:03:40 +0100 (CET) Received: from mail-oa1-f41.google.com (mail-oa1-f41.google.com [209.85.160.41]) by mails.dpdk.org (Postfix) with ESMTP id B9BFA402A6 for ; Wed, 17 Jan 2024 00:03:39 +0100 (CET) Received: by mail-oa1-f41.google.com with SMTP id 586e51a60fabf-21086556f32so410634fac.3 for ; Tue, 16 Jan 2024 15:03:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iol.unh.edu; s=unh-iol; t=1705446219; x=1706051019; darn=dpdk.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=5ffSqSQ93eAiffNv70rYTeoPxt8BGh3COMMJB5iEvlU=; b=doMF1N3lEmt7PqzTx8Oqq668wMjf8QVXpdEpVAKF1HC06TpM7Xat4GIhYKZQ/kKXdi osoBp6nMt0/ucRaZUIc693BrA6y1Z6ZzmsORLm5d5YG64ekpSVIfYb15/JXngIsu1Hny xht9z3ZLuuYwAJkzBmE7GtmFryMLsY2dQqX6g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705446219; x=1706051019; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=5ffSqSQ93eAiffNv70rYTeoPxt8BGh3COMMJB5iEvlU=; b=iV7wNKttjOYgRQQkRZNPXv9wZOY+vDCMLG/5SMKfUX8+QfwqDW3SYN/zZ7LK8gZ9fR 1o57FCsrUaqWx0rgmKUZoR57IPLY+VUrneXk+bAiuQ/HJVbMH10YsKCEljwIVBlh/9Rv /qwoxQZh0oBMtIq06JTHx/g1WxbLeE9/y5gJ1fCanLjTzI0VfcX7EPsxCKXy/QYNoZvV mjEiLdWrvxiMvJfHKxHtKQYPZKq1zeNMvtf5uazfX+U1sErCB3S+d4kwTTuaOA6YD6wC wjeOihfFGvyq4gVeRVBQOqQTdNM10WrvgEyq1twwr2x2DrQwV4RKol+LJBouP/octGGU 9/tQ== X-Gm-Message-State: AOJu0YzSsNIU7R4j3w+WqIChaGhUy3XM4lEhke0Ua+smYp763mG150KU t6+KMq0FYK09SPFVfU5lfd02x/xUGUYvOtaugsHOUSNLimGl1w== X-Google-Smtp-Source: AGHT+IElWuSWCdTTEn1H2eyZnZeckEFUrEvbh/8fny5N7tZxYrKbGrMabtUNPDSXTFgoBN2OHHmAdZkyJZNHF4NOLes= X-Received: by 2002:a05:6870:709c:b0:202:ffd3:d2ce with SMTP id v28-20020a056870709c00b00202ffd3d2cemr9905049oae.85.1705446218833; Tue, 16 Jan 2024 15:03:38 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Patrick Robb Date: Tue, 16 Jan 2024 18:03:28 -0500 Message-ID: Subject: Re: Minutes of Techboard Meeting, 2024-01-10 To: Honnappa Nagarahalli Cc: "Techboard@dpdk.org" , "dev@dpdk.org" , nd Content-Type: multipart/alternative; boundary="0000000000000eb56c060f182481" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --0000000000000eb56c060f182481 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jan 16, 2024 at 11:45=E2=80=AFAM Honnappa Nagarahalli < Honnappa.Nagarahalli@arm.com> wrote: > > 3. How well does DPDK run on Hyperscaler environments? > - Can UNH take the task of running DPDK on Hyperscaler environments? UNH > seems to have lot of things already. > Sorry, I could not make techboard this week as I had a conflict from another project. I would like to reiterate that in principle an effective way to start addressing any gaps is to use testing to better understand the landscape as is. At the same time, yes this conversation did not reach maturity during 2023, so there aren't hyperscaler testing work items in 2024's Community Lab SOW. Written SOW items always have to take precedence, but we will continue to accept ad-hoc community requests like always, and engage in conversations for what's next for testing in DPDK. We had an email chain going with Robin/Honnappa about the most needed test coverage in this space, etc. but it died out. I remember Honnappa mentioning the importance of measuring multi core scalability performance, running l2fwd l3fwd sample apps etc. I think Robin may host some calls in 2024 to take feedback on this. We would still need a plan on funding for the cloud instances used, list of vNICs to provide testing coverage for, a test plan, etc. So, realistically today we are very far off, but if the conversation on this continues to develop, we can engage and define better if/how the Community Lab could play a role. --0000000000000eb56c060f182481 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Tue, Jan 16, 2024 at 11:45=E2=80= =AFAM Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com> wrote:

3. How well does DPDK run on Hyperscaler environments?
- Can UNH take the task of running DPDK on Hyperscaler environments? UNH se= ems to have lot of things already.

Sorr= y, I could not make techboard=C2=A0this week as I had a conflict from anoth= er project. I would like to reiterate=C2=A0that in principle an effective w= ay to start addressing=C2=A0any gaps is to use testing to better understand= the landscape as is. At the same time, yes this conversation did not reach= maturity during 2023, so there aren't hyperscaler testing work items i= n 2024's Community Lab SOW. Written SOW items always have=C2=A0to take = precedence, but we will continue to accept ad-hoc community requests like a= lways, and engage in conversations for what's next for testing in DPDK.=

We had an email chain going with Robin/Honnappa a= bout the most needed test coverage in this space, etc. but it died out. I r= emember Honnappa mentioning the=C2=A0importance of measuring multi core sca= lability performance, running l2fwd l3fwd sample apps etc. I think Robin ma= y host some calls in 2024 to take feedback on this. We would still need a p= lan on funding for the cloud instances used, list of vNICs to provide testi= ng coverage for, a test plan, etc. So, realistically today we are very far = off, but if the conversation on this continues to develop, we can engage an= d define better if/how the Community Lab could play a role.

<= /div>
=C2=A0
--0000000000000eb56c060f182481--