DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>
Cc: <techboard@dpdk.org>
Subject: Tech Board Meeting Minutes - 2025-Apr-02
Date: Mon, 7 Apr 2025 13:47:47 +0100	[thread overview]
Message-ID: <Z_PJczJAn2Rp1iPS@bricha3-mobl1.ger.corp.intel.com> (raw)

TB Members Attending
---------------------
Aaron Conole
Bruce Richardson (chair)
Hemant Agrawal
Honnappa Nagarahalli
Jerin Jacob
Kevin Traynor
Maxime Coquelin
Morten Brørup
Stephen Hemminger
Thomas Monjalon

NOTE: The technical board meetings are on every second Wednesday at 3pm UTC.
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes

Next meeting will be on Wednesday 2025-Apr-17 @ 3pm UTC, and will be
chaired by Hemant.

Agenda Items
=============

Official Deprecation of Old Linux Distro Support
-------------------------------------------------

* RHEL 7 and Centos 7 are no longer supported by DPDK
  - Compiler version GCC 4.8.5 is too old to build DPDK
  - Need to officially announce that it is no longer supported for new
    DPDK releases
  - Will still be maintained by older LTS releases, e.g. 21.11, 22.11
  - [Action Item] Kevin to upstream doc patch for RHEL 7 support removal
* With removal of RHEL 7, RHEL 8 becomes the oldest distro version
  supported.
  - This uses compiler versions GCC 8.2 and Clang 7
  - [Action Item] Bruce to upstream doc patch to update our recommended
    compiler versions to these
* For minimum kernel version support:
  - Patrick confirmed that the lab has just added an image with the
    minimum supported kernel [4.19] on it for CI testing
  - DPDK core does not have a particular dependency on recent kernels,
    this is instead the oldest TESTED kernel version
  - Other components, e.g. drivers, may have more up-to-date kernel
    requirements
  - [Action Item] Stephen to do a patch to update the docs to clarify
    the above points
  
Events Update
--------------

Prague event
- Reminder to register for this event
- Preparations well underway - event "swag" all sorted :)
- Technical board will hold an in-person meeting the day before the
  conference

US Event - Santa Clara
- Planning is ongoing
- Event will take place Sept 17-18th

DPDK Support via Rust APIs
---------------------------

Following discussion on the mailing list (see thread @[1]), open
discussion was held on Rust support in DPDK.

Overview of some points raised:
- Concern over level of rust expertise in community and in Tech-board
- Want to ensure that rust support does not hold back the C project
  itself, or impose limits on which C features or compiler features
  can be used.
- Suggestion that rust code in DPDK repository itself should be kept to
  an absolute minimum
  - rust examples potentially in a separate repository
- Any rust support should not just be a bindgen wrapper around DPDK:
  - been done many times before, value of that alone is questionable
  - desire expressed to have a "rustic" or rust-style set of APIs not
    just thin layer over C APIs
  - From mailing list discussion, seems consensus on having low-level
    API crate and higher-level API crate
- Exposing DPDK APIs officially via rust seen as an expansion of scope
  of DPDK project
  - there is value in having maintained "official" rust APIs from DPDK
    project
- Discussion held over the scope of DPDK exposed via rust APIs
  - limiting scope of what is exposed can reduce risk of C code breaking
    Rust code, and reduce maintenance burden
  - exposing more APIs via rust obviously increases what can be done by
    end-users
    - but problematic if only exposed in low-level C-style bindings
      rather than any higher-level crate
  - suggestion to have the bindgen-exposed APIs limited by what is
    necessary for the higher-level APIs
- More prototyping is likely necessary
- No conclusions reached at this point. Discussion will continue on-list.
 

[1] https://inbox.dpdk.org/dev/20250306133713.393057-1-getelson@nvidia.com/

                 reply	other threads:[~2025-04-07 12:47 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=Z_PJczJAn2Rp1iPS@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --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).