DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
Cc: "Jerin Jacob" <jerinj@marvell.com>,
	"Mattias Rönnblom" <mattias.ronnblom@ericsson.com>,
	dpdk-dev <dev@dpdk.org>, "Gage Eads" <gage.eads@intel.com>,
	"Van Haaren, Harry" <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: eventdev ABI change to support DLB PMD
Date: Tue, 4 Aug 2020 13:08:53 +0530	[thread overview]
Message-ID: <CALBAE1PsSyJAmT1ZUQhm5zmjnqTCMt+ewwi+ZXELRpX4pGvnWQ@mail.gmail.com> (raw)
In-Reply-To: <1596477335-3579-1-git-send-email-timothy.mcdaniel@intel.com>

On Mon, Aug 3, 2020 at 11:28 PM McDaniel, Timothy
<timothy.mcdaniel@intel.com> wrote:
>
> From: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>

There is still "," in the name.

>
> The ABI changes associated with this notification will better support
> devices that:
> 1. Have limits on the number or queues that may be linked to a port
> 2. Have ports that are limited to exactly one linked queue
> 3. Are not able to transparently transfer the event flow_id field
>
> Signed-off-by: McDaniel Timothy
> <timothy.mcdaniel@intel.com>


Acked-by: Jerin Jacob <jerinj@marvell.com>


> ---
>  doc/guides/rel_notes/deprecation.rst |   11 +++++++++++
>  1 file changed, 11 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index 99c9806..bfe6661 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -148,3 +148,14 @@ Deprecation Notices
>    Python 2 support will be completely removed in 20.11.
>    In 20.08, explicit deprecation warnings will be displayed when running
>    scripts with Python 2.
> +
> +* eventdev: ABI changes to support DLB PMD and future extensions:
> +  ``rte_event_dev_info``, ``rte_event_dev_config``, ``rte_event_port_conf`` will
> +  be modified to support DLB PMD and future extensions in the eventdev library.
> +  Patches containing justification, documentation, and proposed modifications
> +  can be found at:
> +
> +  - https://patches.dpdk.org/patch/71457/
> +  - https://patches.dpdk.org/patch/71456/
> +
> +
> --
> 1.7.10
>

  reply	other threads:[~2020-08-04  7:39 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-02 22:13 [dpdk-dev] [PATCH] doc: announce changes to eventdev public data structures McDaniel, Timothy
2020-07-30 16:33 ` McDaniel, Timothy
2020-07-30 18:48   ` Jerin Jacob
2020-07-31 18:51 ` McDaniel, Timothy
2020-07-31 19:03   ` Jerin Jacob
2020-07-31 19:31 ` McDaniel, Timothy
2020-08-03  6:09   ` Jerin Jacob
2020-08-03 17:55     ` [dpdk-dev] [PATCH] doc: eventdev ABI change to support DLB PMD McDaniel, Timothy
2020-08-04  7:38       ` Jerin Jacob [this message]
2020-08-04 15:44         ` Hemant Agrawal
2020-08-05 23:39           ` Thomas Monjalon
2020-08-07 16:21             ` McDaniel, Timothy
2020-08-04 13:46       ` Van Haaren, Harry
2020-08-05  9:36 ` [dpdk-dev] [PATCH] doc: announce changes to eventdev public data structures Kinsella, Ray
2020-08-05 23:46   ` 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=CALBAE1PsSyJAmT1ZUQhm5zmjnqTCMt+ewwi+ZXELRpX4pGvnWQ@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=jerinj@marvell.com \
    --cc=mattias.ronnblom@ericsson.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).