From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-la0-f49.google.com (mail-la0-f49.google.com
 [209.85.215.49]) by dpdk.org (Postfix) with ESMTP id A60C28BA
 for <dev@dpdk.org>; Sat, 18 Oct 2014 11:09:02 +0200 (CEST)
Received: by mail-la0-f49.google.com with SMTP id q1so1811383lam.36
 for <dev@dpdk.org>; Sat, 18 Oct 2014 02:17:04 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to
 :references:mime-version:content-type:content-transfer-encoding;
 bh=K3KNJOPfrRBYQr5tM+lbaRtirBcNMdZuTGqtJb8Tza0=;
 b=MVYl3nXGdGJTqzE/51pU54I5C0YReRcwE3mUm3bMirW7yYJdk+qPHEgn0b9YOrQ+KG
 shDeJdHU0ccXUFWSZtluGAyntxyTev/LM8FA4Q07qXrbzEKHHZ/e9PiSVX5XglEzqc91
 jdPRFVbhTdbvpSi+CBBVIrTmMmem3fkUcJCU6zMduWbr0qgRt6flCafiIjTzVUfxbYai
 cV17FeCcpEr6eHQiYKrSiXOKgTNhP80JpscbE1Ip8UvPQZApnx8rDns2BLCu5nEJ7AHO
 eFL+s37C8mybygM9bUJaJxQjFWysvsTmEaLF7C4m4eF+sRlPpUhu0DtZ5aVtqCNNlMC3
 WS/A==
X-Gm-Message-State: ALoCoQnTf0P7tkraSpCsuX0XfT9zqXM7keTRc545pM6cN2UMnAQicByW2PhEFqOiXwXkgu0Xn6bD
X-Received: by 10.152.161.231 with SMTP id xv7mr14181870lab.43.1413623824039; 
 Sat, 18 Oct 2014 02:17:04 -0700 (PDT)
Received: from uryu.home.lan ([88.128.80.115])
 by mx.google.com with ESMTPSA id 5sm1172651lay.4.2014.10.18.02.17.02
 for <multiple recipients>
 (version=TLSv1.2 cipher=RC4-SHA bits=128/128);
 Sat, 18 Oct 2014 02:17:03 -0700 (PDT)
Date: Sat, 18 Oct 2014 11:16:43 +0200
From: Stephen Hemminger <stephen@networkplumber.org>
To: satish <nsatishbabu@gmail.com>
Message-ID: <20141018111643.44a9d59f@uryu.home.lan>
In-Reply-To: <CADVv77pEx1-ihzFHcj1bXu_7YBSzcvwUjpBv73pGLU+raDM+iA@mail.gmail.com>
References: <CADVv77qR5jT3dn77iuU18UFdm4cfbTs5QJ9m0YmmPE0k0NSMew@mail.gmail.com>
 <CADVv77pEx1-ihzFHcj1bXu_7YBSzcvwUjpBv73pGLU+raDM+iA@mail.gmail.com>
X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.10; x86_64-pc-linux-gnu)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Dynamic port/pipe QoS configuration
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: Sat, 18 Oct 2014 09:09:02 -0000

On Fri, 17 Oct 2014 14:59:35 -0700
satish <nsatishbabu@gmail.com> wrote:

> Hi,
> Can someone please respond to below?
> Thank you.
> 
> On Mon, Oct 13, 2014 at 3:54 PM, satish <nsatishbabu@gmail.com> wrote:
> 
> > Hi,
> > We are trying to provide QoS support for one of our clients using
> > rte_sched.
> > In our implementation we are treating each pipe as a customer.
> > So, we can have maximum of 4096 customers per sub-port.
> > Customers(pipe) can be added, deleted or modified dynamically. Each
> > customer can have different profiles.
> >
> > Currently we are using DPDK-v1.6.
> > Can I modify pipe profile during run time using rte_sched_pipe_config ()?
> >
> > Our plan is to have initial configs as below (similar to examples in DPDK)
> > [1] Specify port params at the initialization of port as below
> > static struct rte_sched_port_params port_param = {
> > :
> > :
> > .n_subports_per_port = 1,
> > .n_pipes_per_subport = 4096,
> > .qsize = {64, 64, 64, 64},
> > .pipe_profiles = pipe_profile,
> > .n_pipe_profiles = 1,
> > }
> >
> > [2]
> > static struct rte_sched_subport_params subport_param[] = {
> > {
> > .tb_rate = Link speed (1G/10G..) divided by 8 (bits),
> > .tb_size = 1000000,
> >
> > .tc_rate = {Same as tb_rate, Same as tb_rate, Same as tb_rate, Same as
> > tb_rate},
> > .tc_period = 10,
> > },
> > };
> >
> > [3]
> > static struct rte_sched_pipe_params pipe_profile[] = {
> > { /* Profile #0 */
> > .tb_rate = Link speed (1G/10G..) divided by 8 (bits)/4096 (maximum number
> > of pipes),
> > .tb_size = 1000000,
> >
> > .tc_rate = {pipe's tb_rate, pipe's tb_rate, pipe's tb_rate, pipe's
> > tb_rate},
> > .tc_period = 40,
> >
> > .wrr_weights = {16, 4, 2, 1,  16, 4, 2, 1,  16, 4, 2, 1,  16, 4, 2, 1},
> > },
> > };
> >
> > Our plan here is to initialize the pipe with default profile and modify
> > each pipe based on user configurations.
> > My questions are
> > [a] Can I modify pipe profile during run time using rte_sched_pipe_config
> > ()? (question repeated)
> > If I can modify at pipe level,
> > [b] Can we have different profiles for pipes, With one default profile at
> > initialization?
> > [c] Can we modify port level params without deleting the port using
> > rte_sched_port_config ()?

[a] no
[b] no
[c] no

Read the code.