DPDK patches and discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "Techboard@dpdk.org" <techboard@dpdk.org>,
	"dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>
Subject: Re: Minutes of Techboard Meeting, 2024-01-10
Date: Tue, 16 Jan 2024 18:03:28 -0500	[thread overview]
Message-ID: <CAJvnSUDtm2fUJ-6aXQds2tDBbWbB97QOJ+=ab8=7SQk3Cb5E2g@mail.gmail.com> (raw)
In-Reply-To: <DBAPR08MB581405E7CF23732B8941B10C98732@DBAPR08MB5814.eurprd08.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1502 bytes --]

On Tue, Jan 16, 2024 at 11:45 AM 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.

[-- Attachment #2: Type: text/html, Size: 1886 bytes --]

      reply	other threads:[~2024-01-16 23:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-16 16:45 Honnappa Nagarahalli
2024-01-16 23:03 ` Patrick Robb [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJvnSUDtm2fUJ-6aXQds2tDBbWbB97QOJ+=ab8=7SQk3Cb5E2g@mail.gmail.com' \
    --to=probb@iol.unh.edu \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    --cc=techboard@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).