From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
"pbhagavatula@marvell.com" <pbhagavatula@marvell.com>
Cc: "jerinj@marvell.com" <jerinj@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"jay.jayatheerthan@intel.com" <jay.jayatheerthan@intel.com>,
"erik.g.carrillo@intel.com" <erik.g.carrillo@intel.com>,
"abhinandan.gujjar@intel.com" <abhinandan.gujjar@intel.com>,
"timothy.mcdaniel@intel.com" <timothy.mcdaniel@intel.com>,
"sthotton@marvell.com" <sthotton@marvell.com>,
"nipun.gupta@nxp.com" <nipun.gupta@nxp.com>,
"harry.van.haaren@intel.com" <harry.van.haaren@intel.com>,
"mattias.ronnblom@ericsson.com" <mattias.ronnblom@ericsson.com>,
"liangma@liangbit.com" <liangma@liangbit.com>,
"peter.mccarthy@intel.com" <peter.mccarthy@intel.com>
Subject: RE: [PATCH v2] doc: announce changes to event device structures
Date: Thu, 27 Jul 2023 09:02:52 +0000 [thread overview]
Message-ID: <PAXPR04MB9328B4CAFE766E05E443C6988901A@PAXPR04MB9328.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <CALBAE1P16O8O+PuUMpVX4iF6GGB5NPSYobYzd0YdOMmVbKkhHA@mail.gmail.com>
> > 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>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
>
>
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2023-07-27 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 23:04 [PATCH] " pbhagavatula
2023-07-26 11:59 ` Jerin Jacob
2023-07-26 15:55 ` [PATCH v2] " pbhagavatula
2023-07-27 9:01 ` Jerin Jacob
2023-07-27 9:02 ` Hemant Agrawal [this message]
2023-07-28 15:14 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PAXPR04MB9328B4CAFE766E05E443C6988901A@PAXPR04MB9328.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=abhinandan.gujjar@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=jay.jayatheerthan@intel.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.com \
--cc=liangma@liangbit.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=nipun.gupta@nxp.com \
--cc=pbhagavatula@marvell.com \
--cc=peter.mccarthy@intel.com \
--cc=sthotton@marvell.com \
--cc=timothy.mcdaniel@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).