From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 5DD0C69A5 for ; Fri, 24 Mar 2017 06:20:08 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1490332808; x=1521868808; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=a8cJ63JqUyJGhdQJHeV3lECZTvXQ/wrvlQmVe7cYCcM=; b=Q9noVnq9HFUJQpeytBrGecaNtn3Xtyut0diIl+sA7vBoTyytD0Fzly0c XypXtdcU1cM6ZNrR6GCMAH4U94i0hg==; Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Mar 2017 22:20:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,213,1486454400"; d="scan'208";a="1146359055" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by fmsmga002.fm.intel.com with ESMTP; 23 Mar 2017 22:20:06 -0700 Received: from fmsmsx122.amr.corp.intel.com (10.18.125.37) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 23 Mar 2017 22:20:06 -0700 Received: from shsmsx104.ccr.corp.intel.com (10.239.4.70) by fmsmsx122.amr.corp.intel.com (10.18.125.37) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 23 Mar 2017 22:20:06 -0700 Received: from shsmsx103.ccr.corp.intel.com ([169.254.4.253]) by SHSMSX104.ccr.corp.intel.com ([169.254.5.42]) with mapi id 14.03.0248.002; Fri, 24 Mar 2017 13:19:51 +0800 From: "Wu, Jingjing" To: "Lu, Wenzhuo" , "dev@dpdk.org" CC: "Lu, Wenzhuo" Thread-Topic: [dpdk-dev] [PATCH 4/8] net/i40e: set TC strict priority mode Thread-Index: AQHSjk3HmCZM34Jzh06UWn3aNL0FF6Gjn31w Date: Fri, 24 Mar 2017 05:19:50 +0000 Message-ID: <9BB6961774997848B5B42BEC655768F810D1061B@SHSMSX103.ccr.corp.intel.com> References: <1487906675-54260-1-git-send-email-wenzhuo.lu@intel.com> <1487906675-54260-5-git-send-email-wenzhuo.lu@intel.com> In-Reply-To: <1487906675-54260-5-git-send-email-wenzhuo.lu@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 4/8] net/i40e: set TC strict priority mode 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, 24 Mar 2017 05:20:09 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Wenzhuo Lu > Sent: Friday, February 24, 2017 11:25 AM > To: dev@dpdk.org > Cc: Lu, Wenzhuo > Subject: [dpdk-dev] [PATCH 4/8] net/i40e: set TC strict priority mode >=20 > Set some TCs to strict priority mode. > It's a global setting on a physical port. >=20 > Signed-off-by: Wenzhuo Lu > --- > doc/guides/nics/i40e.rst | 10 +++ > doc/guides/rel_notes/release_17_05.rst | 7 ++ > drivers/net/i40e/i40e_ethdev.c | 119 > ++++++++++++++++++++++++++++++ > drivers/net/i40e/i40e_ethdev.h | 1 + > drivers/net/i40e/rte_pmd_i40e.h | 15 ++++ > drivers/net/i40e/rte_pmd_i40e_version.map | 1 + > 6 files changed, 153 insertions(+) >=20 > diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst index > 260287e..361d9d9 100644 > --- a/doc/guides/nics/i40e.rst > +++ b/doc/guides/nics/i40e.rst > @@ -478,3 +478,13 @@ enabled. If so, return failure. > When enabling per TC max bandwidth, SW will check if per VF max bandwidt= h > is enabled. If so, disable per VF max bandwidth and continue with per TC = max > bandwidth setting. > + > +TC TX scheduling mode setting > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > + > +There're 2 TX scheduling modes for TCs, round robin and strict priority = mode. > +If a TC is set to strict priority mode, it can consume unlimited bandwid= th. > +It means if APP has set the max bandwidth for that TC, it comes to no > +effect. > +It's suggested to set the strict priority mode for a TC that is latency > +sensitive but no consuming much bandwidth. > diff --git a/doc/guides/rel_notes/release_17_05.rst > b/doc/guides/rel_notes/release_17_05.rst > index d31435c..99811a2 100644 > --- a/doc/guides/rel_notes/release_17_05.rst > +++ b/doc/guides/rel_notes/release_17_05.rst > @@ -55,6 +55,13 @@ New Features > i40e HW supports to set the max bandwidth for a TC on a VF. Enable thi= s > capability. >=20 > +* **Added TC strict priority mode setting on i40e.** > + > + There're 2 TX scheduling modes supported for TCs by i40e HW, round > + ribon mode and strict priority mode. By default it's round robin > + mode. Enable the capability to change the TX scheduling mode for a > + TC. It's a global setting on a physical port. > + > Resolved Issues > + if (!veb->strict_prio_tc) > + ret =3D i40e_aq_config_switch_comp_ets( > + hw, veb->uplink_seid, > + &ets_data, i40e_aqc_opc_enable_switching_comp_ets, > + NULL); How about to check the tc_map when the first time to set strict_prio_tc?