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 1B62945CB4; Fri, 8 Nov 2024 16:03:40 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A3A2C43348; Fri, 8 Nov 2024 16:03:39 +0100 (CET) Received: from fhigh-b6-smtp.messagingengine.com (fhigh-b6-smtp.messagingengine.com [202.12.124.157]) by mails.dpdk.org (Postfix) with ESMTP id F03F54025C for ; Fri, 8 Nov 2024 16:03:37 +0100 (CET) Received: from phl-compute-04.internal (phl-compute-04.phl.internal [10.202.2.44]) by mailfhigh.stl.internal (Postfix) with ESMTP id 170A325400F4; Fri, 8 Nov 2024 10:03:37 -0500 (EST) Received: from phl-mailfrontend-02 ([10.202.2.163]) by phl-compute-04.internal (MEProxy); Fri, 08 Nov 2024 10:03:37 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:message-id:mime-version:reply-to :subject:subject:to:to; s=fm3; t=1731078216; x=1731164616; bh=YR Mk5go/k2wM+N1w824atFSAEIzhS20QJ+SFNnWy1WY=; b=hhl0NQXo+UZhkXql9p L3oD5qDlw26+7lC5XzWhRaq53MV1no+lQY0nm8Ar+XSObfwWhTYTyR57XRlwjC+0 A3Ii4iPLiISYDTEELVdSw44lrcDsIoO3OjZNxJL1SxDAuDVjCc2jEaVFwmBhxGvG GWYDu3TXK3e9+nuCjqv+eRxH1bChWwmy2lzyc9+sYuNwFEBwQD6ttCWxoUNRf7QK sUAhdWE6PMwEL7OFxzN1iYJbXQhay0XAbirGNOcl/MDXEgcM329BeK3MKF56dy11 ibHKvg35Hw+go7tBhTMuwPnafw4qC74aqjb/nS1yaCD9QT+J3zPRAZf87xlAPbM0 QeNw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:message-id:mime-version:reply-to:subject :subject:to:to:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1731078216; x=1731164616; bh=YRMk5go/k2wM+N1w824atFSAEIzh S20QJ+SFNnWy1WY=; b=lQ6oDF8iRO48O2qLT50rshiIp75wc5qTNbPT9KQoakq/ QEWcT1X0xc9UcZ/6nSceDq70OsUF60Zk/zz02fLpsTFtpRZ0u4bFWE/8r87SVqvv N0u7FRau57cp2uEMuZ6aZa08dYN3NCgcmNm7wgCAMqKwHmcCNJeqFbATYui4bkWs y+9gomnpxjG4FWsgSgwEJeXffiQSZxfMai+jPGoiIQf4NRIB2CmSucZlp4ZZ5aOq 8Vux1Ma+lJF1RMYhtQYtZWJqPDLbGJguOTsaFqs/Adk6DSIM1OC6Vzxm9/UHv6kj 4Z9cPX/tXtPkj9euXDJmiBY0Ws67HxdGhtLh/O6zFg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrtdeigdeikecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnth hsucdlqddutddtmdenucfjughrpefhvfevufffkfgggfgtsehtufertddttdejnecuhfhr ohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonh drnhgvtheqnecuggftrfgrthhtvghrnhepjeevhefhvddtheevhffhtdetieekvedvjeeh teelleelffefvdetudehlefgueetnecuffhomhgrihhnpehophgvnhhsuhhsvgdrohhrgh enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhho mhgrshesmhhonhhjrghlohhnrdhnvghtpdhnsggprhgtphhtthhopeeipdhmohguvgepsh hmthhpohhuthdprhgtphhtthhopegrnhgrthholhihrdgsuhhrrghkohhvsehinhhtvghl rdgtohhmpdhrtghpthhtohepmhgrthhtihgrshdrrhhonhhnsghlohhmsegvrhhitghssh honhdrtghomhdprhgtphhtthhopegsrhhutggvrdhrihgthhgrrhgushhonhesihhnthgv lhdrtghomhdprhgtphhtthhopegumhhithhrhidrkhhoiihlihhukhesghhmrghilhdrtg homhdprhgtphhtthhopegurghvihgurdhmrghrtghhrghnugesrhgvughhrghtrdgtohhm pdhrtghpthhtohepuggvvhesughpughkrdhorhhg X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 8 Nov 2024 10:03:35 -0500 (EST) From: Thomas Monjalon To: anatoly.burakov@intel.com, Mattias =?UTF-8?B?UsO2bm5ibG9t?= , Bruce Richardson , Dmitry Kozlyuk Cc: David Marchand , dev@dpdk.org Subject: strange DPDK memory allocator behavior Date: Fri, 08 Nov 2024 16:03:33 +0100 Message-ID: <5579642.iZASKD2KPV@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" 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 Hello, After merging the lcore variables allocation from Mattias, we've seen an issue in unit tests running on 32-bit plaftorms: https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_Testing/i586 The initialization has this error message "most of the time": EAL: Cannot get a virtual area: Cannot allocate memory David did more tests with this command: # (for i in $(seq 10); do echo | LD_LIBRARY_PATH=lib:drivers app/dpdk-test --no-huge -m 2048 -d drivers; done) |& grep 'Cannot get a virtual area: Cannot allocate memory' EAL: Cannot get a virtual area: Cannot allocate memory EAL: Cannot get a virtual area: Cannot allocate memory EAL: Cannot get a virtual area: Cannot allocate memory There are 2 interesting findings: - the issue disappears when changing allocation size 2048 to more (4096) or less (1024) - the issue disappears when removing some big static arrays from unit tests like "sarray_lcore_state" in test_lcore_var_perf.c Should we avoid having such big arrays in our unit tests? I don't understand how "-m 2048" is impacted by the static allocations. And I wonder how it could impact memory fragmentation so 2048 MB cannot be allocated but more or less are working fine. It looks like an issue in the DPDK allocator. Note that we are using --no-huge for these tests. Any ideas?