From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, dev@dpdk.org
Cc: indranil@chelsio.com, nirranjan@chelsio.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/cxgbe: fix control queue mbuf pool naming convention
Date: Wed, 12 Dec 2018 10:42:06 +0000 [thread overview]
Message-ID: <c7733e11-6bb0-c4e9-34ff-30947cbb9a44@intel.com> (raw)
In-Reply-To: <1544091200-16039-1-git-send-email-rahul.lakkireddy@chelsio.com>
On 12/6/2018 10:13 AM, Rahul Lakkireddy wrote:
> When multiple Chelsio adapters are present, the current naming
> convention of using underlying physical port number of the adapter
> creates conflicts when allocating control queue mbuf pool for
> multiple adapters and hence results in allocation failure. Fix by
> using port_id from rte_eth_dev_data, instead of physical port number.
>
> Fixes: 3a3aaabc7c77 ("net/cxgbe: add control queue to communicate filter requests")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>
Applied to dpdk-next-net/master, thanks.
parent reply other threads:[~2018-12-12 10:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1544091200-16039-1-git-send-email-rahul.lakkireddy@chelsio.com>]
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=c7733e11-6bb0-c4e9-34ff-30947cbb9a44@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=indranil@chelsio.com \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=stable@dpdk.org \
/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).