DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: dev@dpdk.org, Jerin Jacob <jerinj@marvell.com>,
	Ray Kinsella <mdr@ashroe.eu>, Jerin Jacob <jerinjacobk@gmail.com>,
	jay.jayatheerthan@intel.com, erik.g.carrillo@intel.com,
	abhinandan.gujjar@intel.com, timothy.mcdaniel@intel.com,
	hemant.agrawal@nxp.com, harry.van.haaren@intel.com,
	mattias.ronnblom@ericsson.com, liangma@liangbit.com
Subject: Re: [PATCH] doc: announce changes to event vector structure
Date: Tue, 12 Jul 2022 16:57:23 +0200	[thread overview]
Message-ID: <3108919.VaX3XB0rFi@thomas> (raw)
In-Reply-To: <CALBAE1ORO4kvvSJsQGAW29Sc-Zo9b1zuR70hWNFGbgvgT7RY9w@mail.gmail.com>

Tip to get more reviews: add interested maintainers in Cc.
Adding Jay, Erik, Abhinandan, Timothy, Hemant, Harry, Mattias and Liang.


11/07/2022 16:56, Jerin Jacob:
> On Tue, Jun 28, 2022 at 5:01 PM <pbhagavatula@marvell.com> wrote:
> >
> > From: Pavan Nikhilesh <pbhagavatula@marvell.com>
> >
> > The structure ``rte_event_vector`` will be modified to include
> > ``elem_offset:12`` bits taken from ``rsvd:15``.
> > The ``elem_offset`` defines the offset into the vector array from
> > which valid elements are present.
> >
> > Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
> 
> 
> Acked-by: Jerin Jacob <jerinj@marvell.com>
> 
> 
> > ---
> >  doc/guides/rel_notes/deprecation.rst | 7 +++++++
> >  1 file changed, 7 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> > index 4e5b23c53d..d7933629f2 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -125,3 +125,10 @@ Deprecation Notices
> >    applications should be updated to use the ``dmadev`` library instead,
> >    with the underlying HW-functionality being provided by the ``ioat`` or
> >    ``idxd`` dma drivers
> > +
> > +* eventdev: The structure ``rte_event_vector`` will be modified to include
> > +  ``elem_offset:12`` bits taken from ``rsvd:15``. The ``elem_offset`` defines
> > +  the offset into the vector array from which valid elements are present.
> > +  The difference between ``rte_event_vector::nb_elem`` and
> > +  ``rte_event_vector::elem_offset`` gives the number of valid elements left to
> > +  process from the ``rte_event_vector::elem_offset``.
> > --
> > 2.25.1
> >
> 






  reply	other threads:[~2022-07-12 14:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 11:28 pbhagavatula
2022-07-11 14:56 ` Jerin Jacob
2022-07-12 14:57   ` Thomas Monjalon [this message]
2022-07-12 16:06     ` McDaniel, Timothy
2022-07-13  6:53     ` Gujjar, Abhinandan S
2022-07-17 12:48 ` 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=3108919.VaX3XB0rFi@thomas \
    --to=thomas@monjalon.net \
    --cc=abhinandan.gujjar@intel.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jay.jayatheerthan@intel.com \
    --cc=jerinj@marvell.com \
    --cc=jerinjacobk@gmail.com \
    --cc=liangma@liangbit.com \
    --cc=mattias.ronnblom@ericsson.com \
    --cc=mdr@ashroe.eu \
    --cc=pbhagavatula@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).