From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A63AA4582F; Wed, 21 Aug 2024 12:57:09 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 41D9740E44; Wed, 21 Aug 2024 12:57:09 +0200 (CEST) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id A744B4003C for ; Wed, 21 Aug 2024 12:57:07 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 89CCB45830; Wed, 21 Aug 2024 12:57:07 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [DPDK/core Bug 1525] dpdk mempool creation is resulting into lot of memory getting wasted Date: Wed, 21 Aug 2024 10:57:07 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: core X-Bugzilla-Version: 20.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: sandipchhikara@gmail.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17242378270.b0eCCD2.1847472 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17242378270.b0eCCD2.1847472 Date: Wed, 21 Aug 2024 12:57:07 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1525 Bug ID: 1525 Summary: dpdk mempool creation is resulting into lot of memory getting wasted Product: DPDK Version: 20.11 Hardware: x86 OS: Linux Status: UNCONFIRMED Severity: major Priority: Normal Component: core Assignee: dev@dpdk.org Reporter: sandipchhikara@gmail.com Target Milestone: --- We are using rte_mempool_op_populate_helper for creating dpdk mempool. Mem= ory is allocated from 1GB huge page and passed to this function. It is observed that rte_mempool_op_populate_helper function is calculating page size as 4K and as MEMPOOL_F_NO_IOVA_CONTIG is not specified, so it don't place objects across pages resulting into lot of memory wastage and creation of pool whic= h is lesser in size then required. rte_mempool_op_calc_mem_size_default is used to calculate how much memory is required for the pool.=20 If it is user application, which is working on virtual memory (No driver accessing physical memory directly), whether it would be fine to enable flag MEMPOOL_F_NO_IOVA_CONTIG.=20 We have object of 712 bytes, (final memory for each object is becoming 812 bytes after accounting header and trailer etc). We are creating 2500000 objects in pool, allocating 2 GB (1 GB huge pages) memory for the same, but after placing 4 objects in one page, it starts usi= ng next page as it is wrongly finding that page size is 4K. --=20 You are receiving this mail because: You are the assignee for the bug.= --17242378270.b0eCCD2.1847472 Date: Wed, 21 Aug 2024 12:57:07 +0200 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID 1525
Summary dpdk mempool creation is resulting into lot of memory getting= wasted
Product DPDK
Version 20.11
Hardware x86
OS Linux
Status UNCONFIRMED
Severity major
Priority Normal
Component core
Assignee dev@dpdk.org
Reporter sandipchhikara@gmail.com
Target Milestone --- 

We are using rte_mempool_op_popula=
te_helper for creating dpdk mempool.  Memory
is allocated from 1GB huge page and passed to this function. It is observed
that rte_mempool_op_populate_helper  function is calculating page size as 4K
and as MEMPOOL_F_NO_IOVA_CONTIG is not specified, so it don't place objects
across pages resulting into lot of memory wastage and creation of pool whic=
h is
lesser in size then required.
rte_mempool_op_calc_mem_size_default is used to calculate how much memory is
required for the pool.=20

If it is user application, which is working on virtual memory (No driver
accessing physical memory directly), whether it would be fine to enable flag
MEMPOOL_F_NO_IOVA_CONTIG.=20

We have object of 712 bytes, (final memory for each object is becoming 812
bytes after accounting header and trailer etc).
We are creating 2500000 objects in pool, allocating 2 GB (1 GB huge pages)
memory for the same, but after placing 4 objects in one page, it starts usi=
ng
next page as it is wrongly finding that page size is 4K.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17242378270.b0eCCD2.1847472--