Thread (39 messages) 39 messages, 5 authors, 2005-02-22

Re: [RFC] batched tc to improve change throughput

From: Thomas Graf <tgraf@suug.ch>
Date: 2005-01-20 17:19:40

* Stephen Hemminger [ref] 2005-01-20 09:06
On Thu, 20 Jan 2005 16:35:59 +0100
Thomas Graf [off-list ref] wrote:
quoted
* jamal [ref] 2005-01-20 09:42
quoted
I like it. Assuming we can have arbitrary hierachies; you just show one
level - but that may be just the example at hand. Given that should be
able to meet the layout requirements that Lennert alluded to earlier.
It doesn't include any context code, the BNF:

PARSER    := TOPNODE*
TOPNODE   := NODELIST DESC LONG_DESC
NODELIST  := NODE*
NODE      := DESC [ NODELIST ] [ ARGUMENT ] [ ATTRS ] [ END_POINT ]
END_POINT := possible end of command
ATTRS     := ATTR*
ATTR      := KEY [ VALUE ]
ARGUMENT  := VALUE [ DESC ]

Not sure if this helps, I attached a complete module below.
A couple additional suggestions.  It would be great to get a useful API
to for 'tc' that is one step above actual low level netlink stuff.
Planned. Trying to reuse an existing grammar but didn't found that
suits well enough yet.
And it would be great to reuse some existing scripting language grammar
and parsing library infrastructure.
Tried very hard to do so. I'd really like to build upon readline and
its completion method but most parser generators are not made to get along
with readline + completion. A c++ hack exist but doesn't really work
with completion. That's why I wrote my own grammar definition thing.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help