From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <srikanth044@gmail.com>
Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com
 [209.85.220.177]) by dpdk.org (Postfix) with ESMTP id D96C32E89
 for <dev@dpdk.org>; Wed,  5 Nov 2014 02:19:40 +0100 (CET)
Received: by mail-vc0-f177.google.com with SMTP id hq12so3736408vcb.8
 for <dev@dpdk.org>; Tue, 04 Nov 2014 17:29:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=ICkjOr8uL+zsr9VA2ngyX7ZKLP5zOrFApHXK6kS+eTY=;
 b=VYVd7SKFFaLzNlp1U6HpVbe7lG+j+KLrSAxKnDz7nzdmpBVG6mqQSj7lzLAwCK2u4x
 h9E4/F23lE63ldPFQITpodcIpRl0OHZyMtrd83/KnC7CmpKudOlWHJzRRjsRc3Oqb/54
 flNgIiFSPokcvOnxKDUlVClLC6YdHnXRlSour/2hl9CZTk8lRnp7k6UNn74xTrQYSUXr
 h7pTz4p8xRrfuZMveuZjr0QYcrTid+9ozcqU5HpXRdHFLmaFo6zhtltKI+xEnm9py0SY
 3ku4dK3hHd3dGGM7QIkzXoqTuWthcaQ25BEzuqY1R/D+PxN5kZB/c+/GHoUyOu3kvMnO
 bWgg==
MIME-Version: 1.0
X-Received: by 10.220.128.71 with SMTP id j7mr3261259vcs.22.1415150940887;
 Tue, 04 Nov 2014 17:29:00 -0800 (PST)
Received: by 10.31.10.21 with HTTP; Tue, 4 Nov 2014 17:29:00 -0800 (PST)
In-Reply-To: <CA+8eA5=ErEWHtQJmy6gePFghdS8Li-OP3dfktiOvO6eEkEtGCg@mail.gmail.com>
References: <CA+8eA5=ErEWHtQJmy6gePFghdS8Li-OP3dfktiOvO6eEkEtGCg@mail.gmail.com>
Date: Tue, 4 Nov 2014 17:29:00 -0800
Message-ID: <CA+8eA5k0=A1N8gTGQ1zGvUsRoLvy3PCmxBHv27xE9=wxVFbR8A@mail.gmail.com>
From: Srikanth Akula <srikanth044@gmail.com>
To: dev@dpdk.org, cristian.dumitrescu@intel.com
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [dpdk-dev] Max throughput Using QOS Scheduler
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Nov 2014 01:19:42 -0000

Hi all,

Can anybody answer my queries ?

thanks & Regards,
Srikanth

On Thu, Oct 30, 2014 at 9:09 AM, Srikanth Akula <srikanth044@gmail.com>
wrote:

> Hello All ,
>
> I am currently trying to implement QOS scheduler using DPDK 1.6 . I have
> configured 1 subport , 4096 pipes for the sub port and 4 TC's and 4 Queues .
>
> Currently i am trying to send packets destined to single Queue of the
> available 16 queues of one of the pipe .
>
> Could some body explain what could be the throughput we can achieve using
> this scheme.  The reason for asking this is , i could sense different
> behavior each time when i send traffic destined to different destination
> Queues  .
>
> for example :
>
> 1. << Only one stream>>> Stream destined Q0 of TC0 ..
>
>
> 2. << 4 streams >>>> 1st Stream destined for Q3 of Tc3 ...
>                                  2nd stream destined for Q2 of Tc2
>                                  3rd stream destined for Q1 of TC1
>                                  4th Stream destined for Q0 of TC0
>
> Is there any difference between scheduler behavior  for above two
> scenarios  while enqueing and de-queueing ??
>
> Queue size is 64 , and number of packets enqueud and dequeued is 64 as
> well.
> And what is the improvements i would gain if i move to DPDK 1.7 w.r.t QOS ?
>
>
> Could you please clarify my queries ?
>
>
> Thanks & Regards,
> Srikanth
>
>
>