From: Pavel Simerda <psimerda@redhat.com>
To: Richard Alpe <richard.alpe@ericsson.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH iproute2] tipc: introduce TIPC configuration tool
Date: Thu, 4 Jun 2015 13:30:43 -0400 (EDT) [thread overview]
Message-ID: <423324682.6031901.1433439043244.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <5570393F.9060401@ericsson.com>
----- Original Message -----
> From: "Richard Alpe" <richard.alpe@ericsson.com>
> To: "Pavel Simerda" <psimerda@redhat.com>, "Stephen Hemminger" <stephen@networkplumber.org>
> Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
> Sent: Thursday, June 4, 2015 1:40:47 PM
> Subject: Re: [PATCH iproute2] tipc: introduce TIPC configuration tool
>
> On 2015-06-04 12:23, Pavel Simerda wrote:
> > ----- Original Message -----
> >> From: "Stephen Hemminger" <stephen@networkplumber.org>
> >> To: "richard alpe" <richard.alpe@ericsson.com>
> >> Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
> >> Sent: Thursday, May 21, 2015 11:43:40 PM
> >> Subject: Re: [PATCH iproute2] tipc: introduce TIPC configuration tool
> >>
> >> On Thu, 7 May 2015 15:07:35 +0200
> >> <richard.alpe@ericsson.com> wrote:
> >>
> >>> From: Richard Alpe <richard.alpe@ericsson.com>
> >>>
> >>> This is the new tipc tool that utilizes the relativly new TIPC netlink
> >>> API
> >>> in
> >>> the kernel. Introducing this tool into iproute2 has been discussed
> >>> previously.
> >>>
> >>> For more information about the design decisions of this tool, see the
> >>> README
> >>> file.
> >>>
> >>> There isn't yet a manpage for the this tool. I will start to write one
> >>> once
> >>> I
> >>> submitted this for review.
> >>>
> >>> Richard Alpe (1):
> >>> tipc: add new TIPC configuration tool
> >>
> >> I went ahead and merged this.
> >> It does add dependency on libmnl which the distribution maintainers will
> >> have
> >> to add to their stuff.
> >
> > Does the new dependency suggest the whole iproute2 is moving to libmnl?
> That is what I was told and the reason I wrote "tipc" based on libmnl.
>
> Regards
> Richard
That is great news, I was at first afraid that it was a random decision limited
to tipc. Is there any plan for the move? I might just as well participate. Also
I found out that some things are done using ioctl instead of netlink,
especially in ip-tunnel. I'd happily be part of a larger scale iproute2 cleanup.
Cheers,
Pavel
> > Or is
> > there a good reason to use an external netlink library as well as an
> > internal one?
> >
> > Cheers,
> >
> > Pavel
> >
> >>
> >>
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe netdev" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>
>
>
prev parent reply other threads:[~2015-06-04 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 13:07 [PATCH iproute2] tipc: introduce TIPC configuration tool richard.alpe
2015-05-07 13:07 ` [PATCH iproute2] tipc: add new " richard.alpe
2015-05-21 21:43 ` [PATCH iproute2] tipc: introduce " Stephen Hemminger
2015-06-04 10:23 ` Pavel Simerda
2015-06-04 11:40 ` Richard Alpe
2015-06-04 17:30 ` Pavel Simerda [this message]
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=423324682.6031901.1433439043244.JavaMail.zimbra@redhat.com \
--to=psimerda@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richard.alpe@ericsson.com \
--cc=stephen@networkplumber.org \
--cc=tipc-discussion@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).