[Top] [All Lists]

Re: [RFC] batched tc to improve change throughput

To: hadi@xxxxxxxxxx
Subject: Re: [RFC] batched tc to improve change throughput
From: Dan Siemon <dan@xxxxxxxxxxxxx>
Date: Sat, 12 Feb 2005 17:07:13 -0500
Cc: netdev@xxxxxxxxxxx
In-reply-to: <1108215923.1126.132.camel@jzny.localdomain>
References: <> <1106002197.1046.19.camel@jzny.localdomain> <> <1106058592.1035.95.camel@jzny.localdomain> <> <1106144009.1047.989.camel@jzny.localdomain> <> <1106232168.1041.125.camel@jzny.localdomain> <> <1106576005.1652.1292.camel@jzny.localdomain> <> <1106747313.1107.7.camel@jzny.localdomain> <1108134446.5523.22.camel@ganymede> <1108215923.1126.132.camel@jzny.localdomain>
Sender: netdev-bounce@xxxxxxxxxxx
On Sat, 2005-12-02 at 08:45 -0500, jamal wrote:
> On first impression, this looks very nice - I think you got the object
> hierachy figured etc; i will look closely later.
> What would be really interesting is to see (gulp) a SOAP/xml interface
> on top of this. Is this something you can do with those "bindings"?

Yes, a SOAP/XML-RPC interface should be quite possible.  This is one of
the main reasons I went to the trouble of creating the Mono bindings.  I
need to create some sort of XML interface to LQL in the next few weeks.

> It seems to me from a library perspective, youa nd Thomas may have to
> sync. And restricting to just QoS maybe be a limitation (netlink is the
> friend you are looking for; so from networking perspective, give them 
> GUI clikers ways to set routes, static IPSEC SAs etc). Oh and it would
> be interesting to have events (see that link come up down etc)

I named the project Linux QoS Library before I realized that interface
parameters etc could be manipulated via Netlink.  I have no intention of
limiting LQL to just QoS features.  Eventually I'll probably stop
referring to it as Linux QoS Library and just use LQL.

As for combining my work with Thomas, I'm certainly willing to discuss

OpenPGP key:
Key fingerprint: FB0A 2D8A A1E9 11B6 6CA3  0C53 742A 9EA8 891C BD98

<Prev in Thread] Current Thread [Next in Thread>