From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
Cc: bruce.richardson@intel.com, harry.van.haaren@intel.com,
gage.eads@intel.com, hemant.agrawal@nxp.com, nipun.gupta@nxp.com,
nikhil.rao@intel.com, santosh.shukla@caviumnetworks.com,
dev@dpdk.org
Subject: Re: [PATCH v3] eventdev: use links map to unlink queues
Date: Sat, 16 Dec 2017 14:46:37 +0530 [thread overview]
Message-ID: <20171216091636.GD8023@jerin> (raw)
In-Reply-To: <20171212185809.15482-1-pbhagavatula@caviumnetworks.com>
-----Original Message-----
> Date: Wed, 13 Dec 2017 00:28:09 +0530
> From: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> To: jerin.jacob@caviumnetworks.com, bruce.richardson@intel.com,
> harry.van.haaren@intel.com, gage.eads@intel.com, hemant.agrawal@nxp.com,
> nipun.gupta@nxp.com, nikhil.rao@intel.com,
> santosh.shukla@caviumnetworks.com
> Cc: dev@dpdk.org, Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH v3] eventdev: use links map to unlink queues
> X-Mailer: git-send-email 2.14.1
>
> The octeontx event device doesn't store the queues to port mapping as a
> result it cannot return the exact number of queues unlinked from a port
> when application wants to unlink all the queues mapped (supplies queues
> param as NULL).
>
> Using links_map we can determine the exact queues mapped to a specific
> port and unlink them.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> Acked-by: Gage Eads <gage.eads@intel.com>
Cc: stable@dpdk.org
Applied to dpdk-next-eventdev/master. Thanks.
prev parent reply other threads:[~2017-12-16 9:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 15:05 [PATCH] eventdev: use links_map to unlink queues Pavan Nikhilesh
2017-12-11 17:24 ` Eads, Gage
2017-12-12 7:23 ` Pavan Nikhilesh Bhagavatula
2017-12-12 9:33 ` [PATCH v2] eventdev: use links map " Pavan Nikhilesh
2017-12-12 16:08 ` Eads, Gage
2017-12-12 17:22 ` Pavan Nikhilesh Bhagavatula
2017-12-12 18:58 ` [PATCH v3] " Pavan Nikhilesh
2017-12-16 9:16 ` Jerin Jacob [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=20171216091636.GD8023@jerin \
--to=jerin.jacob@caviumnetworks.com \
--cc=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=nikhil.rao@intel.com \
--cc=nipun.gupta@nxp.com \
--cc=pbhagavatula@caviumnetworks.com \
--cc=santosh.shukla@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.