From: Dan Siemon <dan@coverfire.com>
To: netdev@oss.sgi.com
Cc: hadi@cyberus.ca
Subject: Re: [RFC] batched tc to improve change throughput
Date: Fri, 11 Feb 2005 10:07:26 -0500 [thread overview]
Message-ID: <1108134446.5523.22.camel@ganymede> (raw)
In-Reply-To: <1106747313.1107.7.camel@jzny.localdomain>
On Wed, 2005-26-01 at 08:48 -0500, jamal wrote:
> Your call really - you are the one who is going to maintain it;->
> As for ease of use and avoiding users from knowing details of how
> tlvs are put together etc - i think it doesnt matter how thats done
> underneath the hood; it is still doable on top of current libnetlink. In
> other words whats required, IMO, is something that hides netlink totaly
> so that the programmer/user doesnt even get to see TLVs.
(Sorry to join this thread so late.)
I'd like to make a little plug for my Linux QoS Library (LQL) [1]
project. LQL provides an abstraction of the kernel QoS features. Full
API documentation is available from the website.
I already have working bindings for one high level language (C# on Mono)
[2]. Creating bindings for Python, Perl etc should be quite easy.
Someone recently emailed me about starting work on Perl bindings.
There is still lots of work to do. Support for more QDiscs and
classifiers is needed and the socket handling code needs a rewrite to
better handle errors. Work continues and these things will be fixed.
[1] - http://www.coverfire.com/lql/
[2] - http://www.coverfire.com/lql-sharp/
--
OpenPGP key: http://www.coverfire.com/files/pubkey.txt
Key fingerprint: FB0A 2D8A A1E9 11B6 6CA3 0C53 742A 9EA8 891C BD98
next prev parent reply other threads:[~2005-02-11 15:07 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-17 15:23 [RFC] batched tc to improve change throughput Thomas Graf
2005-01-17 15:45 ` jamal
2005-01-17 16:05 ` Thomas Graf
2005-01-17 16:36 ` jamal
2005-01-17 16:56 ` Thomas Graf
2005-01-17 22:49 ` jamal
2005-01-18 13:44 ` Thomas Graf
2005-01-18 14:29 ` jamal
2005-01-18 14:36 ` Lennert Buytenhek
2005-01-18 14:43 ` jamal
2005-01-18 15:07 ` Thomas Graf
2005-01-18 15:20 ` Lennert Buytenhek
2005-01-19 14:24 ` jamal
2005-01-18 14:58 ` Thomas Graf
2005-01-18 15:23 ` Lennert Buytenhek
2005-01-19 14:13 ` jamal
2005-01-19 14:36 ` Thomas Graf
2005-01-19 16:45 ` Werner Almesberger
2005-01-19 16:54 ` Thomas Graf
2005-01-20 14:42 ` jamal
2005-01-20 15:35 ` Thomas Graf
2005-01-20 17:06 ` Stephen Hemminger
2005-01-20 17:19 ` Thomas Graf
2005-01-24 14:13 ` jamal
2005-01-24 15:06 ` Thomas Graf
2005-01-26 13:48 ` jamal
2005-01-26 14:35 ` Thomas Graf
2005-02-11 15:07 ` Dan Siemon [this message]
2005-02-12 13:45 ` jamal
2005-02-12 14:29 ` Thomas Graf
2005-02-12 22:07 ` Dan Siemon
2005-02-12 22:32 ` Thomas Graf
2005-02-14 0:23 ` Dan Siemon
2005-02-14 14:27 ` Thomas Graf
2005-02-15 20:28 ` Dan Siemon
2005-02-15 20:47 ` Thomas Graf
2005-02-22 21:40 ` Dan Siemon
2005-02-22 23:15 ` Thomas Graf
2005-01-18 15:07 ` Werner Almesberger
2005-01-19 14:08 ` Thomas Graf
2005-01-19 16:33 ` Werner Almesberger
2005-01-19 17:22 ` Thomas Graf
2005-01-17 18:00 ` Stephen Hemminger
2005-01-17 18:02 ` Stephen Hemminger
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=1108134446.5523.22.camel@ganymede \
--to=dan@coverfire.com \
--cc=hadi@cyberus.ca \
--cc=netdev@oss.sgi.com \
/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).