DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Medvedkin, Vladimir" <vladimir.medvedkin@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>, <dev@dpdk.org>
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH v2] doc: add deprecation notice for iavf devarg auto reconfig
Date: Fri, 17 Jul 2026 09:41:38 +0100	[thread overview]
Message-ID: <16acd53d-6d66-44b5-acb0-feb495c96502@intel.com> (raw)
In-Reply-To: <20260715122045.2256082-1-ciara.loftus@intel.com>

Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>

On 7/15/2026 1:20 PM, Ciara Loftus wrote:
> The `auto_reconfig` devarg in the iavf driver is enabled by default and the
> case for ever disabling it is weak. When disabled, it means the user is
> requesting the driver not to restore settings (unicast/multicast
> promiscuous modes) when recovering from a reset. The use case where this
> might be desired is during a VF initiated reset where the user initiates
> the reset and wants the VF brought back up in an untouched state. That
> scenario can be facilitated by extending the `rte_pmd_iavf_reinit` API
> rather than relying on this devarg, so it should be safe to remove the
> devarg.
>
> Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> v2:
> * Shortened deprecation note
> ---
>   doc/guides/rel_notes/deprecation.rst | 6 ++++++
>   1 file changed, 6 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index f5c12cc747..910feb7cf2 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -159,3 +159,9 @@ Deprecation Notices
>   * net/iavf: The dynamic mbuf field used to detect LLDP packets on the
>     transmit path in the iavf PMD will be removed in a future release.
>     After removal, only packet type-based detection will be supported.
> +
> +* net/iavf: The ``auto_reconfig`` devarg is deprecated and will be removed
> +  in a future release. It allows disabling the automatic restoration of
> +  device settings after a VF reset, but this is of questionable value
> +  since most applications expect their settings to be preserved
> +  transparently across a reset.

-- 
Regards,
Vladimir


  reply	other threads:[~2026-07-17  8:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-15 10:59 [PATCH] doc: add deprecation notice for iavf devarg auto reconfig Ciara Loftus
2026-07-15 12:01 ` Bruce Richardson
2026-07-15 12:20 ` [PATCH v2] " Ciara Loftus
2026-07-17  8:41   ` Medvedkin, Vladimir [this message]
2026-07-22 12:41     ` Thomas Monjalon
2026-07-17  8:46   ` David Marchand

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=16acd53d-6d66-44b5-acb0-feb495c96502@intel.com \
    --to=vladimir.medvedkin@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@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