DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, dev@dpdk.org
Subject: Re: [PATCH] doc: announce changes to event device structures
Date: Wed, 26 Jul 2023 17:29:25 +0530	[thread overview]
Message-ID: <CALBAE1ODYGjffjmtozmi5=Gw2kHaLrb-1UV9w_Ts9Gg97iJB+g@mail.gmail.com> (raw)
In-Reply-To: <20230725230458.1316-1-pbhagavatula@marvell.com>

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
>

  reply	other threads:[~2023-07-26 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 23:04 pbhagavatula
2023-07-26 11:59 ` Jerin Jacob [this message]
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

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='CALBAE1ODYGjffjmtozmi5=Gw2kHaLrb-1UV9w_Ts9Gg97iJB+g@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pbhagavatula@marvell.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).