From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: techboard@dpdk.org
Subject: Minutes of DPDK Technical Board Meeting, 2024-04-03
Date: Wed, 24 Apr 2024 17:24:14 +0200 [thread overview]
Message-ID: <9317330.rMLUfLXkoz@thomas> (raw)
Members Attending: 10/11
- Aaron Conole
- Bruce Richardson
- Hemant Agrawal
- Honnappa Nagarahalli
- Kevin Traynor
- Konstantin Ananyev
- Maxime Coquelin
- Morten Brørup
- Stephen Hemminger
- Thomas Monjalon (Chair)
NOTE: The Technical Board meetings take place every second Wednesday at 3 pm UTC
on https://zoom-lfx.platform.linuxfoundation.org/meeting/96459488340?password=d808f1f6-0a28-4165-929e-5a5bcae7efeb
Meetings are public, and DPDK community members are welcome to attend.
Agenda and minutes can be found at http://core.dpdk.org/techboard/minutes
1/ MSVC
Work to be able to compile DPDK with MSVC is progressing.
Regarding the tooling, UNH CI is testing MSVC in Windows Server 2022 job.
There was an ask for GHA job building with MSVC.
Example:
https://github.com/danielzsh/spark/blob/master/.github/workflows/compile.yml
We should not break MSVC compilation for enabled libraries.
When creating a new library, we should require to allow MSVC where it makes sense.
Some guidelines could be added in doc/guides/contributing/design.rst
2/ function inlining
There are pros and cons for function inlining.
There should not be inlining in control path functions.
Inlining should be avoided in public headers because of ABI compatibility issue
and structures being exported because of inline requirement.
Inlining should be used with care, with benchmarks as a proof of efficiency.
Having too much inlining will have a drawback on instruction cache,
that's why we should justify any new usage of inline.
Note that the same recommendations apply with the use of prefetch and likely/unlikely.
next reply other threads:[~2024-04-24 15:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 15:24 Thomas Monjalon [this message]
2024-04-24 17:25 ` Morten Brørup
2024-04-24 19:10 ` Thomas Monjalon
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=9317330.rMLUfLXkoz@thomas \
--to=thomas@monjalon.net \
--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).