From: Matthias Schiffer <mschiffer@universe-factory.net>
To: Sven Eckelmann <sven@narfation.org>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [RFC v2 0/5] batman-adv netlink query API
Date: Wed, 20 Apr 2016 09:49:25 +0200 [thread overview]
Message-ID: <57173485.2060407@universe-factory.net> (raw)
In-Reply-To: <243525463.WEoUOFbSir@bentobox>
[-- Attachment #1.1: Type: text/plain, Size: 1230 bytes --]
On 04/20/2016 09:39 AM, Sven Eckelmann wrote:
> On Wednesday 20 April 2016 09:32:19 Matthias Schiffer wrote:
> [...]
>> As I've mentioned before, regarding the batctl support, I'd love to see a
>> little library ("libbatadv"?) on top of libnl that could be used by batctl,
>> alfred and other monitoring tools (like the ones we are using in the Gluon
>> Freifunk firmwares).
>
> Hm, then we would have to make everything ABI stable. So we would loose the
> flexibility of netlink (adding more fields) again just to keep the library
> stable.
>
> Or what kind of functionality should this library expose that can be easily be
> kept stable?
>
> Kind regards,
> Sven
>
I don't understand. The same code that would we added to batctl and alfred
could just be made a library with a nicer API, so other projects can easily
reuse it. Of course, the library API/ABI would need to be designed in a way
that keeps it extensible without breaking ABI.
I'm thinking of functions like "iterate over all originators", which would
query the netlink API, and then just call a callback with the netlink
attribute set for each originator. Just a thin wrapper making things more
usable.
Regards,
Matthias
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-04-20 7:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 16:45 [B.A.T.M.A.N.] [RFC v2 0/5] batman-adv netlink query API Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 1/5] batman-adv: add generic netlink query API to replace debugfs files Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 2/5] batman-adv: netlink: add translation table query Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 3/5] batman-adv: netlink: add originator and neighbor table queries Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 4/5] batman-adv: add B.A.T.M.A.N. IV bat_{orig, neigh}_dump implementations Matthias Schiffer
2016-03-17 16:45 ` [B.A.T.M.A.N.] [RFC v2 5/5] batman-adv: add B.A.T.M.A.N. V " Matthias Schiffer
2016-03-17 17:04 ` [B.A.T.M.A.N.] [RFC v2 0/5] batman-adv netlink query API Matthias Schiffer
2016-03-18 7:09 ` Sven Eckelmann
2016-03-18 11:53 ` Matthias Schiffer
2016-04-18 10:59 ` Sven Eckelmann
2016-03-18 11:23 ` Sven Eckelmann
2016-03-18 12:00 ` Matthias Schiffer
2016-03-18 12:04 ` Sven Eckelmann
2016-03-19 8:49 ` Antonio Quartulli
2016-03-19 9:19 ` Sven Eckelmann
2016-04-18 11:10 ` Sven Eckelmann
2016-04-18 14:50 ` Simon Wunderlich
2016-04-20 2:31 ` Andrew Lunn
2016-04-20 11:39 ` Simon Wunderlich
2016-04-20 7:32 ` Matthias Schiffer
2016-04-20 7:39 ` Sven Eckelmann
2016-04-20 7:49 ` Matthias Schiffer [this message]
2016-04-20 7:53 ` Sven Eckelmann
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=57173485.2060407@universe-factory.net \
--to=mschiffer@universe-factory.net \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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