From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qt0-f180.google.com (mail-qt0-f180.google.com [209.85.216.180]) by dpdk.org (Postfix) with ESMTP id AA07A239 for ; Wed, 13 Sep 2017 13:09:26 +0200 (CEST) Received: by mail-qt0-f180.google.com with SMTP id m35so31373347qte.1 for ; Wed, 13 Sep 2017 04:09:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=xhebN0lB3uJJL70cTCyPY8A/wfns7NltRoNE0ijznTQ=; b=PCwcP1bclK1imHs4CIODW32TBNbSMZ7NuDEoJQ4mzdBywn+vtMVJE2zanoMDjilff1 ZiT+jAIuvRLhsX1wK1t20XyyCYbuscfVuVEC31vCs7hEYTjKrnohxGRwp8DPelHPpJKJ 3FBXgR0rDFbFAturKH/UyNsyKxsd2LK1NNOZbAvqbUM6ECTixtjP/pNpJkiPydYjOYR5 mxN/kspOOmfjjthIvI/Jw0zbRYqM6vL8sm1Dwv6BMSeGhsMYaEHdTcUOH7OzKrxTteG+ l523FBX2MFeNf695PMOip9ZYDwyuD4mTA7EYRreD+2FyOYiNple0Yg9CNAYLAgDfyjUC 1Ygw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=xhebN0lB3uJJL70cTCyPY8A/wfns7NltRoNE0ijznTQ=; b=cjUUT5XXzftLGm9wYkSw5d5sl3d2/BcpKUIQOEbBtq9GJ+noqWGLtU1Yw9Ng8X8sHO Qm/2vWoBEvD8EGQcsXM3ZSwzOc5IwhD+npzdFMnVAI5ICqAI3CON+0Pgm3CfxDlOzZWx 2X9s7HFINK4foprBV61gInMXn9R4Av2Dx9dxtPY0+72Keca5n5ktXtc+pbbIrXazITIC a8YLaXwoDH2SjLaoTfkR8X1WO4SDbIAEhRIvGvoiGNiwZTXwEhVnxM8400TqttKoN/Tl JLSGzmJDdKtM55LPXtzTbYUP2VRtJI8pnlnCGd1+djcACyAit44FxqIxaTsG0arbFpii vn4Q== X-Gm-Message-State: AHPjjUg3yMuo6NhEHv+sXWFF6C2nmJPryrXGwQfS1E88zBIAwe6cMDlQ R6+8kNT+MvSinM3owlQQxZqot7SbVVIyutZ7ndXw0g== X-Google-Smtp-Source: AOwi7QB+VsVSFKCTeCt8V+iuQ3jRp6WOkEntNYOeNgbAdlH6cJEKQS+Ic8DaHr0DHSHBPu9NSlQsjUphhSFDPWcLn8Q= X-Received: by 10.200.2.147 with SMTP id p19mr23991622qtg.242.1505300966018; Wed, 13 Sep 2017 04:09:26 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.136.149 with HTTP; Wed, 13 Sep 2017 04:09:25 -0700 (PDT) In-Reply-To: <1001738220.546647.1505238931425@mail.yahoo.com> References: <1001738220.546647.1505238931425.ref@mail.yahoo.com> <1001738220.546647.1505238931425@mail.yahoo.com> From: Nikhil Jagtap Date: Wed, 13 Sep 2017 16:39:25 +0530 Message-ID: To: Manoj Mallawaarachchi , users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Help: DPDK-QoS Scheduler X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Sep 2017 11:09:27 -0000 Hi Manoj, I am not clear about your requirement. Depending on how you want to shape your traffic, you will need to init your scheduler and accordingly classify the traffic to derive the values of port/subport/pipe/tc/queue. For instance, if you want to limit band-width for different clients, your client IP can map to sub-port level. If you want to prioritise say RTP over HTTP, you can map RTP to traffic-class-0 and HTTP to traffic-class-3. Please refer the dpdk documentation for details. Nikhil On 12 September 2017 at 23:25, Manoj Mallawaarachchi wrote: > Dear Nikhil, > > Sorry directly address this mail to you, I got your email from previous > mail threads. I need some help to clarify below points related to DPDK QOS. > > 1) I'm developing L2 forwarding app based on basic L2 forwarder. So I need > to implement client IP based QoS scheduler to this forwarder , like I want > to shape HTTP traffic for client IP- 192.168.2.5 for example. > > the L2 forwarder forwarding traffic from and to INTERNET router (this is > working fine) and I'm getting DHCP from router and clients able to browse > while traffic forwarding via L2 forwarder. > > I'm not clear how can I define and implement TC and shaping to L2 > forwarder or IP-Pipeline. Specially define ports/sub ports/pipes/queues etc > to traffic flow. I go through QoS scheduler example, but it not clear to me. > > your advice highly appreciated. > > Thank you, > Manoj >