From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/DTS Bug 1577] dts: Request for memory usage test in CI
Date: Wed, 13 Nov 2024 16:20:57 +0000 [thread overview]
Message-ID: <bug-1577-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1582 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1577
Bug ID: 1577
Summary: dts: Request for memory usage test in CI
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: DTS
Assignee: dev@dpdk.org
Reporter: probb@iol.unh.edu
CC: juraj.linkes@pantheon.tech, probb@iol.unh.edu
Target Milestone: ---
On 11/13/24 Tech board discussed the idea of tracking hugepage memory usage for
EAL bringup and basic DPDK workloads for per patch CI testing. Ideally UNH
could track a baseline for each DPDK tree, and then for per patch testing
compare the baseline for the tree a patch is applied on with the memory usage
test result for that patch.
Testcases would be:
1. Start testpmd (EAL starts) and check memory usage.
2. Start some basic l2/l3 forwarding and check memory usage during.
3. (possible) Create flow rules for a device, check memory usage.
4. etc.
Prereqs to adding this test:
1. Add a runtime command to testpmd which will return hugepage memory usage.
Other notes:
1. UNH would need to track tree memory usage for each device/driver, as we can
expect usage will not be consistent across devices. In principle it is similar
to how UNH stores performance baselines for NIC/tree combinations right now, so
no DB schema updates should be required.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3523 bytes --]
reply other threads:[~2024-11-13 16:20 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=bug-1577-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).