DPDK patches and discussions
 help / color / mirror / Atom feed
From: "McDaniel, Timothy" <timothy.mcdaniel@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Pavan Nikhilesh <pbhagavatula@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>,
	"Ray Kinsella" <mdr@ashroe.eu>,
	Jerin Jacob <jerinjacobk@gmail.com>,
	"Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>,
	"Carrillo, Erik G" <erik.g.carrillo@intel.com>,
	"Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>,
	"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
	"Van Haaren, Harry" <harry.van.haaren@intel.com>,
	mattias.ronnblom <mattias.ronnblom@ericsson.com>,
	"liangma@liangbit.com" <liangma@liangbit.com>
Subject: RE: [PATCH] doc: announce changes to event vector structure
Date: Tue, 12 Jul 2022 16:06:29 +0000	[thread overview]
Message-ID: <SN6PR11MB31038357546A313B2F893EAE9E869@SN6PR11MB3103.namprd11.prod.outlook.com> (raw)
In-Reply-To: <3108919.VaX3XB0rFi@thomas>



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Tuesday, July 12, 2022 9:57 AM
> 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>; Jayatheerthan, Jay
> <jay.jayatheerthan@intel.com>; Carrillo, Erik G <erik.g.carrillo@intel.com>;
> Gujjar, Abhinandan S <abhinandan.gujjar@intel.com>; McDaniel, Timothy
> <timothy.mcdaniel@intel.com>; hemant.agrawal@nxp.com; Van Haaren, Harry
> <harry.van.haaren@intel.com>; mattias.ronnblom
> <mattias.ronnblom@ericsson.com>; liangma@liangbit.com
> Subject: Re: [PATCH] doc: announce changes to event vector structure
> 
> 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
> > >

Looks good to me.

Acked-by: Timothy McDaniel <timothy.mcdaniel@intel.com>

  reply	other threads:[~2022-07-12 16:06 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
2022-07-12 16:06     ` McDaniel, Timothy [this message]
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=SN6PR11MB31038357546A313B2F893EAE9E869@SN6PR11MB3103.namprd11.prod.outlook.com \
    --to=timothy.mcdaniel@intel.com \
    --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=thomas@monjalon.net \
    /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).