From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1D2EACCA47F for ; Tue, 12 Jul 2022 15:01:08 +0000 (UTC) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1B4BF42684; Tue, 12 Jul 2022 17:01:07 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id DCA3E41109 for ; Tue, 12 Jul 2022 17:01:04 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 921155C0132; Tue, 12 Jul 2022 11:01:04 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 12 Jul 2022 11:01:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding: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=1657638064; x= 1657724464; bh=QE1wF6/V8vkkiDcyvi3oJVNmxnUWHTr9lNSid3tNQaI=; b=a pzuPHg5y06vguAFVVF+lZV7m3ML5dtnjS27ibiWeH43F97fnhipJBNGql1h+l8qH vKoSyphqd13JrOSL5bDGmQPz/rIARy39QoybUV5YyzfNVy78M7Iq8h8FwP5PdDIL U/vvzwALitMCZMikVm1tU3x02cMWgm5fERRWiv9RwsWvMKs5joJK4l3R44v+yljP +1FsC/6l49D521WyadaaChuphrOpzLfb9PPvrTE7yyV3e9SqQZBUs+20f9KpuvLg wubHPx/i/VOuY2meKK22C9NGr4LrIIaARIFVbJB9yvjaps7e1NL8VhrtylP9NCWe y2EhoRZKQsVkENL70xoUw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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=1657638064; x= 1657724464; bh=QE1wF6/V8vkkiDcyvi3oJVNmxnUWHTr9lNSid3tNQaI=; b=b 95dzW4XSkSaFWVFe7rHdzduUbGf05+m0ybuMPSUeci7rZSf+/SbQDCkZeWFTIT4w KW5Eq65Dz1IFrfd98C8MUqSXNcKrkanIpISML7k3FaBqFBM9+5OW/AZd1OF1VtI0 oKKhXHOIPPPisCktVIrpSv8Qo3lmdDSYcuWg+FD+6NvDokox4U1CCWQwALpKyS4v K3B+ffA5C+BNOfeFAMkp3Y5/SSMOSrFxHtNbBb7N06LfKfpGg1WZ5rjrzJxTjghm 5OVInoNhZFJ5HTWkStBB/Peoi5RzCIptiLxxg40F35n7rlTmvP9DoMUkuctk04E/ n0agOHXeWWVLi4i+M8cUw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudejhedgkeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkfgjfhgggfgtsehtuf ertddttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghs sehmohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnheptdejieeifeehtdffgf dvleetueeffeehueejgfeuteeftddtieekgfekudehtdfgnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonh drnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 12 Jul 2022 11:01:03 -0400 (EDT) From: Thomas Monjalon To: Pavan Nikhilesh Cc: jerinj@marvell.com, Ray Kinsella , dev@dpdk.org, pbhagavatula@marvell.com Subject: Re: [PATCH 1/2] doc: add enqueue depth for new event type Date: Tue, 12 Jul 2022 17:01:02 +0200 Message-ID: <23408979.hYz58flQah@thomas> In-Reply-To: <20220627095702.8047-1-pbhagavatula@marvell.com> References: <20220627095702.8047-1-pbhagavatula@marvell.com> 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 I'm not your teacher, but please consider Cc'ing people outside of your company. 27/06/2022 11:57, pbhagavatula@marvell.com: > From: Pavan Nikhilesh > > A new field ``max_event_port_enqueue_new_burst`` will be added to the > structure ``rte_event_dev_info``. The field defines the max enqueue > burst size of new events (OP_NEW) supported by the underlying event > device. > > Signed-off-by: Pavan Nikhilesh > --- > doc/guides/rel_notes/deprecation.rst | 5 +++++ > 1 file changed, 5 insertions(+) > > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst > index 4e5b23c53d..071317e8e3 100644 > --- a/doc/guides/rel_notes/deprecation.rst > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -125,3 +125,8 @@ Deprecation Notices > applications should be updated to use the ``dmadev`` library instead, > with the underlying HW-functionality being provided by the ``ioat`` or > ``idxd`` dma drivers > + > +* eventdev: The structure ``rte_event_dev_info`` will be extended to include the > + max enqueue burst size of new events supported by the underlying event device. > + A new field ``max_event_port_enqueue_new_burst`` will be added to the structure > + ``rte_event_dev_info`` in DPDK 22.11. >