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 8B78BA00C2; Thu, 5 Jan 2023 13:07:56 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 32141400D4; Thu, 5 Jan 2023 13:07:56 +0100 (CET) Received: from mx0b-00169c01.pphosted.com (mx0b-00169c01.pphosted.com [67.231.156.123]) by mails.dpdk.org (Postfix) with ESMTP id 3B71E40041 for ; Thu, 5 Jan 2023 13:07:55 +0100 (CET) Received: from pps.filterd (m0048188.ppops.net [127.0.0.1]) by mx0b-00169c01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 3055RV5X001773 for ; Thu, 5 Jan 2023 04:07:54 -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=2oPllOJAti+yFARAUdLDhKxgUEFqmZ5NUz58FCzSBrU=; b=gt7mBjv9nz65+0MalMHq/C6QgaKjQ9Zf1K3S4catMzqqIU3ChQCVMK32fC0lrykf4PXe m+Ekyjfw7BeQ2ZMISyAIATGnuM7eRocWH515Zyo+HYw0JXBfYyA6GEBoU5vzXMc8njq5 Ndnw9+BILdxDMKb5dn8Do4SWOXkmp84fISNSgg1UyWqM7ZvLk1B/ixcXkOJ0kXovEv6Y fuKmfVufpGuK7qcKfbvzAkbAhW1j6mGCgfR+jzWztWjrygFmKiFbGK69kbclZFXCOnxu mMVuMg5LuwYnP82oRBFk0k+iuAPHAl/Je9knOBvC0zYfBY5q3uAzowqGEqWGfmxMiBiS Dw== Received: from mail-pl1-f200.google.com (mail-pl1-f200.google.com [209.85.214.200]) by mx0b-00169c01.pphosted.com (PPS) with ESMTPS id 3mthmffteh-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Thu, 05 Jan 2023 04:07:54 -0800 Received: by mail-pl1-f200.google.com with SMTP id p14-20020a170902e74e00b00192f6d0600eso2198665plf.3 for ; Thu, 05 Jan 2023 04:07:54 -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=2oPllOJAti+yFARAUdLDhKxgUEFqmZ5NUz58FCzSBrU=; b=clkY12XxCQgVh4/NiqLfRL0oFEAYD62iCnziSN/qRFqwEzL0ZrOBByuN0lqPDvSZUD vWEipMebgdK2wTc038SEqRfRCRsrJyM/2vSDzSvSzZjQg/BJKnUk5w5Fx79pKsRoH6YH ylJBeTxWsldcQ8+5JhIbl/wfjcKLND1zeL+rm8uWFYsvcljMzRVyPwsSO+xgP2/wNZSd FexFMgYvxIVFNHsteGXtUtMBQbMC6c4ScMljijQd6HJXNB8cTvuU9NrGA5AhGnVxMgvP IBb82YreK05/nk3oiJQhk8M+VC6OsilDt18mKMGkB1e3tx2qwDvoOmhZCejPZIF4UP00 n+Tg== 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=2oPllOJAti+yFARAUdLDhKxgUEFqmZ5NUz58FCzSBrU=; b=OTV3atEC1Mmw/hxYbs+AGp31JSVxtj2OjLHVfMP98nQbl8shsaNM15soYLXHRGW0e6 pK2yNVdMFPDbNMKnm+SQE/Rh31s8TN1a3yDiftsl23QjUGST6Q2iYYfuguvyQ5hY0H5f hGUa8GUqg0YSbNpsiXXCP4ThhZXKl5fsWJ1Lc1VBE9t5xu6rWwfDVhe2jPQVt6JJtdY2 tmVbBoSccLx6VSMm5hvMNhQo6//wCyCSHgWe4Hb7JzyWYvF7aEDGgTcDGK5ewYDDwlHJ LhOdTEPYcwr2oBv+3DANT7BQkVdG7XJpvc0WG66nb0pBj2TbsSB354Fz+dALzmQTXQQc qFbA== X-Gm-Message-State: AFqh2koc0jxSHyARuQKMH9RaHZzNWrc+Q7ab+goINqazKX8TuiQc0yn4 iI3RfsYHdLCqatB/SWUsAnd56gW8xIzErHEkiRLHJOE0IDIeJqihfDyoW31Xy4KLptQWQGHRObX 7RHeBvA2ErOOScAXmg6c= X-Received: by 2002:a17:902:d541:b0:192:7d9d:fceb with SMTP id z1-20020a170902d54100b001927d9dfcebmr2184159plf.83.1672920472964; Thu, 05 Jan 2023 04:07:52 -0800 (PST) X-Google-Smtp-Source: AMrXdXvLaC9/PtHho9/2a36tz71NYdy0velFhw1xBCR4MLQUVTWY9ORXFSGCs+0CyDuHVQHWvjZMavtZwBbWd9HxIYQ= X-Received: by 2002:a17:902:d541:b0:192:7d9d:fceb with SMTP id z1-20020a170902d54100b001927d9dfcebmr2184157plf.83.1672920472581; Thu, 05 Jan 2023 04:07:52 -0800 (PST) MIME-Version: 1.0 From: Venky Venkatesh Date: Thu, 5 Jan 2023 04:07:41 -0800 Message-ID: Subject: Traffic Management API Questions To: dev@dpdk.org Content-Type: multipart/alternative; boundary="00000000000081ece805f1832601" X-Proofpoint-GUID: QE8kufznTsQ8DgeZ6akFdNoO24q3cvtX X-Proofpoint-ORIG-GUID: QE8kufznTsQ8DgeZ6akFdNoO24q3cvtX 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=2023-01-05_04,2023-01-04_02,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 mlxlogscore=699 adultscore=0 suspectscore=0 mlxscore=0 clxscore=1015 priorityscore=1501 impostorscore=0 bulkscore=0 malwarescore=0 phishscore=0 spamscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2301050096 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 --00000000000081ece805f1832601 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 --00000000000081ece805f1832601 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: single/dual rate,=C2=A0private (per = node) and shared (by=C2=A0multiple nodes) shapers&= quot; are supported. However it appears that the code supports only=C2=A0single=C2=A0rate shapers. Is my understanding correct?=C2=A0
      • <= li style=3D"margin-left:15px">If not, pls point me to where dual rate shapi= ng is supported in the software based TM implementation code.=C2=A0However, if my understanding is correct, can th= e authors clarify the nature of issues they ran into in supporting dual rat= e (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 o= f my understanding and if it is accurate, the reasons from the author for n= ot supporting it)
  • At the level of the TM= API (and=C2=A0the 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 (whi= ch 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, shape= rs at port level, > 4 levels of shaping etc.)? From the reading of the d= ocumentation it appears that there may be restrictions imposed by the QoS f= ramework API on top of what TM API imposes. Can someone pls confirm this (a= nd if so, the reason for=C2=A0doing so)?

Thanks
-Venky

--00000000000081ece805f1832601--