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 B6A2F424EE; Mon, 4 Sep 2023 11:30:55 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 93589402AF; Mon, 4 Sep 2023 11:30:55 +0200 (CEST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) by mails.dpdk.org (Postfix) with ESMTP id 96454400EF for ; Mon, 4 Sep 2023 11:30:54 +0200 (CEST) Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 3EC7332002E2; Mon, 4 Sep 2023 05:30:51 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Mon, 04 Sep 2023 05:30:51 -0400 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 :sender:subject:subject:to:to; s=fm1; t=1693819850; x= 1693906250; bh=vGyElt6FJcmEGK7B/piKfRBFiLT2uGMuXb5iUbuK07w=; b=k g1WLp47sz+wwEEb9Z6t5A9w1kUVWVRHctn9TEJdXtok2nvSe+MVVynZ40pCyrICx VWLFr6cfqiy+Jt4Vv1bJPECxQx5ZIcnRe2tR2AfJtjDWUdrj+GbVL3AYWBLk9CGd Ho9yJcX5SARmSw5gWZ93FytmiWwC4sK7nmqWP6lO/c1Bj0oZlPzdrNBjAmseXRSD f9TFqaMiwSe8kgOS7cbL57ij6+O6liwzXqwbTXcCBIkcvWu+ctxmtCmJBtjox7LK RDm7yc9swOKO+cFjijwOSh4TDbc6prkwr6ky+xS7Smluui+TQS7uZkKLK85mdSB6 P/QWcQuBLstQZor2/f3NA== 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:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; t=1693819850; x=1693906250; bh=v GyElt6FJcmEGK7B/piKfRBFiLT2uGMuXb5iUbuK07w=; b=hYzyPImKPf0+ePJcq F03Ae4RNOdV9tWonrBTzeb4A8d45bSUDIxZyBjYliOMyqm/2YZqgzPL6U05fXRCG 0/4w+diOAITPO4a5RJ2uS2ZYxiRaBNUTfsY+ifhPSb/qsoAvycKKtKooSfo7yNBh mCQq3hOnRklnDVDRKWqipGntAoUObRSLjjpmipTgr08ymWklvFStktK3W2cRP4xI YhediBZ31CsyXQB2m1aKRzNTl26INuwBOSMiLZeMYhzDFYFkXnkw/jk1LEivKEYB gYLQ6ogyHhJryhJNQsJDOl/qpg/GAFQzgoQxf5RqU7dAs8kYXFZu0kP9mTIVQeuC XTCgg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrudegkedgudeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpeeugfegteduhfdujefgvdfhteeiuefghefffeeukefgfffgtefhfffh jeeuvdefvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 4 Sep 2023 05:30:49 -0400 (EDT) From: Thomas Monjalon To: Honnappa Nagarahalli , Konstantin Ananyev Cc: Morten =?ISO-8859-1?Q?Br=F8rup?= , dev@dpdk.org Subject: ring name size Date: Mon, 04 Sep 2023 11:30:47 +0200 Message-ID: <2838948.yaVYbkx8dN@thomas> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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, When creating a ring, we need to know the maximum length of the name. It seems this value is not documented. And there is no constant defined. There is only RTE_MEMZONE_NAMESIZE. Should we document the maximum length as 31 and add a constant? #define RTE_RING_NAME_SIZE RTE_MEMZONE_NAMESIZE