dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2024-February-21
Date: Thu, 22 Feb 2024 20:57:32 +0100	[thread overview]
Message-ID: <616e2cb9-4aa6-4cd0-8c1c-78a3e4e9318a@redhat.com> (raw)

# Techboard attendees
- Bruce Richardson
- Honnappa Nagarahalli
- Jerin Jacob
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin (Chair)
- Morten Brørup
- Thomas Monjalon

# General information
- Next meeting will take place on March 6th, and will be chaired by 
Morten Brørup.

# Agenda
- Update on lab servers by Aaron
- Marketing updates by Ben

# Minutes
## Update about the UNH lab servers
- HW resources audit was requested
- Some of the servers are getting too old to provide good testing coverage.
   For example AVX-512 require fairly recent CPUs, or newer NICs require 
good enough PCIe.
- Suggestions to have AMD-based server, and questions about ARM-based 
servers in the lab.
- Regarding ARM, there is one Ampere server (Neoverse-N1) donated in 
2022 already. Is that enough?
- Other architectures like RISC-V or LoongArch are not present in the lab.
   Even though LoongSon provide their CI for LoongArch.
- AI: Aaron to start a mail thread to gather requirements.

## Marketing updates
- Ben met with Gal, Mark and Robin to review marketing strategy for 2024.
- One of the goals to have more cross-projects collaborations.
- Request help from the Technical Board to prospect for new members.
- Also calls for ideas for Code Challenge.


                 reply	other threads:[~2024-02-22 19:57 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=616e2cb9-4aa6-4cd0-8c1c-78a3e4e9318a@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=dev@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).