From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Kevin Traynor <ktraynor@redhat.com>
Cc: "Mcnamara, John" <john.mcnamara@intel.com>,
Mingjin Ye <mingjinx.ye@intel.com>,
Ian Stokes <ian.stokes@intel.com>,
David Marchand <david.marchand@redhat.com>,
dpdk stable <stable@dpdk.org>
Subject: RE: 22.11.4 iavf issue
Date: Thu, 11 Jan 2024 06:36:18 +0000 [thread overview]
Message-ID: <DM4PR12MB5373441B8B5066FE570E7C03A1682@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <f3cc15cd-ecfc-4cfd-b151-c84e4bbe8442@redhat.com>
Hi Kevin,
Thanks for the heads up, Intel test identified a bug of virtio:
https://bugs.dpdk.org/show_bug.cgi?id=1338
I'll hold a few days for sure.
Regards,
Xueming.
> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: 1/11/2024 1:20
> To: Xueming(Steven) Li <xuemingl@nvidia.com>
> Cc: Mcnamara, John <john.mcnamara@intel.com>; Mingjin Ye
> <mingjinx.ye@intel.com>; Ian Stokes <ian.stokes@intel.com>; David Marchand
> <david.marchand@redhat.com>; dpdk stable <stable@dpdk.org>
> Subject: 22.11.4 iavf issue
>
> Hi Xueming,
>
> Can I request that you hold off releasing DPDK 22.11.4 for a few days, so we can
> come to a conclusion about:
> https://bugs.dpdk.org/show_bug.cgi?id=1337
>
> It means that OVS deadlocks under certain circumstances with iavf driver. I
> recently moved some of the supported OVS branches to using DPDK 22.11.3, so
> ideally, 22.11.4 would have a fix for this and we can just move again.
>
> I have already reverted the backport [0] that triggered this issue for DPDK
> 21.11.6.
>
> thanks,
> Kevin.
>
> [0]
> 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 ]
prev parent reply other threads:[~2024-01-11 6:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-10 17:20 Kevin Traynor
2024-01-11 6:36 ` 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=DM4PR12MB5373441B8B5066FE570E7C03A1682@DM4PR12MB5373.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=ian.stokes@intel.com \
--cc=john.mcnamara@intel.com \
--cc=ktraynor@redhat.com \
--cc=mingjinx.ye@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).