From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: Patrick McHardy <kaber@trash.net>,
Stephen Hemminger <shemminger@vyatta.com>,
netdev@vger.kernel.org
Subject: Re: PATCH WAS( Re: [ANNOUNCE] iproute2 v2.6.25
Date: Mon, 28 Apr 2008 13:52:03 +0200 [thread overview]
Message-ID: <20080428115203.GM20815@postel.suug.ch> (raw)
In-Reply-To: <1208787720.12249.207.camel@localhost>
* jamal <hadi@cyberus.ca> 2008-04-21 10:21
> On Mon, 2008-21-04 at 15:39 +0200, Patrick McHardy wrote:
>
> >
> > Yes, that would be nice, the iproute netlink infrastructure is really
> > lagging behind.
>
> Agreed.
>
> > I'm not sure which way would be preferrable, build
> > something new on top of libnl without disturbing existing users or
> > gradually port iproute on top of libnl, probably starting with the
> > netlink infrastructure.
>
> I would say build something new would be the proper way to go. Maintain
> output of ip/tc/ifconfig/route and phase them out slowly.
Personally I'm in favour of having many small tools like git, i.e.
rtnl-link-add, rtnl-link-list, etc.
Tools like NetworkManager are already using or currently being ported to
libnl and will hide almost all trivial networking configuration tasks
behind a nice gui.
Alternatively there can be an advanced configuration tool with a focus
on Linux being used as a router.
> The majority of new users out there may not have the same challenges i
> had:
> I wanted to do some simple things in a short period; i knew how to use
> libnetlink - i thought the mapping would be easy to follow from
> libnetlink to libnl; after a few hours, rather than investing more time
> i found it easier to update things on top of libnetlink.
> People who are totaly starting may find it easier to learn libnl first.
> I certainly do plan to poke fingers at libnl - i just happen to have
> something that works.
I'm not going to argue with you Jamal :-) In fact I'm pretty sure that
most of the basic tasks are really trivial with libnl and many common
tasks are now accessible via clean interfaces. I agree though that the
number of functions makes it difficult to find the proper interfaces.
That's why I'm thinking about splitting things up in components like
libnl, libnl-link, libnl-tc, etc. to separate the actual netlink library
from netlink family implementations. Won't happen before 2.0 though.
next prev parent reply other threads:[~2008-04-28 11:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 17:38 [ANNOUNCE] iproute2 v2.6.25 Stephen Hemminger
2008-04-17 20:35 ` PATCH WAS( " jamal
2008-04-17 20:46 ` Stephen Hemminger
2008-04-17 20:59 ` jamal
2008-04-17 21:08 ` Stephen Hemminger
2008-04-17 21:24 ` jamal
2008-04-18 12:45 ` jamal
2008-04-18 14:22 ` Patrick McHardy
2008-04-19 0:08 ` jamal
2008-04-19 0:59 ` Stephen Hemminger
2008-04-19 1:34 ` jamal
2008-04-19 16:45 ` Patrick McHardy
2008-04-20 11:48 ` jamal
2008-04-21 11:50 ` Patrick McHardy
2008-04-21 13:07 ` jamal
2008-04-21 13:39 ` Patrick McHardy
2008-04-21 14:21 ` jamal
2008-04-28 11:52 ` Thomas Graf [this message]
2008-04-28 11:44 ` Thomas Graf
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=20080428115203.GM20815@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).