From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 60080A034E; Mon, 21 Feb 2022 08:28:34 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 325C940DF6; Mon, 21 Feb 2022 08:28:34 +0100 (CET) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by mails.dpdk.org (Postfix) with ESMTP id D7F2C4068C for ; Mon, 21 Feb 2022 08:28:32 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1645428513; x=1676964513; h=from:to:cc:subject:date:message-id; bh=e2Vytui295/lVjySRs0vrSQtmQ7J7SvhIlcH/7d6R6c=; b=UqEduO0Ttk/TiLzEZQuG/pJDWLOmdeN3B3NYu86VfIkdSEgiN4Ijxx0M 9OkxLMJAV3mah62QCQmmgGYNCaNIwGYCtdbYcZPXxH9Yaljdfie9MqDdT MgFB36T2T6ZA+uNI6jh2FUH+ThFOr7cH0E6PcFm8STO2Rzx0VDw8/5cGS y0fLZPjcfTKI46kMP0AO3X5s3ys5Ymm3tnGfe9OMgHsg0ZNErkUENwXP3 /x2DNV+wrHrWpN96zPjiPReKlbm5R27ebFKLOqKRTm1O4mMRnVtAEsJen /c32Pdw52FKDrlQ4dIWArDIep8rV1DeM7ZybrG8460KQiaRokZon1szWj Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10264"; a="251635736" X-IronPort-AV: E=Sophos;i="5.88,385,1635231600"; d="scan'208";a="251635736" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Feb 2022 23:28:31 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.88,385,1635231600"; d="scan'208";a="547223059" Received: from npg-dpdk-xuan-cbdma.sh.intel.com ([10.67.110.228]) by orsmga008.jf.intel.com with ESMTP; 20 Feb 2022 23:28:29 -0800 From: xuan.ding@intel.com To: maxime.coquelin@redhat.com, chenbo.xia@intel.com Cc: dev@dpdk.org, jiayu.hu@intel.com, yinan.wang@intel.com, xinguang.he@intel.com, Xuan Ding Subject: [PATCH] doc: remove multi-queue reconnection known issue Date: Mon, 21 Feb 2022 07:27:43 +0000 Message-Id: <20220221072743.88049-1-xuan.ding@intel.com> X-Mailer: git-send-email 2.17.1 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org From: Xuan Ding Since QEMU 5.2.0 fixes the vhost multi-queue reconnection issue in commit f66337bdbfda ("vhost-user: save features of multiqueues if chardev is closed"), this patch removes the previous description from known issue. Signed-off-by: Xuan Ding --- doc/guides/rel_notes/known_issues.rst | 21 --------------------- 1 file changed, 21 deletions(-) diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst index 187d9c942e..a8d1401a71 100644 --- a/doc/guides/rel_notes/known_issues.rst +++ b/doc/guides/rel_notes/known_issues.rst @@ -884,24 +884,3 @@ Unsuitable IOVA mode may be picked as the default **Driver/Module**: ALL. - -Vhost multi-queue reconnection failed with QEMU version >= 4.2.0 ----------------------------------------------------------------- - -**Description** - It's a QEMU regression bug (bad commit: c6beefd674ff). QEMU only saves - acked features for one vhost-net when vhost quits. When vhost reconnects - to virtio-net/virtio-pmd in multi-queue situations, the features been - set multiple times are not consistent. - -**Implication** - Vhost cannot reconnect back to virtio-net/virtio-pmd normally. - -**Resolution/Workaround**: - It is possible to filter the incorrect acked features at vhost-user side. - -**Affected Environment/Platform**: - ALL. - -**Driver/Module**: - Virtual Device Poll Mode Driver (PMD). -- 2.17.1