From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 37348A0543;
	Tue,  7 Jun 2022 09:42:05 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 1E2E540689;
	Tue,  7 Jun 2022 09:42:05 +0200 (CEST)
Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178])
 by mails.dpdk.org (Postfix) with ESMTP id 0B8DA4021D
 for <dev@dpdk.org>; Tue,  7 Jun 2022 09:42:04 +0200 (CEST)
Received: by inbox.dpdk.org (Postfix, from userid 33)
 id F061AA0544; Tue,  7 Jun 2022 09:42:03 +0200 (CEST)
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1027] mempool cache size parameter is misleading
Date: Tue, 07 Jun 2022 07:42:03 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: DPDK
X-Bugzilla-Component: doc
X-Bugzilla-Version: unspecified
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mb@smartsharesystems.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: <bug-1027-3@http.bugs.dpdk.org/>
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
MIME-Version: 1.0
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org

https://bugs.dpdk.org/show_bug.cgi?id=3D1027

            Bug ID: 1027
           Summary: mempool cache size parameter is misleading
           Product: DPDK
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: doc
          Assignee: dev@dpdk.org
          Reporter: mb@smartsharesystems.com
  Target Milestone: ---

A flush threshold for the mempool cache was introduced in DPDK version
1.3. With this modification, the actual size of the mempool cache was
multiplied by 1.5, so e.g. a specified size of 512 allows the mempool cache=
 to
hold up to 1.5 * 512 =3D 768 objects.

None of the documentation was updated to reflect this change.

E.g. the Programmer's Guide says:

"The maximum size of the cache is static and is defined at compilation time
(RTE_MEMPOOL_CACHE_MAX_SIZE)." But in reality, the maximum size of the cach=
e is
RTE_MEMPOOL_CACHE_MAX_SIZE * 1.5.

Also, the "size" field of the rte_mempool_cache structure and the "cache_si=
ze"
parameter of the rte_mempool_create() function don't mention that the value=
 is
1/1.5 of the actual size.

If we don't want to fix the code, then the documentation needs to be fixed.

--=20
You are receiving this mail because:
You are the assignee for the bug.=