From: Laurent Bercot <ska-devel@skarnet.org>
To: Patrick McHardy <kaber@trash.net>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH libnftnl] src: restore static array with expression operations
Date: Mon, 23 Mar 2015 15:58:07 +0100 [thread overview]
Message-ID: <551029FF.2070300@skarnet.org> (raw)
In-Reply-To: <20150323145011.GC603@acer.localdomain>
On 23/03/2015 15:50, Patrick McHardy wrote:
> I would be surprised if the alternative provides a much smaller
> binary. Basically everything is referenced through the registered
> structures and functions called from there. I don't think it
> makes any difference.
It's the case for now, but it might not be in the future. Else,
why keep libnftnl as a separate package from nftables?
> Well, we would like to keep the callbacks. We can continue to
> look for a different solution. But either way you will have
> tons of potentially unused functions in there since the library
> resolves a lot of things at runtime.
I understand that, and don't mind the current 600k that much.
I am opposed to linking with --whole-archive on principle, but
I'll take any other solution that suits you. Any *clean* solution,
I mean. ;)
--
Laurent
prev parent reply other threads:[~2015-03-23 14:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-23 11:44 [PATCH libnftnl] src: restore static array with expression operations Pablo Neira Ayuso
2015-03-23 11:44 ` Patrick McHardy
2015-03-23 12:34 ` Pablo Neira Ayuso
2015-03-23 13:08 ` Patrick McHardy
2015-03-23 13:21 ` Laurent Bercot
2015-03-23 13:33 ` Patrick McHardy
2015-03-23 13:37 ` Laurent Bercot
2015-03-23 13:54 ` Patrick McHardy
2015-03-23 14:19 ` Laurent Bercot
2015-03-23 14:50 ` Patrick McHardy
2015-03-23 14:58 ` Laurent Bercot [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=551029FF.2070300@skarnet.org \
--to=ska-devel@skarnet.org \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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;
as well as URLs for NNTP newsgroup(s).