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 68F05A054F; Mon, 21 Nov 2022 03:55:02 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 0C5904014F; Mon, 21 Nov 2022 03:55:02 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id BDE8440041; Mon, 21 Nov 2022 03:54:59 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1668999300; x=1700535300; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=nFALXcchQfRD0VjFWjcwiU/iW14qLVDZTMBQI4K0mU0=; b=RdP3f+gLEWmm6xPfFtNSxlYL+U7X9drrmarzcz/TzJrDtvHReG4H8hza NsaHYv+HhW1qfwix1m6g+RgvdNoIj27FkLtrFskqtqVfja0q4bS6ZSdFc NNe1po2YaVIc1VdjaORatDNesVzkKDeXuKuWEVDTyVa7qQl4KvsjKCuXU lZHPSzKwOOPddeY7qcnCkPNiHGsbgKL1QwYJDHDgJED7OKg07Ff7S1Ab1 +SEqq+A0RK8Az6i/c1XOuGWQgXzzHRmMjlYH3WSir/bX3vVD1CPHMeAkQ 9/FtTzeuSm8JzVWkMMJVTYAjF21QMHE4QA0zrVvOOjLymMuxqgDkUxfvz w==; X-IronPort-AV: E=McAfee;i="6500,9779,10537"; a="293169939" X-IronPort-AV: E=Sophos;i="5.96,180,1665471600"; d="scan'208";a="293169939" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Nov 2022 18:54:58 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10537"; a="673830609" X-IronPort-AV: E=Sophos;i="5.96,180,1665471600"; d="scan'208";a="673830609" Received: from unknown (HELO yemj..) ([10.239.252.253]) by orsmga001-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 20 Nov 2022 18:54:55 -0800 From: Mingjin Ye To: dev@dpdk.org Cc: qiming.yang@intel.com, stable@dpdk.org, yidingx.zhou@intel.com, Mingjin Ye , Qi Zhang , Jie Zhou , Ranjit Menon , Ferruh Yigit , Pallavi Kadam Subject: [PATCH v6] doc: add PMD known issue Date: Mon, 21 Nov 2022 10:54:43 +0800 Message-Id: <20221121025443.190608-1-mingjinx.ye@intel.com> X-Mailer: git-send-email 2.34.1 In-Reply-To: <20221108132804.714764-2-mingjinx.ye@intel.com> References: <20221108132804.714764-2-mingjinx.ye@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit 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 Add a known issue: Rx path dynamic routing is not supported for PMD. Fixes: de853a3bb151 ("net/ice: disable DDP package on Windows") Cc: stable@dpdk.org Signed-off-by: Mingjin Ye --- doc/guides/nics/ice.rst | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/doc/guides/nics/ice.rst b/doc/guides/nics/ice.rst index ce075e067c..60fd7834ed 100644 --- a/doc/guides/nics/ice.rst +++ b/doc/guides/nics/ice.rst @@ -395,3 +395,20 @@ file is used by both the kernel driver and the DPDK PMD. Windows support: The DDP package is not supported on Windows so, loading of the package is disabled on Windows. + +ice: Rx path is not supported after PF or DCF add vlan offload +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +If pmd does not enable Vlan offload during initialization, it will +automatically select Rx paths that do not support offload. Even if +Vlan offload is subsequently enabled through the API, Vlan offload +will not work because the selected Rx path does not support Vlan +offload. + +Rx path dynamic routing is not supported. When the offload features is +switched, the queue needs to be reconfigured, then takes effect. It would +take additional workload for the network card to deal with. + +When applying VLAN offload on the PF or DCF, it must be configured +firstly by the startup parameters. + -- 2.34.1