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 BD25842BA9; Fri, 26 May 2023 11:55:40 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 972F140DDA; Fri, 26 May 2023 11:55:40 +0200 (CEST) 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 551C640A89 for <dev@dpdk.org>; Fri, 26 May 2023 11:55:38 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1685094937; 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: in-reply-to:in-reply-to:references:references; bh=LJcmyt9zx/llq88ZIT5MDpeH/bKug8ORRX+5D/z1PlA=; b=eKCxIUQoCNgNMIVc5tF+ks4rFHCAI00bpkIYg9u1z8XVkNxBS0xQZLA/ZJEtwnaOAP1r0x hlgk8X8nidXkfw6zN9HHoOpOWiUvZg21UFQmUFheSeh/CRoTokjl1w8CQGnoY8x3deTBt5 hU5c+rPe+O+kWlVFUIrn3nuIJUChlFE= Received: from mail-pj1-f72.google.com (mail-pj1-f72.google.com [209.85.216.72]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-581-1rIdeThaOCy9EcrxWKbXbw-1; Fri, 26 May 2023 05:55:36 -0400 X-MC-Unique: 1rIdeThaOCy9EcrxWKbXbw-1 Received: by mail-pj1-f72.google.com with SMTP id 98e67ed59e1d1-2555adf8fffso529407a91.2 for <dev@dpdk.org>; Fri, 26 May 2023 02:55:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685094935; x=1687686935; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=LJcmyt9zx/llq88ZIT5MDpeH/bKug8ORRX+5D/z1PlA=; b=DebmZddtIzV2Ivj8x3KW2YTacPJajB/JXvh0WJZDy/7gJUToftjjazvU9TQrXeARSV d1+m4MHJ/Uibwn8CRZ+kF0mjp5Xhw6+HasBQcR8DBj4XX36lyk/4/OMK3Y5wn67ttJGr oaOvVwk/yTBuHa39a6QPJggRuIQdKgeTI9y/K1CEwQDmsANJBt6HHiWcyTKIRIpVx2YQ CFD4QsurDNWOlZ3YODSFH/UtWfdx21847XNVTCqLV1DfuCi6LpVl+rBcjBaHCQD3hGuq IDwZJHUHTxc2KjuVAr/VgrS2bwPYD3y0hm31VtBPavf7yxg3wN14Q3L8xeDujFILJ2n9 6wFg== X-Gm-Message-State: AC+VfDy0A3X1kwp8zMGjRaE+QYHeT45j9QrUA2aMrvgv+BbW707PCQzU +/gK1KTE3PY7iF1ClXiMwQOiIawcTfoIFoNc78Jrg2ca2yY3vm+tzvZbGhLJqMAfZTBupcZy5ZA uNLvT9SYCc1dr8HnxUbk= X-Received: by 2002:a17:90a:670b:b0:253:38bf:9757 with SMTP id n11-20020a17090a670b00b0025338bf9757mr1723017pjj.43.1685094935510; Fri, 26 May 2023 02:55:35 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4l13cMQy6E6ROe5k/by+xt5cr5p/ztiEh1EoWUYfSSvvRQOtMoTxUVmEt46AC7ilnDrhTlUc0w0AYdJGlON8o= X-Received: by 2002:a17:90a:670b:b0:253:38bf:9757 with SMTP id n11-20020a17090a670b00b0025338bf9757mr1723010pjj.43.1685094935279; Fri, 26 May 2023 02:55:35 -0700 (PDT) MIME-Version: 1.0 References: <20230503072641.474600-1-ophirmu@nvidia.com> <20230524222550.3538819-1-ophirmu@nvidia.com> In-Reply-To: <20230524222550.3538819-1-ophirmu@nvidia.com> From: David Marchand <david.marchand@redhat.com> Date: Fri, 26 May 2023 11:55:24 +0200 Message-ID: <CAJFAV8wEUFJ95B4zkSq768wuYZ=x2aY-xa_hJhQosD-=cgawGg@mail.gmail.com> Subject: Re: [PATCH v4] lib: set/get max memzone segments To: Devendra Singh Rawat <dsinghrawat@marvell.com>, Alok Prasad <palok@marvell.com> Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>, Ophir Munk <ophirmu@nvidia.com>, Matan Azrad <matan@nvidia.com>, Thomas Monjalon <thomas@monjalon.net>, Lior Margalit <lmargalit@nvidia.com> X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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 On Thu, May 25, 2023 at 12:26=E2=80=AFAM Ophir Munk <ophirmu@nvidia.com> wr= ote: > > Currently, the max memzones count constat (RTE_MAX_MEMZONE) is used to > decide how many memzones a DPDK application can have. This value could > technically be changed by manually editing `rte_config.h` before > compilation, but if DPDK is already compiled, that option is not useful. > There are certain use cases that would benefit from making this value > configurable. > > This commit addresses the issue by adding a new API to set the max > number of memzones before EAL initialization (while using the old > constant as default value), as well as an API to get current maximum > number of memzones. > > Signed-off-by: Ophir Munk <ophirmu@nvidia.com> > Acked-by: Morten Br=C3=B8rup <mb@smartsharesystems.com> qede maintainers, can you double check the change on your driver please? Thanks. --=20 David Marchand