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 6B75D42850; Thu, 30 Mar 2023 10:28:07 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0845540E25; Thu, 30 Mar 2023 10:28:07 +0200 (CEST) Received: from mail-ed1-f46.google.com (mail-ed1-f46.google.com [209.85.208.46]) by mails.dpdk.org (Postfix) with ESMTP id 6497240685 for ; Thu, 30 Mar 2023 10:28:05 +0200 (CEST) Received: by mail-ed1-f46.google.com with SMTP id r11so73397186edd.5 for ; Thu, 30 Mar 2023 01:28:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680164885; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=Jhyz/sNutCuMKuHBAv08o8IVk9X3VhpsiK/98J2ZvsY=; b=GRSnry7E9jS1eeqlFD8hPd49YR3lPIphawrJ197bAg4ziQ7D2y+F8istbnpipidokF iIpN+WjfoS6pt5E3CoHHql557ANW9ZHQPgKxw2Efmih+WygrrhZTX1P/jboO6k9BBaJN o+ispQKdlB/BZ1vSTPdWSNHfeGDxy2VmT9iaja43NLvCFTjJWbo3H3uWfmcgFB4DRuFD ezNoPQLGZM0asz/CQ5f7JBzdCl6HGIXDIkzV8418mT0GzZVJgY644G8XUOd+wx4eZN5K 6/kXP+ZoV6qjhZIjrHOKYFes1R3U1xhu5kcbLnQbagHblmByie1m7rR3r2WP/00PVgJk svUA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680164885; 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=Jhyz/sNutCuMKuHBAv08o8IVk9X3VhpsiK/98J2ZvsY=; b=CfsvCQ84JM+Giq1U4t/zKW+CmGC7/xRtaZsSU5Db8FPalBlxE/LES0BkZ6mUxHiba6 UxDQW0Do1hE5DT9z1/alL2KpPNa6sjMh84tx6le2vgtpnpseHXoYzo1ob9Gg3AxNqWqP vRcq7WIOUtRMlsZRdaSdZK+gPbcyR/zC2mYweUc9SrAepzGtMH6fgwL0aUHD5Pgff7KO 3g+EaWK7K/3MhR85xiJBt0OsJNOBWmfVfUX16ai8vaEXnhyPknJq5Xati5QLXkinB/uB IM5Q9ivEN+ER/O7ed6cfFZir9IKCfm/V8s0appm2cooi9BfiOOzZ2nGwq49gIEzYETK0 LAvA== X-Gm-Message-State: AAQBX9fu3Rq4aD5X5m+UarLVD8amhq8wTzuao/68elMh02DwTLIPaJYA OBdObvTK4CPXvFX6rUhvFRSNgG2eDyOwIjg78GvXabB03TzLzQ== X-Google-Smtp-Source: AKy350a0YkKWvR8xCOAVSNcv4x7q5Ske+9pfHyc20dOxyAZ9d1ZgT4OACXhgbi40YNnCAH8UWbRVMZ0JISaracaWths= X-Received: by 2002:a50:d6d6:0:b0:4fb:c8e3:1adb with SMTP id l22-20020a50d6d6000000b004fbc8e31adbmr10822928edj.3.1680164884865; Thu, 30 Mar 2023 01:28:04 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Prashant Upadhyaya Date: Thu, 30 Mar 2023 13:57:52 +0530 Message-ID: Subject: Re: Regarding DPDK API's like rte_timer_subsystem_init/rte_hash_create etc. in VPP To: Bruce Richardson Cc: dev@dpdk.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Hi, The hash creation API throws the following error -- RING: Cannot reserve memory for tailq HASH: memory allocation failed The timer subsystem init api throws this error -- EAL: memzone_reserve_aligned_thread_unsafe(): Number of requested memzone segments exceeds RTE_MAX_MEMZONE I did check the code and apparently the memzone and rte zmalloc related api's are not being able to allocate memory. Regards -Prashant On Thu, Mar 30, 2023 at 1:30=E2=80=AFPM Bruce Richardson wrote: > > On Thu, Mar 30, 2023 at 10:30:24AM +0530, Prashant Upadhyaya wrote: > > Hi, > > > > While trying to port some code to VPP (which uses DPDK as the backend > > driver), I am running into a problem that calls to API's like > > rte_timer_subsystem_init, rte_hash_create are failing while allocation > > of memory. > > > > This is presumably because VPP inits the EAL with the following argumen= ts -- > > > > -in-memory --no-telemetry --file-prefix vpp > > > > Is there is something that can be done eg. passing some more parms in > > the EAL initialization which hopefully wouldn't break VPP but will > > also be friendly to the RTE timer and hash functions too, that would > > be great, so requesting some advice here. > > > Hi, > > can you provide some more details on what the errors are that you are > receiving? Have you been able to dig a little deeper into what might be > causing the memory failures? The above flags alone are unlikely to cause > issues with hash or timer libraries, for example. > > /Bruce