patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>, "stable@dpdk.org" <stable@dpdk.org>
Cc: David Marchand <david.marchand@redhat.com>
Subject: RE: [PATCH 22.11] Revert "net/iavf: fix abnormal disable HW interrupt"
Date: Fri, 19 Jan 2024 13:56:23 +0000	[thread overview]
Message-ID: <DM4PR12MB5373DB632C7E6F836208554EA1702@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <980fa553-adb0-40cf-95ee-43b331478124@redhat.com>

Hi Kevin,

Patch applied to 22.11 candidate branch, thanks for your help!

Regards,
Xueming

> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: 1/18/2024 20:24
> To: Xueming(Steven) Li <xuemingl@nvidia.com>; stable@dpdk.org
> Cc: David Marchand <david.marchand@redhat.com>
> Subject: Re: [PATCH 22.11] Revert "net/iavf: fix abnormal disable HW interrupt"
> 
> On 18/01/2024 12:03, Xueming(Steven) Li wrote:
> > It's on my TODO list, will apply by EOW.
> >
> 
> Thanks!
> 
> > Thanks,
> > Xueming
> >
> >> -----Original Message-----
> >> From: Kevin Traynor <ktraynor@redhat.com>
> >> Sent: 1/18/2024 19:42
> >> To: stable@dpdk.org; Xueming(Steven) Li <xuemingl@nvidia.com>
> >> Cc: David Marchand <david.marchand@redhat.com>
> >> Subject: Re: [PATCH 22.11] Revert "net/iavf: fix abnormal disable HW
> interrupt"
> >>
> >> Hi Xueming, did you get a chance to apply this?
> >>
> >> Just want to make sure we don't miss it for 22.11.4, because the
> >> referenced patch created a regression that broke iavf devices with OVS.
> >>
> >> thanks,
> >> Kevin.
> >>
> >> On 12/01/2024 11:20, Kevin Traynor wrote:
> >>> This reverts commit 2bdeeb53da0dda4e36a022553d3403c1217d677e.
> >>>
> >>> The change in behaviour [0] for handling some admin queue messages
> >>> from polling to interrupt mode has changed the behaviour and is
> >>> leading to a deadlock with OVS.
> >>>
> >>> [0]
> >>> commit 2bdeeb53da0dda4e36a022553d3403c1217d677e
> >>> Author: Mingjin Ye <mingjinx.ye@intel.com>
> >>> Date:   Wed Jun 14 09:53:03 2023 +0000
> >>>
> >>>     net/iavf: fix abnormal disable HW interrupt
> >>>
> >>>     [ upstream commit 675a104e2e940ec476e8b469725e8465d01c0098 ]
> >>>
> >>> Bugzilla ID: 1337
> >>> Reported-by: Kevin Traynor <ktraynor@redhat.com>
> >>> Signed-off-by: Kevin Traynor <ktraynor@redhat.com>
> >>> ---
> >>>  drivers/net/iavf/iavf_ethdev.c | 25 +++++++++---------
> >>> drivers/net/iavf/iavf_vchnl.c  | 48
> >>> +++++++++++++++++++++++++++-------
> >>>  2 files changed, 50 insertions(+), 23 deletions(-)
> >>>
> >>
> >>
> >


      reply	other threads:[~2024-01-19 13:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 11:20 Kevin Traynor
2024-01-14 23:47 ` Chris Brezovec (cbrezove)
2024-01-15 10:02   ` Kevin Traynor
2024-01-18 11:41 ` Kevin Traynor
2024-01-18 12:03   ` Xueming(Steven) Li
2024-01-18 12:23     ` Kevin Traynor
2024-01-19 13:56       ` Xueming(Steven) Li [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=DM4PR12MB5373DB632C7E6F836208554EA1702@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=ktraynor@redhat.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).