From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Tomasz Bursztyka <tomasz.bursztyka@linux.intel.com>
Cc: Eric Leblond <eric@regit.org>,
Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>,
Patrick McHardy <kaber@trash.net>,
Julien Vehent <julien@linuxwall.info>
Subject: Re: [Nftables RFC] High level library proposal
Date: Tue, 23 Apr 2013 13:31:13 +0200 [thread overview]
Message-ID: <20130423113112.GB3348@localhost> (raw)
In-Reply-To: <51765F2E.9000909@linux.intel.com>
On Tue, Apr 23, 2013 at 01:15:10PM +0300, Tomasz Bursztyka wrote:
> Hi Eric and Pablo,
> >>>I don't get why you may need something different than libmnl or libnl.
> >>
> >>I don't think Tomasz need it but future application developers will
> >>really love to avoid to learn how netlink messages are build.
>
> I actually need this flexibility. But indeed, it's thought to hide
> netlink IOs anyway.
[...]
> >I was referring to the driver switch that he wants to introduce to
> >select libnl or libmnl in runtime, it makes no sense to me.
>
> It's easy to support it.
[...]
Again, you say you need this driver thing, but you will not escape
without explaining me why you need this.
Regards.
next prev parent reply other threads:[~2013-04-23 11:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 13:41 [Nftables RFC] High level library proposal Tomasz Bursztyka
2013-04-17 13:52 ` Victor Julien
2013-04-19 6:50 ` Tomasz Bursztyka
2013-04-19 10:05 ` Pablo Neira Ayuso
2013-04-19 11:26 ` Tomasz Bursztyka
2013-04-19 12:11 ` Pablo Neira Ayuso
2013-04-22 23:03 ` Eric Leblond
2013-04-22 23:50 ` Pablo Neira Ayuso
2013-04-23 10:15 ` Tomasz Bursztyka
2013-04-23 11:31 ` Pablo Neira Ayuso [this message]
2013-04-23 11:55 ` Tomasz Bursztyka
2013-04-23 10:15 ` Tomasz Bursztyka
2013-04-22 20:05 ` Jesper Dangaard Brouer
2013-04-22 22:26 ` Eric Leblond
2013-04-23 7:27 ` Fabio M. Di Nitto
2013-04-23 10:15 ` Tomasz Bursztyka
2013-04-23 18:49 ` Jesper Dangaard Brouer
2013-04-24 6:06 ` Tomasz Bursztyka
2013-04-24 11:23 ` Jesper Dangaard Brouer
2013-04-24 15:35 ` Stephen Hemminger
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=20130423113112.GB3348@localhost \
--to=pablo@netfilter.org \
--cc=eric@regit.org \
--cc=julien@linuxwall.info \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=tomasz.bursztyka@linux.intel.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).