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 A594042F6C; Fri, 28 Jul 2023 17:14:50 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7E0C240685; Fri, 28 Jul 2023 17:14:50 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id B00E74021E for ; Fri, 28 Jul 2023 17:14:48 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5B4FD5C018D; Fri, 28 Jul 2023 11:14:48 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 28 Jul 2023 11:14:48 -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:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1690557288; x=1690643688; bh=J4HuVDSIMU/JqiwMSTnHDOLODUsPDcOvcjd Ww69v2Ao=; b=W93KDIQ+JpyFSszdqPem9qBfzbt7ixc3HYmJyZ3mRD1C2OcY+O5 EFSIxSnZFCq/lkS00Hlx6OKm6yUWDD/5HUZwhl6aNjVhS8l+SV71S07kQv02dn1D 0VwA9e99xZT4uCsUd7r2fST2Vjf0mTWEDXYoB7wJvfEZNl7AAYxmaSkPHu3Fe6MH B3PmjY93rEtB4lPJPITy3PUzd62iN+ufSvIGgayJAVnsw60pHthHNL1lJBaJ2jxn 1123e2ZpF3Isv+ADdXPiWcqLxtYPXDFXIlb0ELgWc7qrz7crryDRuRnsxn/VxbKg A04cfrWdNqjwGfpdwXrxp9pkcCF68HM/PWw== 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:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1690557288; x=1690643688; bh=J4HuVDSIMU/JqiwMSTnHDOLODUsPDcOvcjd Ww69v2Ao=; b=ELAx9dMwCM9q9i2lOvpUrLu3/cGOO+MUPUHDGS9s8rUTiIX0QaQ vE1eBZFSw1bn2iXxnnx553mbPjuHN+c/F2C79xg9tAiMCfx3hcJLS2dKcGPK2PJH jCMGj/yEBFiHbojGCpfKofB4gj/O+NdnqT/fTHmN6apQXYuY/RRvA+grH5sBTH6+ 9izuUvgtPJerjXEuK5OV5DJy3LeEL38SPF+d68JSOodUT6unD1sDZZmMjS+Y8Whi ovXW4c3JR799+Z9wSlK6ksqsRyKXNGOqlqgUmT2ner+xCA9t7Nw2EFTW8CmkckEM 9/1YsYeh88vHUTnAY3YCMSj5s9OWEzGXdlw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrieeigdekgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvvefufffkjghfggfgtgesthhqre dttddtjeenucfhrhhomhepvfhhohhmrghsucfoohhnjhgrlhhonhcuoehthhhomhgrshes mhhonhhjrghlohhnrdhnvghtqeenucggtffrrghtthgvrhhnpefftdeuhfehvdekleelve ffvdelhfelhedvgedtvddvudeuieevtdfgjedvudegfeenucffohhmrghinhepughpughk rdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 28 Jul 2023 11:14:46 -0400 (EDT) From: Thomas Monjalon To: pbhagavatula@marvell.com Cc: dev@dpdk.org, jerinj@marvell.com, jay.jayatheerthan@intel.com, erik.g.carrillo@intel.com, abhinandan.gujjar@intel.com, timothy.mcdaniel@intel.com, sthotton@marvell.com, hemant.agrawal@nxp.com, nipun.gupta@nxp.com, harry.van.haaren@intel.com, mattias.ronnblom@ericsson.com, liangma@liangbit.com, peter.mccarthy@intel.com, Jerin Jacob Subject: Re: [PATCH v2] doc: announce changes to event device structures Date: Fri, 28 Jul 2023 17:14:45 +0200 Message-ID: <4155307.1IzOArtZ34@thomas> In-Reply-To: References: <20230725230458.1316-1-pbhagavatula@marvell.com> <20230726155524.799-1-pbhagavatula@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" 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 27/07/2023 11:01, Jerin Jacob: > On Wed, Jul 26, 2023 at 9:25=E2=80=AFPM wrote: > > > > From: Pavan Nikhilesh > > > > The structures ``rte_event_dev_info``, ``rte_event_fp_ops`` will be > > modified to add new elements to support link profiles. > > A new field ``max_profiles_per_port`` will be added to > > ``rte_event_dev_info`` and ``switch_profile`` will be added to > > ``rte_event_fp_ops``. > > > > A profile is a unique identifier for a set of event queues linked to > > an event port. The unique identifier spans from 0 to the value > > advertised in ``rte_event_dev_info.max_profiles_per_port`` - 1. > > > > Two new experimental APIs will be added, one to associate a set of > > event queues with a profile which can be linked to an event port and > > another to switch the profile which would affect the next dequeue call. > > > > Signed-off-by: Pavan Nikhilesh >=20 > > + > > +* eventdev: The structures ``rte_event_dev_info``, ``rte_event_fp_ops`= ` will be > > + modified to add new elements to support link profiles.A new field > > + ``max_profiles_per_port`` will be added to ``rte_event_dev_info`` and > > + ``switch_profile`` will be added to ``rte_event_fp_ops``. >=20 > There are other deprecation notices to update rte_event_fp_ops. > Exact fields in rte_event_dev_info be decided later along with patch. > With that >=20 > Acked-by: Jerin Jacob Actually it does not look necessary to announce adding new fields. The ABI compatibility breakage should be covered by this patch: https://patches.dpdk.org/project/dpdk/patch/20230728142946.1201459-1-thomas= @monjalon.net/ Marking as superseded.