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 8CE1645C69; Fri, 8 Nov 2024 19:17:56 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 63D55433B6; Fri, 8 Nov 2024 19:17:56 +0100 (CET) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id E65484067C for ; Fri, 8 Nov 2024 19:17:54 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1731089874; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=j4mX9Uwfji80CSUw/OoVGNNqapEd+d6psOeVcnJtl4E=; b=gqfZBfc+5WBNnVd6duKJD+sLQTjdVtDJbAwVhTVnY3OL2wSpvlbmegAfFGtkZHXSJdT11e s8sIfzjnTknhFHC6utJoshNPeOLO9ykwPNr7ubv/LXFQRGrF996I3Fnuv7/PDOkybRpkpt A2ZuK3CzR9k3H+OS8FMXeDNNX4YdsSY= Received: from mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (ec2-54-186-198-63.us-west-2.compute.amazonaws.com [54.186.198.63]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-529-Ripmmp3OOeKPR-EfAyfKLw-1; Fri, 08 Nov 2024 13:17:50 -0500 X-MC-Unique: Ripmmp3OOeKPR-EfAyfKLw-1 X-Mimecast-MFC-AGG-ID: Ripmmp3OOeKPR-EfAyfKLw Received: from mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com [10.30.177.17]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx-prod-mc-04.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTPS id E38AF193585F; Fri, 8 Nov 2024 18:17:47 +0000 (UTC) Received: from dmarchan.redhat.com (unknown [10.45.224.57]) by mx-prod-int-05.mail-002.prod.us-west-2.aws.redhat.com (Postfix) with ESMTP id 438271953880; Fri, 8 Nov 2024 18:17:43 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: thomas@monjalon.net, Bruce Richardson , =?UTF-8?q?Mattias=20R=C3=B6nnblom?= , Stephen Hemminger , =?UTF-8?q?Morten=20Br=C3=B8rup?= , Chengwen Feng , Konstantin Ananyev Subject: [PATCH] config: limit lcore variable maximum size to 4k Date: Fri, 8 Nov 2024 19:17:32 +0100 Message-ID: <20241108181732.173263-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.0 on 10.30.177.17 X-Mimecast-Spam-Score: 0 X-Mimecast-MFC-PROC-ID: C8fNExIeIeuZ9Hz-B1oBImRuOXm5-THDzWvidZT_Xjo_1731089868 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true 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 OVS locks all pages to avoid page faults while processing packets. 1M for each lcore translates to allocating 128M with default build options on x86. This resulted in OOM while running unit tests in parallel. At the moment, the more demanding DPDK user of lcore variable is rte_service, with a 2112 bytes object. Limit the lcore variable maximum size to 4k which looks more reasonable. Fixes: 5bce9bed67ad ("eal: add static per-lcore memory allocation facility") Signed-off-by: David Marchand --- config/rte_config.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/rte_config.h b/config/rte_config.h index 498d509244..5f0627679f 100644 --- a/config/rte_config.h +++ b/config/rte_config.h @@ -41,7 +41,7 @@ /* EAL defines */ #define RTE_CACHE_GUARD_LINES 1 #define RTE_MAX_HEAPS 32 -#define RTE_MAX_LCORE_VAR 1048576 +#define RTE_MAX_LCORE_VAR 4096 #define RTE_MAX_MEMSEG_LISTS 128 #define RTE_MAX_MEMSEG_PER_LIST 8192 #define RTE_MAX_MEM_MB_PER_LIST 32768 -- 2.47.0