From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <wenzhuol@shecgisg004.sh.intel.com> Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 4D79B2B9E for <dev@dpdk.org>; Wed, 24 Feb 2016 06:33:13 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP; 23 Feb 2016 21:33:12 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,492,1449561600"; d="scan'208";a="909987422" Received: from shvmail01.sh.intel.com ([10.239.29.42]) by fmsmga001.fm.intel.com with ESMTP; 23 Feb 2016 21:33:10 -0800 Received: from shecgisg004.sh.intel.com (shecgisg004.sh.intel.com [10.239.29.89]) by shvmail01.sh.intel.com with ESMTP id u1O5X8Ma008048; Wed, 24 Feb 2016 13:33:08 +0800 Received: from shecgisg004.sh.intel.com (localhost [127.0.0.1]) by shecgisg004.sh.intel.com (8.13.6/8.13.6/SuSE Linux 0.8) with ESMTP id u1O5X4WL007491; Wed, 24 Feb 2016 13:33:06 +0800 Received: (from wenzhuol@localhost) by shecgisg004.sh.intel.com (8.13.6/8.13.6/Submit) id u1O5X4MY007487; Wed, 24 Feb 2016 13:33:04 +0800 From: Wenzhuo Lu <wenzhuo.lu@intel.com> To: dev@dpdk.org Date: Wed, 24 Feb 2016 13:33:04 +0800 Message-Id: <1456291984-7309-1-git-send-email-wenzhuo.lu@intel.com> X-Mailer: git-send-email 1.7.4.1 Subject: [dpdk-dev] [PATCH] doc: Malicious Driver Detection not supported by ixgbe X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 24 Feb 2016 05:33:13 -0000 Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com> --- doc/guides/nics/ixgbe.rst | 21 +++++++++++++++++++++ doc/guides/rel_notes/release_16_04.rst | 24 ++++++++++++++++++++++++ 2 files changed, 45 insertions(+) diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst index 8cae299..aac5586 100644 --- a/doc/guides/nics/ixgbe.rst +++ b/doc/guides/nics/ixgbe.rst @@ -147,6 +147,27 @@ The following MACROs are used for these three features: * ETH_TXQ_FLAGS_NOXSUMTCP +Malicious Driver Detection not Supported by ixgbe +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ + +On Intel x550 series NICs, HW supports a feature called MDD (Malcicious +Driver Detection). +MDD is used to check the behavior of the VF driver. It means when transmitting +packets, the VF must use the advanced context descriptor and set it correctly. +And VF must set the CC (Check Context) bit either. +DPDK PF doesn't support MDD. We may hit problem in this scenario kernel PF + +DPDK VF. If user enables MDD in kernel PF, DPDK VF will not work. Because +kernel PF thinks the VF is malicious. But actually it's not. The only reason +is the VF doesn't act as MDD required. +There's significant performance impact to support MDD. DPDK should check if +the advanced context descriptor should be set and set it. And DPDK has to ask +the info about the header length from the upper layer, because parsing the +packet itself is not acceptale. So, it's too expensive to support MDD. +When using kernel PF + DPDK VF on x550, please make sure using the kernel +driver that disables MDD or can disable MDD. (Some kernel driver can use +this CLI 'insmod ixgbe.ko MDD=0,0' to disable MDD. Some kernel driver disable +it by default.) + Sample Application Notes ~~~~~~~~~~~~~~~~~~~~~~~~ diff --git a/doc/guides/rel_notes/release_16_04.rst b/doc/guides/rel_notes/release_16_04.rst index 5786f74..df81c54 100644 --- a/doc/guides/rel_notes/release_16_04.rst +++ b/doc/guides/rel_notes/release_16_04.rst @@ -90,6 +90,30 @@ This section should contain new known issues in this release. Sample format: tense. Add information on any known workarounds. +Restriction +----------- + +* **Malicious Driver Detection is not supported by ixgbe** + + On Intel x550 series NICs, HW supports a feature called MDD (Malcicious + Driver Detection). + MDD is used to check the behavior of the VF driver. It means when transmitting + packets, the VF must use the advanced context descriptor and set it correctly. + And VF must set the CC (Check Context) bit either. + DPDK PF doesn't support MDD. We may hit problem in this scenario kernel PF + + DPDK VF. If user enables MDD in kernel PF, DPDK VF will not work. Because + kernel PF thinks the VF is malicious. But actually it's not. The only reason + is the VF doesn't act as MDD required. + There's significant performance impact to support MDD. DPDK should check if + the advanced context descriptor should be set and set it. And DPDK has to ask + the info about the header length from the upper layer, because parsing the + packet itself is not acceptale. So, it's too expensive to support MDD. + When using kernel PF + DPDK VF on x550, please make sure using the kernel + driver that disables MDD or can disable MDD. (Some kernel driver can use + this CLI 'insmod ixgbe.ko MDD=0,0' to disable MDD. Some kernel driver disable + it by default.) + + API Changes ----------- -- 1.9.3