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 3EE97423A1; Tue, 10 Jan 2023 09:52:32 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2B2A340691; Tue, 10 Jan 2023 09:52:32 +0100 (CET) Received: from mx0b-00169c01.pphosted.com (mx0a-00169c01.pphosted.com [67.231.148.124]) by mails.dpdk.org (Postfix) with ESMTP id 3804240689 for ; Tue, 10 Jan 2023 09:52:31 +0100 (CET) Received: from pps.filterd (m0048493.ppops.net [127.0.0.1]) by mx0a-00169c01.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 30A64Ruo028830 for ; Tue, 10 Jan 2023 00:52:30 -0800 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=paloaltonetworks.com; h=mime-version : references : in-reply-to : from : date : message-id : subject : to : content-type; s=PPS12012017; bh=ol7EiV7ne4BCN7us20uXFHO/LWcZtPMmCnKqw7R/UrI=; b=gZ/LXjCf5Juf29+PvQbySxoTx9fAb2Ju70ec4AaDjy07OhdqtGJ/6648U5ucDi6xY0Pj QSAHLVUJWKrqdHVhF3y2MHlz1E9TK5ztRQ43UuKDm9AhFNy5l05ghAeZaOryCEDUrKug ctovC9YW6vsKOWrhEXKdkyGMYmZgGMPTQeHvRR1HAwjRCjZlvGLJs/DYUI+oC7regnsc /kuaB7Mp3aXcmYattuEc8ij22QXULNjU+6Bg/RAiYFRmJYx9A/1gOJS2T1KbqJIBJydN Kc0Eo6LgTsShX+C/51t4ArodK8IjW9KfFtAHVWe090a8nk8fPQLJ+lItOfpSxhPmZex6 7w== Received: from mail-pl1-f198.google.com (mail-pl1-f198.google.com [209.85.214.198]) by mx0a-00169c01.pphosted.com (PPS) with ESMTPS id 3my8nx0fg0-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT) for ; Tue, 10 Jan 2023 00:52:30 -0800 Received: by mail-pl1-f198.google.com with SMTP id u6-20020a170903124600b00188cd4769bcso8006162plh.0 for ; Tue, 10 Jan 2023 00:52: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:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=ol7EiV7ne4BCN7us20uXFHO/LWcZtPMmCnKqw7R/UrI=; b=FGaHa8SaJarBTpKL6sfzrBbY6WfCcdpZtGoyXQcoqB1A3CsRnt2mZQ8DQfTMzIxHFC TcnZGyrosd4E5HfHeBAgm+e7OCO83NFmX0/X9+k2Zefq2RvYw820tdHijhR/sAdXxQrq sTP+36lhYGf9Rk0ndwgAbsgc++Re/a6rh25c5hkdVRO0jjGdcNsnzYW69CCj+EteNcrn z5ZlLcSeloLHr1161eEL6fmhRa2hh8B/Hy2dLNnfi29w7jV9zO8Kk5wUOlz5NTVk6/GU Dt75mirJrjCEZPENiZI5IVjD93KBErkkX3em75b9zVXrOhiMVHQuR2+h0TkCuv+2jHmb yZBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ol7EiV7ne4BCN7us20uXFHO/LWcZtPMmCnKqw7R/UrI=; b=l6lI3H7uhMEXZVGwRmTLq8+x//voMM4AxunrgItzJPJzaSDQHhNN7IgJTYDNSFRrDq 6UMm7EtyWt2tNWuyyDgUFBaW63Ek4XjMStcsPFYQiVo3O5Gq8OhOBmSF0BY67g3ktD15 FAXvoBeg/bXJv9AhT38nnKAGt3rMbaDyuFMl1YFeBCtdA7fth+cm/d0kgya/W3IJi11Z fH+q2+uY5snySwfAX9/VDd+Au0Mn5hg+uWeRGxnfS28fr6znBfsSQKO5livlyO1ukNMY 4pRFuIfTfcL20l6NhWi+k+e/PIJvHP5wGzs7GlSpFzzTR5nshA5ZPDc4AoCgCePVUlPj W88A== X-Gm-Message-State: AFqh2ko14N4ml0KPUczs4lnxQkRNm1UAVemqDFUmTUYDTRbrmCroHXl1 wRvK4VZ78ivoOML7rmckB+iF8lr7du+wWadDG/MzV/7pAYi9hXyEjVWlfoCWkuIEw55FZWJivtB hGznLGoctImi4vDposBY= X-Received: by 2002:a63:e50c:0:b0:49b:3742:9dce with SMTP id r12-20020a63e50c000000b0049b37429dcemr2848024pgh.507.1673340748891; Tue, 10 Jan 2023 00:52:28 -0800 (PST) X-Google-Smtp-Source: AMrXdXsgbqEBkKuSceF5KyEuOQKEM5C75k8t4T07edI+3hYnmDmkbwzc7e1L7f0y5efx/VBPjEJ/t3VM5esGiyQOSHM= X-Received: by 2002:a63:e50c:0:b0:49b:3742:9dce with SMTP id r12-20020a63e50c000000b0049b37429dcemr2848021pgh.507.1673340748587; Tue, 10 Jan 2023 00:52:28 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Venky Venkatesh Date: Tue, 10 Jan 2023 00:52:17 -0800 Message-ID: Subject: [2nd Try]:Re: Traffic Management API Questions To: dev@dpdk.org Content-Type: multipart/alternative; boundary="000000000000e8ce9905f1e50021" X-Proofpoint-GUID: 8q-LaqhAxCJxtU-aEhjoPYPT14ep4chK X-Proofpoint-ORIG-GUID: 8q-LaqhAxCJxtU-aEhjoPYPT14ep4chK 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-10_02,2023-01-09_02,2022-06-22_01 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 lowpriorityscore=0 mlxscore=0 malwarescore=0 bulkscore=0 phishscore=0 suspectscore=0 clxscore=1015 mlxlogscore=739 adultscore=0 impostorscore=0 spamscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2212070000 definitions=main-2301100053 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 --000000000000e8ce9905f1e50021 Content-Type: text/plain; charset="UTF-8" Hi, Can someone pls get back on these Thanks -Venky On Thu, Jan 5, 2023 at 4:07 AM Venky Venkatesh < vvenkatesh@paloaltonetworks.com> wrote: > 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 > > --000000000000e8ce9905f1e50021 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,
Can someone pls get bac= k on these
Thanks
-Venky

On Thu, Jan 5, 2023 at 4:07 AM = Venky Venkatesh <vven= katesh@paloaltonetworks.com> wrote:
Hi,
I was looking at the DP= DK Traffic Management API. I wanted to clarify some things that I understan= d from the code (for software based TM implementation (at 20.11)) vs the do= cumentation.
  • The documentation= says "Traffic shaping: single/dual rate= ,=C2=A0private (per node) and shared (by=C2=A0multiple nodes<= /u>) shapers" are supported. However it appears that the= code supports only=C2=A0single=C2=A0rate shapers. Is my understandi= ng correct?=C2=A0
    • If not, pls point = me to where dual rate shaping is supported in the software based TM impleme= ntation code.=C2=A0
    • However, if my under= standing is correct, can the authors clarify the nature of issues they ran = into in supporting dual rate (which thus prevented them from implementing i= t)?
  • 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 abo= ve(regarding the accuracy of my understanding and if it is accurate, the re= asons from the author for not 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 (which I suppose is built on lower level building bl= ocks 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 restri= ctions imposed by the 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

--000000000000e8ce9905f1e50021--