From: David Miller <davem@davemloft.net>
To: richard.alpe@ericsson.com
Cc: netdev@vger.kernel.org, tipc-discussion@lists.sourceforge.net
Subject: Re: [PATCH net-next v1 00/17] tipc: new compat layer for the legacy NL API
Date: Mon, 09 Feb 2015 13:21:14 -0800 (PST) [thread overview]
Message-ID: <20150209.132114.285702672812314395.davem@davemloft.net> (raw)
In-Reply-To: <1423471819-23112-1-git-send-email-richard.alpe@ericsson.com>
From: <richard.alpe@ericsson.com>
Date: Mon, 9 Feb 2015 09:50:02 +0100
> This is a compatibility / transcoding layer for the old netlink API.
> It relies on the new netlink API to collect data or perform actions
> (dumpit / doit).
>
> The main benefit of this compat layer is that it removes a lot of
> complex code from the tipc core as only the new API needs to be able
> harness data or perform actions. I.e. the compat layer isn't concerned
> with locking or how the internal data-structures look. As long as the
> new API stays relatively intact the compat layer should be fine.
>
> The main challenge in this compat layer is the randomness of the legacy
> API. Some commands send binary data and some send ASCII data, some are
> very picky in optimizing there buffer sizes and some just don't care.
> Most legacy commands put there data in a single TLV (data container) but some
> segment the data into multiple TLV's. This list of randomness goes on and on..
Series applied, thanks.
prev parent reply other threads:[~2015-02-09 21:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 8:50 [PATCH net-next v1 00/17] tipc: new compat layer for the legacy NL API richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 01/17] tipc: move and rename the legacy nl api to "nl compat" richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 02/17] tipc: convert legacy nl bearer dump to nl compat richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 03/17] tipc: convert legacy nl bearer enable/disable " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 04/17] tipc: convert legacy nl link stat " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 05/17] tipc: convert legacy nl link dump " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 06/17] tipc: convert legacy nl link prop set " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 07/17] tipc: convert legacy nl link stat reset " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 08/17] tipc: convert legacy nl name table dump " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 09/17] tipc: convert legacy nl socket " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 10/17] tipc: convert legacy nl media " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 11/17] tipc: convert legacy nl node " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 12/17] tipc: convert legacy nl node addr set " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 13/17] tipc: convert legacy nl net id " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 14/17] tipc: convert legacy nl net id get " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 15/17] tipc: convert legacy nl stats show " richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 16/17] tipc: nl compat add noop and remove legacy nl framework richard.alpe
2015-02-09 8:50 ` [PATCH net-next v1 17/17] tipc: remove tipc_snprintf richard.alpe
2015-02-09 21:21 ` David Miller [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=20150209.132114.285702672812314395.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=richard.alpe@ericsson.com \
--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).