From: Ray Kinsella <mdr@ashroe.eu>
To: Ivan Malov <ivan.malov@oktetlabs.ru>
Cc: dev@dpdk.org, Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Andy Moreton <amoreton@xilinx.com>
Subject: Re: [PATCH 2/3] common/sfc_efx/base: manage VNIC MAC address by MCDI handle
Date: Thu, 26 May 2022 10:54:25 +0100 [thread overview]
Message-ID: <87tu9cbovi.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <20220526084550.243121-2-ivan.malov@oktetlabs.ru>
Ivan Malov <ivan.malov@oktetlabs.ru> writes:
> The board admin may need to assign a MAC address to a guest
> VNIC identified by its MCDI handle. Provide an API for that.
>
> In the case when a libefx-based driver is used at the guest,
> it will need to check its MAC address using the symmetrical
> API if the admin has tweaked it by means of its representor.
>
> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> Reviewed-by: Andy Moreton <amoreton@xilinx.com>
> ---
> drivers/common/sfc_efx/base/ef10_nic.c | 9 ++-
> drivers/common/sfc_efx/base/efx.h | 21 ++++-
> drivers/common/sfc_efx/base/efx_mcdi.c | 101 +++++++++++++++++++++++++
> drivers/common/sfc_efx/version.map | 2 +
> 4 files changed, 127 insertions(+), 6 deletions(-)
>
Acked-by: Ray Kinsella <mdr@ashoe.eu>
next prev parent reply other threads:[~2022-05-26 9:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 8:45 [PATCH 1/3] common/sfc_efx/base: convert EFX PCIe INTF to MCDI value Ivan Malov
2022-05-26 8:45 ` [PATCH 2/3] common/sfc_efx/base: manage VNIC MAC address by MCDI handle Ivan Malov
2022-05-26 9:54 ` Ray Kinsella [this message]
2022-05-26 8:45 ` [PATCH 3/3] net/sfc: allow to control the represented entity MAC address Ivan Malov
2022-05-31 16:57 ` [PATCH 1/3] common/sfc_efx/base: convert EFX PCIe INTF to MCDI value Andrew Rybchenko
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=87tu9cbovi.fsf@mdr78.vserver.site \
--to=mdr@ashroe.eu \
--cc=amoreton@xilinx.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ivan.malov@oktetlabs.ru \
/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).