From: Jamal Hadi <hadi@shell.cyberus.ca>
To: Hisham Kotry <etsh_cucu@yahoo.com>
Cc: david-b@pacbell.net, rddunlap@osdl.org,
linux-net@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: netlink tester program
Date: Sun, 8 Jun 2003 21:35:09 -0400 (EDT) [thread overview]
Message-ID: <20030608212033.Y33230@shell.cyberus.ca> (raw)
In-Reply-To: <20030603075742.34434.qmail@web14305.mail.yahoo.com>
On Tue, 3 Jun 2003, Hisham Kotry wrote:
> It was defenitly a nice read, but the netlink2 draft
> is somewhat inconsistent, it mentions reducing the
> 32-bit length field to 16-bits and equally
> distributing the remaining 16-bits between the new
> version and extended flags fields, but the draft makes
> no further refrence to the version field. Infact the
> netlink2 message header diagram on page 16, as well as
> the pseudo message on page 28, show a 16-bits extended
> flags field with no version field in the header. So
> this is probably one of those cases in wich specs
> aren't clear enough and code usually has the final
> word in such situations.
>
> I mailed Jamal about this a while ago but never got a
> reply back.
>
apologies, I actually have a unrelated daytime job that tends to keep me
too occupied at times ;->
Netlink2 draft is work in progress. The draft tends to lag reality.
I believe what you refer to has been fixed. Refer to the slides at:
http://www.zurich.ibm.com/~rha/netlink2.pdf
> BTW, is netlink2 support planned for linux in the near
> future?
>
You will see code from us that is GPL. Consider netlink2 as a distributed
netlink. netlink is already proven so why reinvent the wheel?
Essentially you should be able to manager clusters of linux network
devices (think firewalls, routers etc) with netlink/netlink2.
There are some mechanisms for distributdness that are missing. These are
the holes we are going to fill.
Note some of the stuff i am working on at:
www.cyberus.ca/~hadi/patches/action which fits the whole forces paradigm
and works quiet well with netlink today and netlink2 next.
(I stopped updating that web page for sometime now, talk to me if
interested in the patches and if you would like to help in testing,
coding, etc)
cheers,
jamal
next prev parent reply other threads:[~2003-06-09 1:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-30 16:00 netlink tester program Randy.Dunlap
2003-05-31 0:11 ` David S. Miller
2003-05-31 3:22 ` Randy.Dunlap
2003-05-31 6:42 ` David S. Miller
2003-05-31 12:09 ` Andi Kleen
2003-06-02 17:07 ` Randy.Dunlap
2003-06-02 21:04 ` Randy.Dunlap
2003-06-02 21:56 ` David S. Miller
2003-06-03 1:56 ` David Brownell
2003-06-03 2:02 ` David S. Miller
2003-06-03 3:34 ` David Brownell
2003-06-03 3:38 ` David S. Miller
2003-06-03 3:49 ` Randy.Dunlap
2003-06-03 3:51 ` David S. Miller
2003-06-03 7:57 ` Hisham Kotry
2003-06-09 1:35 ` Jamal Hadi [this message]
2003-06-09 14:37 ` Mr. James W. Laferriere
2003-06-09 17:16 ` David S. Miller
2003-06-03 2:33 ` John S. Denker
2003-06-03 2:38 ` David S. Miller
2003-06-03 3:20 ` John S. Denker
2003-06-03 3:22 ` David S. Miller
2003-06-03 3:41 ` John S. Denker
2003-06-03 3:46 ` David S. Miller
2003-06-03 3:54 ` Randy.Dunlap
2003-06-03 3:54 ` David S. Miller
2003-06-03 3:37 ` David Brownell
2003-06-03 3:32 ` Randy.Dunlap
2003-06-03 3:35 ` 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=20030608212033.Y33230@shell.cyberus.ca \
--to=hadi@shell.cyberus.ca \
--cc=david-b@pacbell.net \
--cc=etsh_cucu@yahoo.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rddunlap@osdl.org \
/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).