DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: dev@dpdk.org, kaiwenx.deng@intel.com, stable@dpdk.org
Subject: Re: [PATCH] net/iavf: delay VF reset command
Date: Fri, 20 Sep 2024 13:01:58 +0200	[thread overview]
Message-ID: <CAJFAV8yZzfMz4v1AM=oDi+003Hngc3V=byZ5QWi-RTZFOeoBSA@mail.gmail.com> (raw)
In-Reply-To: <20240909110356.23757-1-bruce.richardson@intel.com>

On Mon, Sep 9, 2024 at 1:04 PM Bruce Richardson
<bruce.richardson@intel.com> wrote:
>
> Commit 0f9ec0cbd2a9 ("net/iavf: fix VF reset when using DCF"),
> introduced a VF-reset adminq call into the reset sequence for iavf.
> However, that call was very early in the sequence before other adminq
> commands had been sent.
>
> To delay the VF reset, we can put the message sending in the "dev_close"
> function, right before the adminq is shut down, and thereby guaranteeing
> that we won't have any subsequent issues with adminq messages.
>
> In the process of making this change, we can also use the iavf_vf_reset
> function from common/iavf, rather than hard-coding the message sending
> lower-level calls in the net driver.
>
> Fixes: e74e1bb6280d ("net/iavf: enable port reset")
> Fixes: 0f9ec0cbd2a9 ("net/iavf: fix VF reset when using DCF")
> Cc: kaiwenx.deng@intel.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>

I see this patch is already merged, but as I was investigating iavf
internals, I remembered this patch and relooked at it.

Sending a reset request to the PF while closing the device seems saner to me.
It also aligns the DPDK iavf driver behavior to the Linux kernel iavf driver.

Reviewed-by: David Marchand <david.marchand@redhat.com>

Thanks Bruce.

-- 
David Marchand


      parent reply	other threads:[~2024-09-20 11:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 11:03 Bruce Richardson
2024-09-17 14:31 ` Bruce Richardson
2024-09-20 11:01 ` David Marchand [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='CAJFAV8yZzfMz4v1AM=oDi+003Hngc3V=byZ5QWi-RTZFOeoBSA@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=kaiwenx.deng@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).