Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Kamil Maziarz <kamil.maziarz@intel.com>,
	<intel-wired-lan@lists.osuosl.org>
Cc: Dawid Wesierski <dawidx.wesierski@intel.com>,
	Sylwester Dziedziuch <sylwesterx.dziedziuch@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH net v3 1/4] iavf: Wait for reset in callbacks which trigger it
Date: Wed, 19 Apr 2023 15:47:17 -0700	[thread overview]
Message-ID: <e0bb847d-e773-dd08-8edd-6d323d1a4c8a@intel.com> (raw)
In-Reply-To: <20230419115006.200409-2-kamil.maziarz@intel.com>



On 4/19/2023 4:50 AM, Kamil Maziarz wrote:
> From: Marcin Szycik <marcin.szycik@linux.intel.com>
> 
> There was a fail when trying to add the interface to bonding
> right after changing the MTU on the interface. It was caused
> by bonding interface unable to open the interface due to
> interface being in __RESETTING state because of MTU change.
> 
> Add new reset_waitqueue to indicate that reset has finished.
> Add waiting for reset to finish in .
> 
> Add waiting for reset to finish in callbacks which trigger hw reset:
> iavf_set_priv_flags(), iavf_change_mtu() and iavf_set_ringparam().
> We choose 5 sec for the timeout waiting time because the same interval
> is used in oot where waiting
> 
> Add a function iavf_wait_for_reset() to reuse waiting for reset code and
> use it also in iavf_set_channels(), which already waits for reset.
> We don't use error handling in iavf_set_channels() as this could
> cause the device to be in incorrect state if the reset was scheduled
> but hit timeout or the waitng function was interrupted by a signal.
> 
> We use a 5000ms timeout period because on Hyper-V based systems,
> this operation takes around 3000-4000ms. In normal circumstances,
> it doesn't take more than 500ms to complete.
> 
> Fixes: aa626da947e9 ("iavf: Detach device during reset task")
> Signed-off-by: Marcin Szycik <marcin.szycik@linux.intel.com>
> Co-developed-by: Dawid Wesierski <dawidx.wesierski@intel.com>

The sign-off directly following co-developed needs to be the same.

WARNING: Co-developed-by and Signed-off-by: name/email do not match

> Signed-off-by: Sylwester Dziedziuch <sylwesterx.dziedziuch@intel.com>
> Signed-off-by: Dawid Wesierski <dawidx.wesierski@intel.com>
> Signed-off-by: Kamil Maziarz <kamil.maziarz@intel.com>

_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan

  parent reply	other threads:[~2023-04-19 22:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-19 11:50 [Intel-wired-lan] [PATCH net v3 0/4] iavf: fix reset task deadlock Kamil Maziarz
2023-04-19 11:50 ` [Intel-wired-lan] [PATCH net v3 1/4] iavf: Wait for reset in callbacks which trigger it Kamil Maziarz
2023-04-19 18:36   ` Jacob Keller
2023-04-19 22:47   ` Tony Nguyen [this message]
2023-04-19 11:50 ` [Intel-wired-lan] [PATCH net v3 2/4] iavf: Don't lock rtnl_lock twice in reset Kamil Maziarz
2023-04-19 18:40   ` Jacob Keller
2023-04-19 22:48   ` Tony Nguyen
2023-04-19 11:50 ` [Intel-wired-lan] [PATCH net v3 3/4] Revert "iavf: Detach device during reset task" Kamil Maziarz
2023-04-19 18:41   ` Jacob Keller
2023-04-19 11:50 ` [Intel-wired-lan] [PATCH net v3 4/4] Revert "iavf: Do not restart Tx queues after reset task failure" Kamil Maziarz
2023-04-19 18:42   ` Jacob Keller
2023-05-18 21:28     ` Jacob Keller
2023-04-19 18:35 ` [Intel-wired-lan] [PATCH net v3 0/4] iavf: fix reset task deadlock Jacob Keller

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=e0bb847d-e773-dd08-8edd-6d323d1a4c8a@intel.com \
    --to=anthony.l.nguyen@intel.com \
    --cc=dawidx.wesierski@intel.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kamil.maziarz@intel.com \
    --cc=sylwesterx.dziedziuch@intel.com \
    /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