DPDK patches and discussions
 help / color / mirror / Atom feed
From: "wuchangsheng (C)" <wuchangsheng2@huawei.com>
To: "anatoly.burakov@intel.com" <anatoly.burakov@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"jiangheng (G)" <jiangheng14@huawei.com>,
	"Yanan (Euler)" <yanan@huawei.com>,
	"Suweifeng (Weifeng, EulerOS)" <suweifeng1@huawei.com>
Subject: [DPDK] heap memory fragmentation issue
Date: Tue, 18 Apr 2023 02:48:18 +0000	[thread overview]
Message-ID: <448c5b93631a4ef191b57efb10d9424f@huawei.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 638 bytes --]

ping



Hello:

  When using rte_malloc and rte_free to request and release memory repeatedly, the usage of large pages gradually increases.

Checking the relevant source code shows that memory requests and releases are started from the head of the freelist chain list of the heap. Memory fragmentation seems to result from this, which is considered because the memory recently released may be in the cache, and requesting this memory at the time of allocation may achieve higher performance?

How does the community consider the heap's memory fragmentation issue? Is there a future plan for memory fragmentation optimization?

[-- Attachment #2: Type: text/html, Size: 3422 bytes --]

             reply	other threads:[~2023-04-18  2:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-18  2:48 wuchangsheng (C) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-12  8:44 wuchangsheng (C)
2023-04-18 21:35 ` Dmitry Kozlyuk
2023-04-18 22:43   ` 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=448c5b93631a4ef191b57efb10d9424f@huawei.com \
    --to=wuchangsheng2@huawei.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=jiangheng14@huawei.com \
    --cc=suweifeng1@huawei.com \
    --cc=yanan@huawei.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).