All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andre D. Correa" <andre.correa@pobox.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] XML for tc hierarchy representation
Date: Mon, 15 Aug 2005 20:11:18 +0000	[thread overview]
Message-ID: <4300F6E6.6060901@pobox.com> (raw)
In-Reply-To: <4300E025.9030408@pobox.com>


In fact I'm just search for an XML representation of tc hierarchy. 
Although I could design my own, using a reviewed and "widely accepted" 
schema makes more sense to me. I'm not testing or planning to use LTCM.

Tks anyway...

Andre


Shane O'Hanlon wrote:
> I just tried to get that code working some of the test programs worked
> some did not I could not find a versioning file. Have you had more
> success in getting it to work. I would like to get it too work.
> 
> Kernel 2.6.11.7
> 
> Here is the output of the test programs some failed some succeeded but I
> am sure its just my libs are not the correct version
> 
> output of e00
> created dev_interface for eth0
> pfifo qdisc {
>         limit: 0
> }
> 
> output of e01
> created dev_interface for eth0
> failure: netlink failure
> 
> output of e02
> created dev_interface for eth0
> failure: netlink failure
> 
> output of e03
> created dev_interface for eth0
> failure: netlink failure
> 
> output of e04
> created dev_interface for eth0
> qdisc is of type pfifo
> 
> output of e05
> failure: netlink failure
> 
> output of e06
> fifo qdisc stars with limit = 100
> failure: netlink failure
> 
> output of e07
> creating root qdisc
> failure: netlink failure
> 
> output of e08
> qdisc 1:0
> 
> output of e09
> creating root qdisc
> failure: netlink failure
> 
> output of e10
> creating root qdisc
> failure: netlink failure
> 
> output of e11
> 
> output of e12
> created dev_interface for eth0
> failure: system reply: invalid arguments
> 
> 
> 
> On Mon, 2005-08-15 at 15:34 -0300, Andre D. Correa wrote:
> 
>>Hi list, I would like to know about any proposed XML representation for 
>>tc objects hierarchy. I found something at "LTCM, a Linux QoS API 
>>Library" (http://artemis.av.it.pt/~ltcmmm/) that looks like a start, but 
>>any others are welcome.
>>
>>I'm starting a project to automatically syncronize traffic shape rules 
>>between servers and thought XML is the best way to represent tc hierarchy.
>>
>>Tks in advance for any information.
>>
>>--------------------------------------------------------------------
>>Andre D. Correa, CISSP         |  Visite meus projetos pessoais:
>>andre.correa (at) pobox.com    |  Visit my personal projects:
>>http://andre.hiperlinks.com.br |  -http://malware.hiperlinks.com.br
>>Sao Paulo / SP / Brazil        |  -http://www.linuximq.net/
>>--------------------------------------------------------------------
>>
>>_______________________________________________
>>LARTC mailing list
>>LARTC@mailman.ds9a.nl
>>http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
> 
> 
> 

--------------------------------------------------------------------
Andre D. Correa, CISSP         |  Visite meus projetos pessoais:
andre.correa (at) pobox.com    |  Visit my personal projects:
http://andre.hiperlinks.com.br |  -http://malware.hiperlinks.com.br
Sao Paulo / SP / Brazil        |  -http://www.linuximq.net/
--------------------------------------------------------------------


_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

      reply	other threads:[~2005-08-15 20:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 18:34 [LARTC] XML for tc hierarchy representation Andre D. Correa
2005-08-15 20:11 ` Andre D. Correa [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=4300F6E6.6060901@pobox.com \
    --to=andre.correa@pobox.com \
    --cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.