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 843DCA00C4; Mon, 2 Jan 2023 10:15:36 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id B8F6A42D22; Mon, 2 Jan 2023 10:15:25 +0100 (CET) Received: from mx0b-00169c01.pphosted.com (mx0a-00169c01.pphosted.com [67.231.148.124]) by mails.dpdk.org (Postfix) with ESMTP id DF1A440A82 for ; Thu, 29 Dec 2022 02:26:18 +0100 (CET) Received: from pps.filterd (m0045114.ppops.net [127.0.0.1]) by mx0a-00169c01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 2BT1JL5u025678 for ; Wed, 28 Dec 2022 17:26:18 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paloaltonetworks.com; h=mime-version : from : date : message-id : subject : to : content-type; s=PPS12012017; bh=CEJ33zb2Fbg1CqRBOjTSPxlJXUHb87WAh6/EW7TBTGk=; b=bdEfrC57w+4RYWV+ofv5n7OuWKTtKiOOF01wRIrSXR4kSfErbsAm9nukpyrekX5b6N4r 7XqXovDYvX7lPo0zDLWKaNzL8GFecss5GwsUdk0bioZnlR3fQ1g/sZJ3Rakx/dbdRXpl CpfqqOibYEm870UptRVZZzTpfHPvr7lXTIIQpTnfiBVF9juCcgAC/5wvgep66kYTZqSW JV1HH77wFyA8Ilf6cP7KhcBFkCV3UBHxsIhwAjsumx73RjiHECJ5D4zT1bf45UMhXaad v2ixC8YmhKBSQivVQ4jTB/K5l9z45F0CyxeigXhK59loH+01Lbt1H4eNrgHNHxO3G089 aw== Received: from mail-pg1-f197.google.com (mail-pg1-f197.google.com [209.85.215.197]) by mx0a-00169c01.pphosted.com (PPS) with ESMTPS id 3mnxascnxm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Wed, 28 Dec 2022 17:26:17 -0800 Received: by mail-pg1-f197.google.com with SMTP id 191-20020a6306c8000000b0049699771579so6300966pgg.3 for ; Wed, 28 Dec 2022 17:26:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paloaltonetworks.com; s=google.paloaltonetworks.com; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=CEJ33zb2Fbg1CqRBOjTSPxlJXUHb87WAh6/EW7TBTGk=; b=NHFCdUy4SigO/KIZDl1b8v+fWXhIZnPNvUsZm3FUIt1sKgK9DWBlS0lwWvjW9tDEUZ dosHwpOatUVmTeytD8xCEha3ufoq2Y7mC31Wrb7BovqDOuD++J8dS+sQ28lXcGY2HUjd fAifi3k+CoD1KLvQSVwSkzW5qOUCsVkdret4zDFshtGNVgb2iNEyi40dn2AHHiOmmeQ+ Kae5U/YaWRJlt8L9vvWNo1oUlXn+HVXx6Crp+VK7H2XQoUMckIiGs6qqMoF4ICajE03c eO+x52F1rwCEh+BiUf90iE/jC6OdqeZ9dlNxdCnlzb+wrREr4U1oQur0CQZR3eAYlog8 0Pjg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=CEJ33zb2Fbg1CqRBOjTSPxlJXUHb87WAh6/EW7TBTGk=; b=Mj0w0dr2axf2lEt6WY2S8Lip69bwNXDuYEJWEnCrkronRSyyKhFvnXznimzNtK75fa 2YrNG3HWj2xdTjU2WmzcSWoeXtbZXXTi2I+ueqW/vaeZiWEKHuzB+FLNOj9w6ekkMxTr guOXOXT4Z4nVhWRVEI6Lu23VwKQ02UsgXNecHCdfrlnRV5RRBe3kJex45V8rv5t7+4Fs hXofOGbzViD9OxTrwPkQp1tMFgw2A+EEzpDjUPPjAQlWzQCFnfn8varfFoFdqj6m2lVP P2zQZ9kzOblLJ7tsx1sodr5baTjJNrmB9e0ijkVagJ6pkAXe79XAUu6nbCFUrbTusqal u0fw== X-Gm-Message-State: AFqh2koGawANgCMHVw9NcphNybp8ls0nQUc8UPcoNjferUDn4lyvLSGA dRhUKdQARoCb7D7932NElNktq3e7dRpR/9JChCWdUPlQ8zaGndcbqKScvEL/5sGItHL5DNqA/7K qWnfdamiK+whHnDhWgbE= X-Received: by 2002:a17:902:d541:b0:192:7d9d:fceb with SMTP id z1-20020a170902d54100b001927d9dfcebmr664111plf.83.1672277176691; Wed, 28 Dec 2022 17:26:16 -0800 (PST) X-Google-Smtp-Source: AMrXdXvrO2U8W4616KCFzCeMYKxMC4GCZh3AYT6T6UYDfTMuM4nT2ZqYM3QRQiP6WXDuqAnchnp2RHKDwjCgNZZEnvU= X-Received: by 2002:a17:902:d541:b0:192:7d9d:fceb with SMTP id z1-20020a170902d54100b001927d9dfcebmr664108plf.83.1672277176297; Wed, 28 Dec 2022 17:26:16 -0800 (PST) MIME-Version: 1.0 From: Venky Venkatesh Date: Wed, 28 Dec 2022 17:26:05 -0800 Message-ID: Subject: Traffic Management API Questions To: dev@dpdk.org Content-Type: multipart/alternative; boundary="0000000000000f6b2105f0ed5ff0" X-Proofpoint-ORIG-GUID: NnQDGB5hwBC2P0CuWXrhZFo5386NtoWr X-Proofpoint-GUID: NnQDGB5hwBC2P0CuWXrhZFo5386NtoWr X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.923,Hydra:6.0.545,FMLib:17.11.122.1 definitions=2022-12-29_01,2022-12-28_02,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1011 priorityscore=1501 suspectscore=0 impostorscore=0 mlxlogscore=717 spamscore=0 bulkscore=0 malwarescore=0 mlxscore=0 adultscore=0 phishscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2212290009 X-Mailman-Approved-At: Mon, 02 Jan 2023 10:15:22 +0100 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 --0000000000000f6b2105f0ed5ff0 Content-Type: text/plain; charset="UTF-8" Hi, I was looking at the DPDK Traffic Management API. I wanted to clarify some things that I understand from the code (for software based TM implementation (at 20.11)) vs the documentation. - The documentation says "Traffic shaping: single/*dual rate,* private (*per node*) and shared (by *multiple nodes*) shapers" are supported. However it appears that the code supports only *single *rate shapers. Is my understanding correct? - If not, pls point me to where dual rate shaping is supported in the software based TM implementation code. - However, if my understanding is correct, can the authors clarify the nature of issues they ran into in supporting dual rate (which thus prevented them from implementing it)? - The documentation comment above sounds like every node can have shapers. However it appears that the code does not support shaping at the port level. Again the same questions as above(regarding the accuracy of my understanding and if it is accurate, the reasons from the author for not supporting it) - At the level of the TM API (*and* the associated software TM implementation) are there any restrictions on the number of levels of QoS hierarchy we can construct? - Lastly, does the QoS framework API (which I suppose is built on lower level building blocks including the TM API) expose the entire capabilities of the TM API (e.g. dual rate shapers, shapers at port level, > 4 levels of shaping etc.)? From the reading of the documentation it appears that there may be restrictions imposed by the QoS framework API on top of what TM API imposes. Can someone pls confirm this (and if so, the reason for doing so)? Thanks -Venky --0000000000000f6b2105f0ed5ff0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
I was looking at the DPDK Traffic Management API. = I wanted to clarify some things that I understand from the code (for softwa= re based TM implementation (at 20.11)) vs the documentation.
    =
  • The documentation says "Traffic shaping: singl= e/dual rate, private (per node) and shared (by mult= iple nodes) shapers" are supported. However it appea= rs that the code supports only single rate shapers. Is my understand= ing correct?=C2=A0
    • If not, pls point me to where dual rate shap= ing is supported in the software based TM implementation code.=C2=A0
      • However, if my understanding is correct, can the authors clarify the natu= re of issues they ran into in supporting dual rate (which thus prevented th= em from implementing it)?
  • The documentation comment above soun= ds like every node can have shapers. However it appears that the code does = not support shaping at the port level. Again the same questions as above(re= garding the accuracy of my understanding and if it is accurate, the reasons= from the author for not supporting it)
  • At the level of the TM API = (and the associated software TM implementation) are there any restri= ctions on the number of levels of QoS hierarchy we can construct?
  • L= astly, does the QoS framework API (which I suppose is built on lower level = building blocks including the TM API) expose the entire capabilities of the= TM API (e.g. dual rate shapers, shapers at port level, > 4 levels of sh= aping etc.)? From the reading of the documentation it appears that there ma= y be restrictions imposed by the QoS framework API on top of what TM API im= poses. Can someone pls confirm this (and if so, the reason for=C2=A0doing s= o)?

Thanks
-Venky
--0000000000000f6b2105f0ed5ff0--