From: Florian Westphal <fw@strlen.de>
To: Florian Westphal <fw@strlen.de>,
Pablo Neira Ayuso <pablo@netfilter.org>,
Netfilter Development <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH libnetfilter_queue v3 1-5/5] src: Speed-up
Date: Mon, 7 Feb 2022 11:44:52 +0100 [thread overview]
Message-ID: <20220207104452.GA25000@breakpoint.cc> (raw)
In-Reply-To: <YgBmr3+IqGXQ4M6E@slk1.local.net>
Duncan Roe <duncan_roe@optusnet.com.au> wrote:
> There is no pkt_buff layout freeze. If we want to change it in future, we bump
> the major version of libnetfilter_queue.so, same as we would do if changing the
> signature of an existing function.
ABI breakage is bad, just say no.
next prev parent reply other threads:[~2022-02-07 10:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 3:16 [PATCH libnetfilter_queue v3 0/5] Speed-up Duncan Roe
2022-01-09 3:16 ` [PATCH libnetfilter_queue v3 1/5] src: eliminate packet copy when constructing struct pkt_buff Duncan Roe
2022-01-09 3:16 ` [PATCH libnetfilter_queue v3 2/5] src: Avoid compiler warning Duncan Roe
2022-01-09 3:16 ` [PATCH libnetfilter_queue v3 3/5] src: Use more meaningful name in callback.c Duncan Roe
2022-01-09 3:16 ` [PATCH libnetfilter_queue v3 4/5] build: doc: Eliminate doxygen warnings Duncan Roe
2022-01-09 3:16 ` [PATCH libnetfilter_queue v3 5/5] src: struct pktbuff is no longer opaque Duncan Roe
2022-01-17 23:58 ` [PATCH libnetfilter_queue v3 1-5/5] src: Speed-up Duncan Roe
2022-01-18 1:11 ` Pablo Neira Ayuso
2022-01-20 3:56 ` Duncan Roe
2022-01-20 6:27 ` Florian Westphal
2022-01-21 2:36 ` Duncan Roe
2022-01-23 2:03 ` Duncan Roe
2022-01-20 12:04 ` Florian Westphal
2022-01-20 12:40 ` Pablo Neira Ayuso
2022-02-22 1:39 ` Duncan Roe
2022-02-07 0:24 ` Duncan Roe
2022-02-07 10:44 ` Florian Westphal [this message]
2022-01-21 3:19 ` Duncan Roe
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=20220207104452.GA25000@breakpoint.cc \
--to=fw@strlen.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.