From: Ariel Rodriguez <arodriguez@callistech.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Qos scheduler question.
Date: Wed, 21 May 2014 19:55:16 -0300 [thread overview]
Message-ID: <CADoa0bY3P4WFDT04KhdWtFydDWa4OuRAJyhXuXEnvkbN9B=Uhg@mail.gmail.com> (raw)
In-Reply-To: <CADoa0bZdggnLoK22-jQExz-HqzUGRHuOuxNA9rgwFcZ85SOwqw@mail.gmail.com>
Hi , we re implementing bandwith controller per user with the dpdk qos
scheduler framework.
I want to know if the framework support dynamic changes in the
rte_sched_port structure.
For example, we want to give the possibility to change the configuration
of the different bucket rates int the port. We have a managment tool thats
allow to change the configuration of the subport , ports, and pipe. We
group a set of subscribers in a pipe. When the subscriber login in the
system, the data of the login specify the subport and pipe where the
subscriber will be bounded. What we want is give the customer the ability
to change that login information based on their bussiness logic.
So , Can we change the rte_sched_port configuration when a user apllies new
configuration to the system? . I found a solution where we just create a
parallel structure from scratch , and then notifies to the logical core
assigned to the bandwith managment via rte_ring, when the notification is
process , that core just change the reference of the rte_sched_port and
frees the old one. i imagine if the old structure has packets on his queues
, this packets are lost, and probably leaked. if there a way to achieve
this, or the framework just support a static configuration
On Tue, May 20, 2014 at 3:58 PM, Ariel Rodriguez
<arodriguez@callistech.com>wrote:
> Hi , we re implementing bandwith controller per user with the dpdk qos
> scheduler framework.
>
> I want to know if the framework support dynamic changes in the
> rte_sched_port structure.
> For example, we want to give the possibility to change the configuration
> of the different bucket rates int the port. We have a managment tool thats
> allow to change the configuration of the subport , ports, and pipe. We
> group a set of subscribers in a pipe. When the subscriber login in the
> system, the data of the login specify the subport and pipe where the
> subscriber will be bounded. What we want is give the customer the ability
> to change that login information based on their bussiness logic.
> So , Can we change the rte_sched_port configuration when a user apllies
> new configuration to the system? . I found a solution where we just create
> a parallel structure from scratch , and then notifies to the logical core
> assigned to the bandwith managment via rte_ring, when the notification
> is process , that core just change the reference of the rte_sched_port and
> frees the old one. i imagine if the old structure has packets on his queues
> , this packets are lost, and probably leaked. if there a way to achieve
> this, or the framework just support a static configuration
>
prev parent reply other threads:[~2014-05-21 22:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 18:58 Ariel Rodriguez
2014-05-21 22:55 ` Ariel Rodriguez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADoa0bY3P4WFDT04KhdWtFydDWa4OuRAJyhXuXEnvkbN9B=Uhg@mail.gmail.com' \
--to=arodriguez@callistech.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).