From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: "David S. Miller" <davem@davemloft.net>, netdev@oss.sgi.com
Subject: Re: patch: annoying u32 double listing
Date: Sun, 6 Feb 2005 23:24:50 +0100 [thread overview]
Message-ID: <20050206222450.GX31837@postel.suug.ch> (raw)
In-Reply-To: <1107726133.1055.34.camel@jzny.localdomain>
* jamal <1107726133.1055.34.camel@jzny.localdomain> 2005-02-06 16:42
> On Sun, 2005-02-06 at 16:29, Thomas Graf wrote:
>
> > assign filters attached to it, i.e. listing filters based on
> > parent == XX: && dev == %DEV will result in the filters being listed
> > for both the qdisc and the class. I haven't found a fix that wouldn't
> > break many scripts so if you have a good idea, go ahead. ;->
>
> I cant say ive run into this one - mostly i attach filters to root.
> Example script?
See the post as reply to Patick's comment. You won't notice it in
tc because it doesn't output complete trees.
> BTW, cycles allow me to work on the eaction stuff today. So far
> ive come to the conclusion that whats really needed to simplify
> writting some actions is to just provide generic methods they
> can use without them necessarily knowing details. I hope to test
> later on, maybe write a simple action and its user apce piece, and post
> patch.
Sounds good, I've been mostly occupied by writing a API documentation
to libnl and clean it up which almost doubled its usefulnes. There
is still some effort to go into the core to make it easier to use for
applications needing non blocking sockets or weird multiplexing.
The traffic control part is slowly evoling but it take some more time
to implement all the remaining qdiscs and classifiers. A bit of luck
allowed me to provide a XML based external interface to other
applications. It should be easy to extend it to make it bidirectional
and get distributed configuration via some kind of existing or
new protocol. The most problematic issue remaining is byte ordering.
I guess I will end up having all the modules define their part of
the grammar specifying the required byte order of every field and
have a generic parser to do transformations as necessary.
next prev parent reply other threads:[~2005-02-06 22:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-06 19:49 patch: annoying u32 double listing jamal
2005-02-06 20:44 ` 2.4.29 version: " jamal
2005-02-06 21:29 ` Thomas Graf
2005-02-06 21:42 ` jamal
2005-02-06 22:24 ` Thomas Graf [this message]
2005-02-06 21:47 ` Patrick McHardy
2005-02-06 22:12 ` Thomas Graf
2005-02-06 21:39 ` Patrick McHardy
2005-02-06 21:55 ` Patrick McHardy
2005-02-06 22:02 ` jamal
2005-02-06 23:17 ` Patrick McHardy
2005-02-07 6:36 ` David S. Miller
2005-02-07 13:49 ` jamal
2005-02-09 4:56 ` David S. Miller
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=20050206222450.GX31837@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--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).