From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/core Bug 1853] Comment about /dev/zero in eal_common_memory.c is obsolete
Date: Thu, 18 Dec 2025 13:42:11 +0000 [thread overview]
Message-ID: <bug-1853-3@http.bugs.dpdk.org/> (raw)
http://bugs.dpdk.org/show_bug.cgi?id=1853
Bug ID: 1853
Summary: Comment about /dev/zero in eal_common_memory.c is
obsolete
Product: DPDK
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: marcel@telka.sk
Target Milestone: ---
This comment is in lib/eal/common/eal_common_memory.c:
/*
* Try to mmap *size bytes in /dev/zero. If it is successful, return the
* pointer to the mmap'd area and keep *size unmodified. Else, retry
* with a smaller zone: decrease *size by hugepage_sz until it reaches
* 0. In this case, return NULL. Note: this function returns an address
* which is a multiple of hugepage size.
*/
Unfortunately, the comment is no longer accurate. The mmap-ing of *size bytes
in /dev/zero has been removed in April 2018 and since that the implementation
is different. The comment should be updated to reflect the current code.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2025-12-18 13:42 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-1853-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.