You could add support for your qdisc to OVS, including support for queue
statistics.

On Sun, Jul 24, 2016 at 06:19:37PM +0000, fatt 3issam wrote:
> I get what you said but as I mentioned my goal is to get those stats with 
> OpenFlow so it's not a matter of seeing the packets being dropped it's about 
> the counter itself that registers them.when using tc -s I can indeed see them 
> but only the tx I need both tx and rx + when I request port stats using 
> OpenFlow the counters are always 0 like with ifconfig!
> is there any other tool that can make packets drop on veth interfaces or is 
> there any possible way that I can register the correct port stats?
> Best regards.---------------------------------
> 
> > Date: Sun, 24 Jul 2016 11:05:27 -0700
> > From: b...@ovn.org
> > To: fat...@hotmail.com
> > CC: discuss@openvswitch.org
> > Subject: Re: [ovs-discuss] ifconfig counters issue!
> > 
> > On Sun, Jul 24, 2016 at 10:29:43AM +0000, fatt 3issam wrote:
> > > I'm trying to test poor connexion networks. So in a simple linear 
> > > topology (host1 ---- switch1 ------ (s2-eth2)switch2(s2-eth1) ----- 
> > > host2) I created packet loss (50%) in the interface s2-eth2 using the tc 
> > > command, I pinged from host1 to host2 and indeed the ping results are 
> > > around the 50% loss. Now the problem is when I try to prove these results 
> > > with ifconfig I'm seeing that the rx/tx drop counts are always 0 (the 
> > > same goes for the errors/overruns/collisions counters with their specific 
> > > tests of course)!!!
> > > P.S: I also tried to jam the network by creating some background trafic 
> > > with iperf tool but still seeing 0s!
> > > How can I affect ifconfig counters or how to actually make veth 
> > > interfaces feel what's going on! because I need to have those numbers 
> > > registred on the port's stats to get them from OpenFlow after!!
> > > I hope that this issue is clear and thanks in advance.Best regards.       
> > >                                   
> > 
> > This doesn't seem to have anything to do with OVS.
> > 
> > I believe that when TC drops a packet, the drops will be accounted by
> > the packet scheduler rather than by the interface, so you should be able
> > to use some "tc -s" command to view drops.
>                                         
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to