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 24B53A0C43; Tue, 28 Sep 2021 16:04:10 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A0A3440E3C; Tue, 28 Sep 2021 16:04:09 +0200 (CEST) Received: from mail-ot1-f99.google.com (mail-ot1-f99.google.com [209.85.210.99]) by mails.dpdk.org (Postfix) with ESMTP id BC8D140DF6 for ; Tue, 28 Sep 2021 16:04:07 +0200 (CEST) Received: by mail-ot1-f99.google.com with SMTP id r43-20020a05683044ab00b0054716b40005so22165884otv.4 for ; Tue, 28 Sep 2021 07:04:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:date:subject:to:message-id; bh=jQZLJieds/atGz4ztF80XiVtjeZqyEwGWJLwiRkSMnk=; b=m6AwX7AR4yHIQVRguSShMjC1aUVzsH9wAWR7ZlAtbtDd0qzHRm71F6u0h3No7Z8XVv 8fQdrrUStl2++/g78E6eW6Yp/vlJZw+d60sbltNKy6MBNt6WGjqmS83ME/7Nz1kcSTsh UXoDNHn7yZgy8eZmYffvx/Ww+zZLNc/I32eT0t54gNrQrvpuucSjRfw6j9hJ9+DpVNxR ugaUkwN/lS5ij6se8z9imyIOd9o9v3okb6cVeYcVx+or6FPoobhOIiw9EwxQgDa50KhT u57sRRFngvUUKaMVSXRY3l2L++OdwggIswpdeXgiI967Ly3JZmB4t7l66Z987/hTUCAZ O8xQ== X-Gm-Message-State: AOAM531ucMHkT8ICWlpY5hfprpwpXzvA9o0LuRoPmMErNfG7hHn0lTGU LEWkKmWjxMGX4wEGcJfP8vRSDmG5FeVrVZwpt2h0+Q8uvrEq3w== X-Google-Smtp-Source: ABdhPJxtPv1xdImsawHvA0T5oRkDSdk6ONZcvbljaaMcLGCwlRXovsuhRqrKuS/z598nM2Hj4edQCXIZmpsb X-Received: by 2002:a9d:7d8c:: with SMTP id j12mr5183568otn.135.1632837846368; Tue, 28 Sep 2021 07:04:06 -0700 (PDT) Received: from optima.cs.arizona.edu (optima.cs.arizona.edu. [192.12.69.5]) by smtp-relay.gmail.com with ESMTPS id r23sm6162608otu.7.2021.09.28.07.04.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Sep 2021 07:04:06 -0700 (PDT) X-Relaying-Domain: cs.arizona.edu Received: from cs.arizona.edu (lectura.cs.arizona.edu [192.12.69.186]) by optima.cs.arizona.edu (8.14.4/8.14.4/Debian-2ubuntu2.1) with ESMTP id 18SE451w030692 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 28 Sep 2021 07:04:05 -0700 Received: from localhost (cs.arizona.edu [local]) by cs.arizona.edu (OpenSMTPD) with ESMTPA id 824db556; Tue, 28 Sep 2021 14:03:49 +0000 (UTC) From: Junxiao Shi Date: Tue, 28 Sep 2021 13:51:59 +0000 To: dev@dpdk.org Message-ID: <973fc5b37c6164c1@cs.arizona.edu> Subject: [dpdk-dev] [PATCH] net/memif: allocate socket hash on any NUMA socket 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 Sender: "dev" Previously, memif socket hash is always allocated on NUMA socket 0. If the application is entirely running on another NUMA socket and EAL --socket-limit prevents memory allocation on NUMA socket 0, memif creation fails with "HASH: memory allocation failed" error. This patch allows allocating memif socket hash on any NUMA socket. Signed-off-by: Junxiao Shi --- drivers/net/memif/memif_socket.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/net/memif/memif_socket.c b/drivers/net/memif/memif_socket.c index f58ff4c0cb..364e818d65 100644 --- a/drivers/net/memif/memif_socket.c +++ b/drivers/net/memif/memif_socket.c @@ -946,6 +946,7 @@ memif_create_socket_hash(void) params.key_len = MEMIF_SOCKET_UN_SIZE; params.hash_func = rte_jhash; params.hash_func_init_val = 0; + params.socket_id = SOCKET_ID_ANY; return rte_hash_create(¶ms); } -- 2.17.1