From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id E73EE1B63C for ; Fri, 13 Oct 2017 04:56:51 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Oct 2017 19:56:50 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.43,369,1503385200"; d="scan'208";a="162615794" Received: from dpdk26.sh.intel.com ([10.67.110.152]) by fmsmga006.fm.intel.com with ESMTP; 12 Oct 2017 19:56:49 -0700 From: Wenzhuo Lu To: dev@dpdk.org Cc: Wenzhuo Lu Date: Fri, 13 Oct 2017 10:58:02 +0800 Message-Id: <1507863488-41191-1-git-send-email-wenzhuo.lu@intel.com> X-Mailer: git-send-email 1.9.3 Subject: [dpdk-dev] [PATCH 0/6] fix TM (Traffic Management) issues on i40e and ixgbe X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Oct 2017 02:56:52 -0000 By design, all the queues are leaf nodes and others are non-leaf nodes, and the shaper profile can be null. Currently the i40e and ixgbe implementation doesn't follow this design. This patch set fixes this issue. Wenzhuo Lu (6): net/i40e: fix TM node parameter checking net/i40e: fix TM level capability getting net/ixgbe: fix TM node parameter checking net/ixgbe: fix TM level capability getting net/i40e: fix not supporting NULL TM profile net/ixgbe: fix not supporting NULL TM profile drivers/net/i40e/i40e_tm.c | 100 +++++++++++++++++++++++++++---------------- drivers/net/ixgbe/ixgbe_tm.c | 91 +++++++++++++++++++++++---------------- 2 files changed, 116 insertions(+), 75 deletions(-) -- 1.9.3