Hi Ben,
            Thank you for the answers. 

> Date: Thu, 24 Jan 2013 08:44:05 -0800
> From: b...@nicira.com
> To: cerisierfi...@hotmail.com
> CC: discuss@openvswitch.org
> Subject: Re: [ovs-discuss] Implementing hierarchy in HTB in OpenvSwitch
> 
> On Thu, Jan 24, 2013 at 02:39:12PM +0530, Mathumitha S wrote:
> > I am trying to use HTB in OpenvSwitch. Currently, OvS supports only
> > single-level of hierarchy in HTB. Am I correct? 
> 
> Yes.
> 
> > But for implementing DiffServ, it would be good if multiple levels of
> > hierarchy are supported. Hence, I read the source code and tried to
> > modify it to support multiple hierarchy levels. I found that the
> > functions related to htb such as htb_setup_qdisc, htb_setup_class and
> > others are in netdev-linux.c file. 
> 
> I imagine that this is the code that you should change.
> 
> > I went through the ovs-vsctl code and identified the functions
> > pre_create, cmd_create and post_create which are used to make entries
> > in the 'Qos' and 'queue' tables in the database. But I could not find
> > the link between the functions i.e which function is used to create
> > the queues using the tc command. 
> 
> Open vSwitch does not invoke the tc program.  Instead, it uses direct
> Netlink calls to the kernel from netdev-linux.c
> 
> > When we give ovs-vsctl create queue command, what is the sequence of
> > functions called to create the queues? 
> 
> vsctl contacts ovsdb-server and tells it to change the tables.
> ovsdb-server contacts ovs-vswitchd and tells it how the tables changed.
> The ovs-vswitchd "bridge" looks at the new table contents and passes
> them to netdev-linux via iface_configure_qos().
> netdev-linux reconfigures the kernel.
> 
> > Can somebody help me? 
> 
> I think I just did.
> 
> > Or is there a patch that is available to implement multiple levels of
> > hierarchy in HTB?
> 
> I don't know of one.
                                          
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to