From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Ivan Malov <ivan.malov@arknetworks.am>, dev@dpdk.org
Cc: stable@dpdk.org, Andy Moreton <amoreton@xilinx.com>,
Viacheslav Galaktionov <Viacheslav.Galaktionov@arknetworks.am>
Subject: Re: [PATCH v2] net/sfc: export pick transfer proxy callback to representors
Date: Tue, 31 Jan 2023 14:13:15 +0300 [thread overview]
Message-ID: <12847fa4-130a-1fda-c658-a1bf4d35a64a@oktetlabs.ru> (raw)
In-Reply-To: <20230131110839.7453-1-ivan.malov@arknetworks.am>
On 1/31/23 14:08, Ivan Malov wrote:
> Currently, the "pick transfer proxy ethdev" callback is only
> advertised for non-representor (in example, main PF) ethdevs.
> That does not sit well with the original idea of this method,
> which is to let applications discover the privileged port to
> use for transfer flow management instead of any given ethdev.
> Applications trying to leverage this API on sfc representors
> receive an error and cannot configure transfer flow offloads.
>
> Fix the problem by exporting the method to representor ports.
>
> Fixes: 26706314d418 ("net/sfc: implement transfer proxy port callback")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ivan Malov <ivan.malov@arknetworks.am>
> Reviewed-by: Andy Moreton <amoreton@xilinx.com>
> Reviewed-by: Viacheslav Galaktionov <Viacheslav.Galaktionov@arknetworks.am>
No capital letters in E-mail address, please.
Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
next prev parent reply other threads:[~2023-01-31 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 7:24 [PATCH] " Ivan Malov
2023-01-31 7:52 ` Andrew Rybchenko
2023-01-31 11:08 ` [PATCH v2] " Ivan Malov
2023-01-31 11:13 ` Andrew Rybchenko [this message]
2023-02-08 22:06 ` Ferruh Yigit
2023-02-09 7:49 ` Ivan Malov
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=12847fa4-130a-1fda-c658-a1bf4d35a64a@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=Viacheslav.Galaktionov@arknetworks.am \
--cc=amoreton@xilinx.com \
--cc=dev@dpdk.org \
--cc=ivan.malov@arknetworks.am \
--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).