From: 郭春霞 <cx.guo@samsung.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: 张士亚 <sy0705.zhang@samsung.com>, 金明 <ming83.jin@samsung.com>,
"SRC-B Security" <bstsecurity@samsung.com>
Subject: Inquiry About DPDK's Roadmap for Dynamic CPU Scaling Support
Date: Fri, 28 Mar 2025 12:37:31 +0900 [thread overview]
Message-ID: <20250328033731epcms5p1393d177ee4de90debad11e9578e758f9@epcms5p1> (raw)
In-Reply-To: <CGME20250328033731epcms5p1393d177ee4de90debad11e9578e758f9@epcms5p1>
[-- Attachment #1: Type: text/html, Size: 25870 bytes --]
[-- Attachment #2: Type: image/png, Size: 15092 bytes --]
[-- Attachment #3: Type: image/png, Size: 22957 bytes --]
next parent reply other threads:[~2025-04-08 11:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250328033731epcms5p1393d177ee4de90debad11e9578e758f9@epcms5p1>
2025-03-28 3:37 ` 郭春霞 [this message]
2025-04-08 13:27 ` Stephen Hemminger
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=20250328033731epcms5p1393d177ee4de90debad11e9578e758f9@epcms5p1 \
--to=cx.guo@samsung.com \
--cc=bstsecurity@samsung.com \
--cc=dev@dpdk.org \
--cc=ming83.jin@samsung.com \
--cc=sy0705.zhang@samsung.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).