patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhou, YidingX" <yidingx.zhou@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhou, YidingX" <yidingx.zhou@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v5] net/iavf: add thread for event callbacks
Date: Thu, 20 Oct 2022 05:40:08 +0000	[thread overview]
Message-ID: <DM4PR11MB599462DC54DA83666639D4C6D72A9@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20221020050022.102064-1-yidingx.zhou@intel.com>



> -----Original Message-----
> From: Yiding Zhou <yidingx.zhou@intel.com>
> Sent: Thursday, October 20, 2022 1:00 PM
> To: dev@dpdk.org
> Cc: Zhou, YidingX <yidingx.zhou@intel.com>; stable@dpdk.org
> Subject: [PATCH v5] net/iavf: add thread for event callbacks
>
> All callbacks registered for ethdev events are called in eal-intr-thread, and
> some of them execute virtchnl commands. Because interrupts are disabled in
> the intr thread, there will be no response received for these commands.
> So all callbacks should be called in a new context.
>
> When the device is bonded, the bond pmd registers callback for LSC event to
> execute virtchnl commands to reinitialize the device, it would also raise the
> above issue.
>
> This commit add a new thread to call all event callbacks.
>
> Fixes: 48de41ca11f0 ("net/avf: enable link status update")
> Fixes: 84108425054a ("net/iavf: support asynchronous virtual channel
> message")
> Cc: stable@dpdk.org
>
> Signed-off-by: Yiding Zhou <yidingx.zhou@intel.com>

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel after fix some typo

Thanks
Qi


  reply	other threads:[~2022-10-20  5:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19  6:06 [PATCH] net/iavf: fix error of virtchnl command Yiding Zhou
2022-09-19  7:53 ` [PATCH v2] " Yiding Zhou
2022-10-08  8:48 ` [PATCH v3] " Yiding Zhou
2022-10-09  6:03   ` Zhang, Qi Z
2022-10-10  2:02     ` Zhou, YidingX
2022-10-13  6:20 ` [PATCH v4] " Yiding Zhou
2022-10-18 13:18   ` Zhang, Qi Z
2022-10-13  6:21 ` [PATCH] net/ice/base: fix duplicate flow rules Yiding Zhou
2022-10-19 12:19   ` Xu, Ke1
2022-11-09  0:40     ` Zhang, Qi Z
2022-11-08  6:37   ` Zhou, YidingX
2022-10-20  5:00 ` [PATCH v5] net/iavf: add thread for event callbacks Yiding Zhou
2022-10-20  5:40   ` Zhang, Qi Z [this message]
2022-10-28 21:45   ` Thomas Monjalon

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=DM4PR11MB599462DC54DA83666639D4C6D72A9@DM4PR11MB5994.namprd11.prod.outlook.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    --cc=yidingx.zhou@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;
as well as URLs for NNTP newsgroup(s).