From: jamal <hadi@cyberus.ca>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: Thomas Graf <tgraf@suug.ch>, Patrick McHardy <kaber@trash.net>,
Stephen Hemminger <shemminger@osdl.org>,
netdev@oss.sgi.com, Werner Almesberger <werner@almesberger.net>
Subject: Re: [RFC] batched tc to improve change throughput
Date: 19 Jan 2005 09:24:26 -0500 [thread overview]
Message-ID: <1106144666.1049.994.camel@jzny.localdomain> (raw)
In-Reply-To: <20050118152017.GA11798@xi.wantstofly.org>
On Tue, 2005-01-18 at 10:20, Lennert Buytenhek wrote:
> On Tue, Jan 18, 2005 at 09:43:51AM -0500, jamal wrote:
>
> > > If you do this, please consider using Juniper config syntax instead
> > > of doing it the Cisco/quagga way.
> >
> > Juniper is XML driven config files?
>
> Uhm, no :) The main advantage over Cisco (IMHO, the last thing I want
> is to start a holy war) is hierarchical config syntax, and the ability
> to commit/rollback all your changes in one go. It's unfortunately
> rather more verbose, though.
As long as a machine(as opposed to a human) is worrying about the
verbosity - should be fine ;->
> Example at the bottom.
It has a well defined structure. Do you know if the publish the bnf to
it? Are these guys gonna come after us if we replicate it you think?
>
> > btw, libio uses libevent; i recall you said you had some alternative to
> > it.
>
> Yeah, ivykis (http://libivykis.sourceforge.net/) has been happily used
> in-house at my last job for years but never really caught on anywhere
> else, which is perhaps because I never did much lobbying for it. The
> way it works also requires all code written for it to be fully async
> (can't use blocking code anywhere), which I think is an advantage but
> everyone else thinks is a disadvantage.
very similar to libevent. I am gonna start using yours because then i
could send you emails which start with "Dear sir, .. i have doubts
because it doesnt work" ;->
cheers,
jamal
next prev parent reply other threads:[~2005-01-19 14:24 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 [this message]
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
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=1106144666.1049.994.camel@jzny.localdomain \
--to=hadi@cyberus.ca \
--cc=buytenh@wantstofly.org \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
--cc=tgraf@suug.ch \
--cc=werner@almesberger.net \
/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