From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Ed Czeck <ed.czeck@atomicrules.com>, dev@dpdk.org
Cc: stable@dpdk.org, Shepard Siegel <shepard.siegel@atomicrules.com>,
John Miller <john.miller@atomicrules.com>
Subject: Re: [PATCH v2 1/3] net/ark: support for single function with multiple port
Date: Wed, 11 Oct 2023 12:28:11 +0100 [thread overview]
Message-ID: <d153a8cf-b5ed-4473-b147-b66c1a4d8dc8@amd.com> (raw)
In-Reply-To: <20231010204207.1027430-1-ed.czeck@atomicrules.com>
On 10/10/2023 9:42 PM, Ed Czeck wrote:
> Support the creation of multiple ports from one ark device via
> the use of ark pmd extension. I.e., one device with q queue can
> seen a p ports each with q/p queues.
>
> Add unique dev_private data for each port to manage queue assignment.
>
> This patch repairs a latent issue uncovered during testing.
> Fixes: 6799275eeea6 ("net/ark: support virtual functions")
> Cc: stable@dpdk.org
> Backporting is not requested.
>
> Signed-off-by: Ed Czeck <ed.czeck@atomicrules.com>
>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-10-11 11:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 20:52 [PATCH " Ed Czeck
2023-10-10 20:42 ` [PATCH v2 " Ed Czeck
2023-10-11 11:28 ` Ferruh Yigit [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=d153a8cf-b5ed-4473-b147-b66c1a4d8dc8@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=john.miller@atomicrules.com \
--cc=shepard.siegel@atomicrules.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).