DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
	Nikhil Rao <nikhil.rao@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eventdev: optimize Rx adapter event enqueue
Date: Sun, 16 Jun 2019 09:22:51 +0000	[thread overview]
Message-ID: <BYAPR18MB24247905FBC9CB63C671FD57C8E80@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <BYAPR18MB2424F10BA35444B2BE95F1C4C8E80@BYAPR18MB2424.namprd18.prod.outlook.com>



> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Jerin Jacob Kollanukkaran
> Sent: Sunday, June 16, 2019 2:10 PM
> To: Nikhil Rao <nikhil.rao@intel.com>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] eventdev: optimize Rx adapter event
> enqueue
> 
> 
> 
> > -----Original Message-----
> > From: Nikhil Rao <nikhil.rao@intel.com>
> > Sent: Tuesday, May 28, 2019 6:35 AM
> > To: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
> > Cc: dev@dpdk.org; Nikhil Rao <nikhil.rao@intel.com>
> > Subject: [EXT] [PATCH] eventdev: optimize Rx adapter event enqueue
> >
> > Setup event when the Rx queue is added to the adapter in place of
> > generating the event when it is being enqueued to the event device.
> >
> > Signed-off-by: Nikhil Rao <nikhil.rao@intel.com>
> 
> Acked-by: Jerin Jacob <jerinj@marvell.com>

Applied to dpdk-next-eventdev/master. Thanks.


  reply	other threads:[~2019-06-16  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-16  8:39 Jerin Jacob Kollanukkaran
2019-06-16  9:22 ` Jerin Jacob Kollanukkaran [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-06-10  4:20 Jerin Jacob Kollanukkaran
2019-06-14  5:02 ` Rao, Nikhil
2019-05-28  1:05 Nikhil Rao

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=BYAPR18MB24247905FBC9CB63C671FD57C8E80@BYAPR18MB2424.namprd18.prod.outlook.com \
    --to=jerinj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=nikhil.rao@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).