From: Patrick Robb <probb@iol.unh.edu>
To: "Brandes, Shai" <shaibran@amazon.com>
Cc: ci@dpdk.org, Aaron Conole <aconole@redhat.com>,
Luca Vizzarro <Luca.Vizzarro@arm.com>,
Dean Marx <dmarx@iol.unh.edu>,
Andrew Bailey <abailey@iol.unh.edu>
Subject: AWS EC2 ENA instance for a new DTS branch?
Date: Mon, 18 Aug 2025 11:34:16 -0400 [thread overview]
Message-ID: <CAJvnSUBQqmLXn6UP1cqb96SCFfw4Uzu9voj3C=gS4Woy_XT0ew@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
Hi Shai,
I'm thinking about how we can get the DPDK DTS group broadly, and the
students at UNH, to start staging DTS for running in a cloud environment
(like AWS) during this release cycle, so that we can start running some of
the E2E testing DTS provides in this setting. I believe we will have time
for this during the 25.11 development period as our "normal" roadmap items
are progressing well.
Is there a way that you would/will be able to make an AWS EC2 instance with
ENA adapter(s) available to the DTS group so that we can begin to work on
some testpmd DPDK workloads / make a DTS branch for running DTS in this
environment? It seems like getting onto an EC2 instance and experimenting
there would be a logical first step.
If providing such an instance is problematic or time consuming to you for
any technical or bureaucratic reason, then I will ask internally in my lab
if I can have a small spend authorization for an AWS account and proceed in
that way.
Let me know what your thoughts are! Cheers.
[-- Attachment #2: Type: text/html, Size: 1179 bytes --]
reply other threads:[~2025-08-18 15:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJvnSUBQqmLXn6UP1cqb96SCFfw4Uzu9voj3C=gS4Woy_XT0ew@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=Luca.Vizzarro@arm.com \
--cc=abailey@iol.unh.edu \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=dmarx@iol.unh.edu \
--cc=shaibran@amazon.com \
/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).