From: Werner Almesberger <werner@almesberger.net>
To: jamal <hadi@cyberus.ca>
Cc: Thomas Graf <tgraf@suug.ch>, Patrick McHardy <kaber@trash.net>,
Stephen Hemminger <shemminger@osdl.org>,
netdev@oss.sgi.com
Subject: Re: [RFC] batched tc to improve change throughput
Date: Tue, 18 Jan 2005 12:07:37 -0300 [thread overview]
Message-ID: <20050118120737.I15303@almesberger.net> (raw)
In-Reply-To: <1106058592.1035.95.camel@jzny.localdomain>; from hadi@cyberus.ca on Tue, Jan 18, 2005 at 09:29:52AM -0500
jamal wrote:
> On Tue, 2005-01-18 at 08:44, Thomas Graf wrote:
> > I'm aware of [tcng] but naturally it always lags behind a bit and keeping
> > it up to date requires quite some work and I already have problems
> > finding the time for my own changes ;->
Sigh, yes, I don't have all that much time for it myself, and
my focus of interest has shifted, too. Unfortunately, everybody
I've tried to talk in to taking over its maintenance so far was
wise enough to politely pass up the offer :-(
There's also the issue of classifier construction: while I think
that the language for this is near-perfect, the internal
processing is scary at best, and doesn't produce very nice
results. I dream of a new classifier works on a state machine
constructed from single-bit classification decisions, but the
graph theory required for ordering them properly is a bit above
me. (Construction of an unordered and redundant FSM is almost
trivial - tcng can already do this.)
> > - interactive shell supporting context help + completion
>
> MUST
I'm not so sure about interactive use of "tc". In general, a
single configuration line has no meaning. You almost always
need a lot more context to understand what it does.
Think of the interactive BASIC systems on ancient PCs. There,
you would enter/edit/remove lines by their number. Now, would
you want to use something like this for C ? Me, I prefer a
free-format text editor :-)
An interactive help system that could be called from an
editor, e.g. when editing tcng configurations, would certainly
be a nice touch. But that's an orthogonal issue. A set of man,
info, etc. pages would serve nicely, too.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina werner@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2005-01-18 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
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 [this message]
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=20050118120737.I15303@almesberger.net \
--to=werner@almesberger.net \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
--cc=tgraf@suug.ch \
/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).