From: Bruce Richardson <bruce.richardson@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>, Jingjing Wu <jingjing.wu@intel.com>
Subject: Re: [PATCH v2] net/iavf: preserve MAC address with i40e PF Linux driver
Date: Tue, 1 Oct 2024 11:08:31 +0100 [thread overview]
Message-ID: <ZvvKH3slGViB9_7J@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20241001091254.98540-1-david.marchand@redhat.com>
On Tue, Oct 01, 2024 at 11:12:54AM +0200, David Marchand wrote:
> Following two upstream Linux kernel changes (see links), the mac address
> of a iavf port, serviced by a i40e PF driver, is lost when the DPDK iavf
> driver probes the port again (which may be triggered at any point of a
> DPDK application life, like when a reset event is triggered by the PF).
>
> A first change results in the mac address of the VF port being reset to 0
> during the VIRTCHNL_OP_GET_VF_RESOURCES query.
> The i40e PF driver change is pretty obscure but the iavf Linux driver does
> set VIRTCHNL_VF_OFFLOAD_USO.
> Announcing such a capability in the DPDK driver does not seem to be an
> issue, so do the same in DPDK to keep the legacy behavior of a fixed mac.
>
> Then a second change in the kernel results in the VF mac address being
> cleared when the VF driver remove its default mac address.
> Removing (unicast or multicast) mac addresses is not done by the kernel VF
> driver in general.
> The reason why the DPDK driver behaves like this is undocumented
> (and lost because the authors are not active anymore).
> Aligning DPDK behavior to the upstream kernel driver is safer in any
> case.
>
One question inline below.
/Bruce
> Cc: stable@dpdk.org
>
> Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fed0d9f13266
> Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ceb29474bbbc
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> drivers/net/iavf/iavf_ethdev.c | 22 +++++-----------------
> drivers/net/iavf/iavf_vchnl.c | 1 +
> 2 files changed, 6 insertions(+), 17 deletions(-)
>
> diff --git a/drivers/net/iavf/iavf_ethdev.c b/drivers/net/iavf/iavf_ethdev.c
> index 11036bc179..97cdb1cbe0 100644
> --- a/drivers/net/iavf/iavf_ethdev.c
> +++ b/drivers/net/iavf/iavf_ethdev.c
> @@ -1044,7 +1044,7 @@ iavf_dev_start(struct rte_eth_dev *dev)
> if (iavf_configure_queues(adapter,
> IAVF_CFG_Q_NUM_PER_BUF, index) != 0) {
> PMD_DRV_LOG(ERR, "configure queues failed");
> - goto err_queue;
> + goto error;
> }
> num_queue_pairs -= IAVF_CFG_Q_NUM_PER_BUF;
> index += IAVF_CFG_Q_NUM_PER_BUF;
> @@ -1052,12 +1052,12 @@ iavf_dev_start(struct rte_eth_dev *dev)
>
> if (iavf_configure_queues(adapter, num_queue_pairs, index) != 0) {
> PMD_DRV_LOG(ERR, "configure queues failed");
> - goto err_queue;
> + goto error;
> }
>
> if (iavf_config_rx_queues_irqs(dev, intr_handle) != 0) {
> PMD_DRV_LOG(ERR, "configure irq failed");
> - goto err_queue;
> + goto error;
> }
> /* re-enable intr again, because efd assign may change */
> if (dev->data->dev_conf.intr_conf.rxq != 0) {
> @@ -1077,14 +1077,12 @@ iavf_dev_start(struct rte_eth_dev *dev)
>
> if (iavf_start_queues(dev) != 0) {
> PMD_DRV_LOG(ERR, "enable queues failed");
> - goto err_mac;
> + goto error;
> }
>
> return 0;
>
> -err_mac:
> - iavf_add_del_all_mac_addr(adapter, false);
> -err_queue:
> +error:
> return -1;
> }
>
> @@ -1113,16 +1111,6 @@ iavf_dev_stop(struct rte_eth_dev *dev)
> /* Rx interrupt vector mapping free */
> rte_intr_vec_list_free(intr_handle);
>
> - /* adminq will be disabled when vf is resetting. */
> - if (!vf->in_reset_recovery) {
> - /* remove all mac addrs */
> - iavf_add_del_all_mac_addr(adapter, false);
> -
> - /* remove all multicast addresses */
> - iavf_add_del_mc_addr_list(adapter, vf->mc_addrs, vf->mc_addrs_num,
> - false);
> - }
> -
Question on this: while I understand we don't want to remove the default
mac address, should all other non-default macs not still be removed?
next prev parent reply other threads:[~2024-10-01 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-19 12:00 [PATCH] net/iavf: fix mac " David Marchand
2024-10-01 9:12 ` [PATCH v2] net/iavf: preserve MAC " David Marchand
2024-10-01 10:08 ` Bruce Richardson [this message]
2024-10-01 13:07 ` David Marchand
2024-10-01 13:14 ` Bruce Richardson
2024-10-15 17:03 ` Bruce Richardson
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=ZvvKH3slGViB9_7J@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jingjing.wu@intel.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).