From: Mykola Kostenok <mko-plv@napatech.com>
To: "ci@dpdk.org" <ci@dpdk.org>
Cc: "aconole@redhat.com" <aconole@redhat.com>,
"probb@iol.unh.edu" <probb@iol.unh.edu>,
"lylavoie@iol.unh.edu" <lylavoie@iol.unh.edu>,
Maksym Kovaliov <mak-plv@napatech.com>,
Christian Koue Muf <ckm@napatech.com>,
Rasmus Carlson <rc@napatech.com>,
Vitalii Vrublevskyi <vvr-plv@napatech.com>
Subject: Napatech participation in DPDK. Open questions.
Date: Tue, 8 Aug 2023 09:34:16 +0000 [thread overview]
Message-ID: <AS1P190MB1797DA0E1228BF521A3D3EAC9F0DA@AS1P190MB1797.EURP190.PROD.OUTLOOK.COM> (raw)
[-- Attachment #1: Type: text/plain, Size: 772 bytes --]
Hi.
* If we follow the option of sending Napatech NIC to DPDK lab, how many servers are required for 1 testbed?
* How many testbeds are needed? Please confirm that no yearly fee is required, Just contribution in the form of servers.
* What is the procedure of upgrade of Napatech NIC software? Will Napatech engineers have access to the LAB? Or should Napatech share the instructions on how to upgrade NICs to the LAB engineers?
* Is a specific membership tier required for hardware inclusion in the lab?
* There was mentioned that governing board approval might be required to get new vendor into community LAB. How to get this approval?
* Who is right contact person for this and next questions?
Best regards,
Mykola Kostenok.
[-- Attachment #2: Type: text/html, Size: 8618 bytes --]
next reply other threads:[~2023-08-08 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 9:34 Mykola Kostenok [this message]
2023-08-08 13:54 ` Patrick Robb
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=AS1P190MB1797DA0E1228BF521A3D3EAC9F0DA@AS1P190MB1797.EURP190.PROD.OUTLOOK.COM \
--to=mko-plv@napatech.com \
--cc=aconole@redhat.com \
--cc=ci@dpdk.org \
--cc=ckm@napatech.com \
--cc=lylavoie@iol.unh.edu \
--cc=mak-plv@napatech.com \
--cc=probb@iol.unh.edu \
--cc=rc@napatech.com \
--cc=vvr-plv@napatech.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).