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 696D1A00C4; Mon, 2 Jan 2023 10:15:42 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CF1AB42D2A; Mon, 2 Jan 2023 10:15:26 +0100 (CET) Received: from mx0b-00169c01.pphosted.com (mx0b-00169c01.pphosted.com [67.231.156.123]) by mails.dpdk.org (Postfix) with ESMTP id A2E1540141 for ; Sun, 1 Jan 2023 03:29:31 +0100 (CET) Received: from pps.filterd (m0281121.ppops.net [127.0.0.1]) by mx0b-00169c01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 2BVNQnel031851 for ; Sat, 31 Dec 2022 18:29:30 -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=i0zQMikFPHUFMs3jWIfu/YHEqGhZYxIoL9BtkD/qJ44=; b=KC+8tiX+S1qXGgZQO5y5MOhn4PVWr+10YDKjiOUuJiLXwdvfkHSijUTSjDNgGhCNfXrP T5uLMigcag08w1zjF7Zx0wUa8dcDNaKX+OIDNSScsP+hROKzdH6hj5oWogFj2ysK4kDa a+kBmhR80xmYIJ9P+5+OkS8tmNyEt3cJg+omsy5bhyUgndwuXLE+IsQO3NimRLPStxxJ 5ZxZam5Js/VpE8n5B3rmysPxLubwgmZshoT5tmfOT2U5j5sqOvwPiBQzVt/kLmxeuAx1 b3tCMrjZkEAV8ADt6iJcSon4u4L8jbJeQ0QeJEZ3SbONCPz3v+EOb9tSQ3zZcBxxGEJa xw== Received: from mail-pl1-f197.google.com (mail-pl1-f197.google.com [209.85.214.197]) by mx0b-00169c01.pphosted.com (PPS) with ESMTPS id 3mtkbarwwj-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Sat, 31 Dec 2022 18:29:30 -0800 Received: by mail-pl1-f197.google.com with SMTP id u2-20020a17090341c200b00192bc565119so1562112ple.16 for ; Sat, 31 Dec 2022 18:29:30 -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=i0zQMikFPHUFMs3jWIfu/YHEqGhZYxIoL9BtkD/qJ44=; b=bzcWbyAnxsdGfxodMQp41q1BFpkIhz2VD1z4wn7nxubky+UJbZyhNtCPcFbsq4S8Gr 4NbPtqvhnWLolAXm5FrlbbOluh1pQIADlxW+ACg1Km+1vnk4ri7DQMw4a6TuxsmI4JBx +Wl8ooCah9xWUSq9uF5gjw9oB1vhmAMEdVEfe6pC9v3R3v6UQRZ4AUCNp4KI5kSZ+Wo3 AePiTPlQZuWFkXccd+gumDYqIMzpsij1PUFZPLL4OGvXlkGCo4g0WRfNQxcsX65wto2/ kNGhmkxHfQlS2WdTjpLp3zix7HRT28/do0zoA4nlDb/diSAcXahmjWLMDO+DaOpsnkBY CU3A== 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=i0zQMikFPHUFMs3jWIfu/YHEqGhZYxIoL9BtkD/qJ44=; b=IO1tqqYVP1y0W2O/Q2DLJ+iLBhDyzpnY+zsRJq4N+0GEbH7tb6D7qULB3/wu7UGyKx EY8cCwxWRNi69BUFIAi+zuD9dV2e0cL+r5c91mG+gcC9b7MlsN+WVIJPPwrG8UlXPiYf PFGqLsii2/mYDcniKSgA98v3tSxi/YtuYmT7S3h2XuDJNfhGMD2wmD0eX1VwERcaOQMX NBciO1LkDLuQ+UzgFFM3L5tp9XlPPq1s00ScJbKL3zHBqwqBdT9/ARtNP95cIdh9GzOE LSAvGiOwwnz6oJuey1JUeiVAGss4/TM0gaHHi/Cm4CFEhnEQGZkBD31VIZ1um0Pyzi3T /5jg== X-Gm-Message-State: AFqh2kpnuARe3h9i+fFoBLzP44Hx2LAvosE913i+kIWJYOWPOKWxAmb7 bM+jWOqqOB5ZFgwJ7SX9k/Qcecg9xoYRElumNkUUHBNI4UXdKtGq/P1KKBN548AXrrsbWGq3wOC 8ssZGRWbzUpkaSCnqcto= X-Received: by 2002:a62:5293:0:b0:577:1b6:ee7b with SMTP id g141-20020a625293000000b0057701b6ee7bmr2473281pfb.5.1672540169071; Sat, 31 Dec 2022 18:29:29 -0800 (PST) X-Google-Smtp-Source: AMrXdXsAKVjWe+8KtXKVUaG57INafJe27eoveZt7TFjxyvluRqLKTkDabU4cvKea+OZ7YU+WbGcvV+3fw51qjnn9a3c= X-Received: by 2002:a62:5293:0:b0:577:1b6:ee7b with SMTP id g141-20020a625293000000b0057701b6ee7bmr2473279pfb.5.1672540168667; Sat, 31 Dec 2022 18:29:28 -0800 (PST) MIME-Version: 1.0 From: Venky Venkatesh Date: Sat, 31 Dec 2022 18:29:18 -0800 Message-ID: Subject: Traffic Management API Questions To: dev@dpdk.org Content-Type: multipart/alternative; boundary="000000000000a0649e05f12a9a8d" X-Proofpoint-GUID: pMJUjI9dE2a5KnsVveydcr2XEjQVWEKT X-Proofpoint-ORIG-GUID: pMJUjI9dE2a5KnsVveydcr2XEjQVWEKT 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-31_16,2022-12-30_01,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 impostorscore=0 malwarescore=0 suspectscore=0 mlxlogscore=701 clxscore=1015 adultscore=0 phishscore=0 bulkscore=0 lowpriorityscore=0 mlxscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2301010021 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 --000000000000a0649e05f12a9a8d 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 --000000000000a0649e05f12a9a8d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
=C2=A0 Hi,
I was looking at the DPDK Traffic Managemen= t 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,=C2=A0private (= per node) and shared (by=C2=A0multiple nodes) shapers<= /span>" are supported. However it appears that the code supports only= =C2=A0single=C2=A0rate shapers. Is my understanding correct?=C2=A0
    • If not, pls point me to where dual ra= te shaping is supported in the software based TM implementation code.=C2=A0=
    • 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 sh= aping at the port level. Again the same questions as above(regarding the ac= curacy of my understanding and if it is accurate, the reasons from the auth= or for not supporting it)
  • At the level o= f the TM API (and=C2=A0the associated software TM implementation) ar= e there any restrictions on the number of levels of QoS hierarchy we can co= nstruct?
  • 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 shaper= s, shapers at port level, > 4 levels of shaping etc.)? From the reading = of the documentation it appears that there may be restrictions imposed by t= he QoS framework API on top of what TM API imposes. Can someone pls confirm= this (and if so, the reason for=C2=A0doing so)?

Thanks
-Venky

--000000000000a0649e05f12a9a8d--