DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Nipun Gupta <nipun.gupta@nxp.com>
Cc: Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	"gage.eads@intel.com" <gage.eads@intel.com>,
	"harry.van.haaren@intel.com" <harry.van.haaren@intel.com>
Subject: Re: [dpdk-dev] [PATCH] eventdev: limit port link operation to configured queues
Date: Wed, 15 Feb 2017 14:53:05 +0000	[thread overview]
Message-ID: <20170215145305.GA85444@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <AM5PR0401MB2514092648A2A46F2BF01B34E6430@AM5PR0401MB2514.eurprd04.prod.outlook.com>

On Tue, Feb 07, 2017 at 10:00:10AM +0000, Nipun Gupta wrote:
> 
> 
> > -----Original Message-----
> > From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com]
> > Sent: Monday, February 06, 2017 11:00
> > To: dev@dpdk.org
> > Cc: bruce.richardson@intel.com; Hemant Agrawal
> > <hemant.agrawal@nxp.com>; gage.eads@intel.com;
> > harry.van.haaren@intel.com; Nipun Gupta <nipun.gupta@nxp.com>; Jerin Jacob
> > <jerin.jacob@caviumnetworks.com>
> > Subject: [dpdk-dev] [PATCH] eventdev: limit port link operation to configured
> > queues
> > 
> > On port_setup, the link_map is updated only
> > for configured number of event queues.
> > Limit the port_links_get scan only to configured number
> > of event queues. Also, Limit the port link and unlink queue
> > validation to configured number of event queues.
> > 
> > Fixes: 8ca610e0487c ("eventdev: implement the northbound APIs")
> > 
> > Reported-by: Nipun Gupta <nipun.gupta@nxp.com>
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> 
> Acked-by: Nipun Gupta <nipun.gupta@nxp.com>

Applied to dpdk-next-eventdev

Please note too, that next-eventdev tree has been rebased on top of the
mainline 17.02 release. This should make it easier to merge in the 17.05
timeframe.

/Bruce

      reply	other threads:[~2017-02-15 14:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-06  5:29 Jerin Jacob
2017-02-07 10:00 ` Nipun Gupta
2017-02-15 14:53   ` Bruce Richardson [this message]

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=20170215145305.GA85444@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=gage.eads@intel.com \
    --cc=harry.van.haaren@intel.com \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=nipun.gupta@nxp.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).