* [PATCH] doc: announce changes to event device structures
@ 2023-07-25 23:04 pbhagavatula
2023-07-26 11:59 ` Jerin Jacob
2023-07-26 15:55 ` [PATCH v2] " pbhagavatula
0 siblings, 2 replies; 6+ messages in thread
From: pbhagavatula @ 2023-07-25 23:04 UTC (permalink / raw)
To: jerinj; +Cc: dev, Pavan Nikhilesh
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``.
Two new experimental APIs will be added, one to associate one to
associate an set of event queues with a profile which can be linked
to a event port and another to switch the profile which would
affect the next dequeue call.
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
doc/guides/rel_notes/deprecation.rst | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index fb771a0305..2b1fcf52ca 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -161,3 +161,11 @@ Deprecation Notices
The new port library API (functions rte_swx_port_*)
will gradually transition from experimental to stable status
starting with DPDK 23.07 release.
+
+* 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``.
+ Two new experimental APIs will be added, one to associate an set of event
+ queues with a profile which can be linked to a event port and an other to
+ switch the profile which would affect the next dequeue call.
--
2.25.1
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH] doc: announce changes to event device structures
2023-07-25 23:04 [PATCH] doc: announce changes to event device structures pbhagavatula
@ 2023-07-26 11:59 ` Jerin Jacob
2023-07-26 15:55 ` [PATCH v2] " pbhagavatula
1 sibling, 0 replies; 6+ messages in thread
From: Jerin Jacob @ 2023-07-26 11:59 UTC (permalink / raw)
To: pbhagavatula; +Cc: jerinj, dev
On Wed, Jul 26, 2023 at 4:35 AM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Please add all eventdev driver and subsystem mainainters.
>
> The structures ``rte_event_dev_info``, ``rte_event_fp_ops`` will be
> modified to add new elements to support link profiles.
Please describe what profile means here. Meaning the usage model.
>
> 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``.
> Two new experimental APIs will be added, one to associate one to
> associate an set of event queues with a profile which can be linked
> to a event port and another to switch the profile which would
> affect the next dequeue call.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index fb771a0305..2b1fcf52ca 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -161,3 +161,11 @@ Deprecation Notices
> The new port library API (functions rte_swx_port_*)
> will gradually transition from experimental to stable status
> starting with DPDK 23.07 release.
> +
> +* 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``.
> + Two new experimental APIs will be added, one to associate an set of event
> + queues with a profile which can be linked to a event port and an other to
> + switch the profile which would affect the next dequeue call.
New API additions does not need to mention here.
> --
> 2.25.1
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* [PATCH v2] doc: announce changes to event device structures
2023-07-25 23:04 [PATCH] doc: announce changes to event device structures pbhagavatula
2023-07-26 11:59 ` Jerin Jacob
@ 2023-07-26 15:55 ` pbhagavatula
2023-07-27 9:01 ` Jerin Jacob
1 sibling, 1 reply; 6+ messages in thread
From: pbhagavatula @ 2023-07-26 15:55 UTC (permalink / raw)
To: jerinj
Cc: dev, jay.jayatheerthan, erik.g.carrillo, abhinandan.gujjar,
timothy.mcdaniel, sthotton, hemant.agrawal, nipun.gupta,
harry.van.haaren, mattias.ronnblom, liangma, peter.mccarthy,
Pavan Nikhilesh
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>
---
v2 Changes:
- Add more description to commit log.
- Remove experimental API description from deprication.rst.
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 fb771a0305..1c52159673 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -161,3 +161,8 @@ Deprecation Notices
The new port library API (functions rte_swx_port_*)
will gradually transition from experimental to stable status
starting with DPDK 23.07 release.
+
+* 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``.
--
2.25.1
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] doc: announce changes to event device structures
2023-07-26 15:55 ` [PATCH v2] " pbhagavatula
@ 2023-07-27 9:01 ` Jerin Jacob
2023-07-27 9:02 ` Hemant Agrawal
2023-07-28 15:14 ` Thomas Monjalon
0 siblings, 2 replies; 6+ messages in thread
From: Jerin Jacob @ 2023-07-27 9:01 UTC (permalink / raw)
To: pbhagavatula
Cc: jerinj, dev, jay.jayatheerthan, erik.g.carrillo,
abhinandan.gujjar, timothy.mcdaniel, sthotton, hemant.agrawal,
nipun.gupta, harry.van.haaren, mattias.ronnblom, liangma,
peter.mccarthy
On Wed, Jul 26, 2023 at 9:25 PM <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
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: [PATCH v2] doc: announce changes to event device structures
2023-07-27 9:01 ` Jerin Jacob
@ 2023-07-27 9:02 ` Hemant Agrawal
2023-07-28 15:14 ` Thomas Monjalon
1 sibling, 0 replies; 6+ messages in thread
From: Hemant Agrawal @ 2023-07-27 9:02 UTC (permalink / raw)
To: Jerin Jacob, pbhagavatula
Cc: jerinj, dev, jay.jayatheerthan, erik.g.carrillo,
abhinandan.gujjar, timothy.mcdaniel, sthotton, nipun.gupta,
harry.van.haaren, mattias.ronnblom, liangma, peter.mccarthy
> > 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
> >
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH v2] doc: announce changes to event device structures
2023-07-27 9:01 ` Jerin Jacob
2023-07-27 9:02 ` Hemant Agrawal
@ 2023-07-28 15:14 ` Thomas Monjalon
1 sibling, 0 replies; 6+ messages in thread
From: Thomas Monjalon @ 2023-07-28 15:14 UTC (permalink / raw)
To: pbhagavatula
Cc: dev, jerinj, jay.jayatheerthan, erik.g.carrillo,
abhinandan.gujjar, timothy.mcdaniel, sthotton, hemant.agrawal,
nipun.gupta, harry.van.haaren, mattias.ronnblom, liangma,
peter.mccarthy, Jerin Jacob
27/07/2023 11:01, Jerin Jacob:
> On Wed, Jul 26, 2023 at 9:25 PM <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>
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.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2023-07-28 15:14 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-07-25 23:04 [PATCH] doc: announce changes to event device structures 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
2023-07-28 15:14 ` Thomas Monjalon
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).