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 E074442F5B; Thu, 27 Jul 2023 11:01:54 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 707DD40693; Thu, 27 Jul 2023 11:01:54 +0200 (CEST) Received: from mail-vk1-f178.google.com (mail-vk1-f178.google.com [209.85.221.178]) by mails.dpdk.org (Postfix) with ESMTP id 03D0940041 for <dev@dpdk.org>; Thu, 27 Jul 2023 11:01:52 +0200 (CEST) Received: by mail-vk1-f178.google.com with SMTP id 71dfb90a1353d-4865f74d470so213701e0c.3 for <dev@dpdk.org>; Thu, 27 Jul 2023 02:01:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1690448512; x=1691053312; 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=XeHcbjQ75U1bLBCxrr2C9XQoXrAy/BVyA/g5gUv+TFY=; b=DUzaBz6tpjzn/HHULi7Dbd5ApH090bQEoPqkJwGQJB1FQ03lcOg9eX7xSXcHqfV/7d 3P7MI4FPZ0T8JdLv5VS8lS57E54djE11iJh1I7u3WuNNTPAggQUmoB+HGbJycBo258LU +6T5WHrdXNRf2upt3ujPaOJwunSbs6iaeBh+n6flQk3MszGHD2TmZXUfJ33PRakKxSsG pO+CpvLXR9xvJ79BC86UUrGTu+H9ewqIFlKX/eTGK/FVXV+S9pea+OZBEWxNQ4OEhya1 VG+rsd4gcB3URnQJ+YAjD3j1IugFyefyhCeGEOAAJGo6OzEpdS95v0OBBSV0Op2P8eNy 7QQA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1690448512; x=1691053312; 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=XeHcbjQ75U1bLBCxrr2C9XQoXrAy/BVyA/g5gUv+TFY=; b=CjmR+WALj1CXaGNA4xpq3aR+la95BSy4MEx6T31dD7fQJOE1Q5nXdkEXQ+V/8KGrob eTeDZJ6D+oTlpXEH1RZ0kZEUodBN0rhzpD6mKLemJlzaHsP5mbSkLhYKms0KWHA4EmzQ wFX8xCRju6qVqUFrf5iVwmBkhiwme0Zi18pwpUo3DGU4hC7HWI6wkbWACXwmPRM6+5eO nekslIy9iFhZ+c6vVavfosnj3DjmGZVU2srQMQafnSt0dXolm0ECx45+VJebaspmOzy/ 7EJMianxEwCxoL2UXdppRmuw9zqA06lkR5WVZTlx4ON2jguHUMEdq5vv9SpE//xsygfU xbqw== X-Gm-Message-State: ABy/qLZLATbdT9zxw1fAoQZFCzIqQnHMuiOI2a0ikvD5OI9aeUh0m+0n bH+RBp0wSYBlwmOkL22zhn7AEEhcBLLPeWagkXI= X-Google-Smtp-Source: APBJJlH4JOJRQ9eOu6Man1YAof/coyfcEp7/HrcZHq5Ck3eKxYWj61C3NQUBTnBZ+fEFNMX55WfCCbjFogsiAnvWpcA= X-Received: by 2002:a1f:3f08:0:b0:486:467f:97da with SMTP id m8-20020a1f3f08000000b00486467f97damr456004vka.0.1690448512078; Thu, 27 Jul 2023 02:01:52 -0700 (PDT) MIME-Version: 1.0 References: <20230725230458.1316-1-pbhagavatula@marvell.com> <20230726155524.799-1-pbhagavatula@marvell.com> In-Reply-To: <20230726155524.799-1-pbhagavatula@marvell.com> From: Jerin Jacob <jerinjacobk@gmail.com> Date: Thu, 27 Jul 2023 14:31:26 +0530 Message-ID: <CALBAE1P16O8O+PuUMpVX4iF6GGB5NPSYobYzd0YdOMmVbKkhHA@mail.gmail.com> Subject: Re: [PATCH v2] doc: announce changes to event device structures To: pbhagavatula@marvell.com Cc: jerinj@marvell.com, dev@dpdk.org, 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 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 Wed, Jul 26, 2023 at 9:25=E2=80=AFPM <pbhagavatula@marvell.com> wrote: > > From: Pavan Nikhilesh <pbhagavatula@marvell.com> > > 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 <pbhagavatula@marvell.com> > + > +* 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``. 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 Acked-by: Jerin Jacob <jerinj@marvell.com> > -- > 2.25.1 >