From: Dmitrii Banshchikov <me@ubique.spb.ru>
To: Raymond Burkholder <ray@oneunified.net>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v2 00/13] bpfilter
Date: Mon, 30 Aug 2021 16:54:59 +0400 [thread overview]
Message-ID: <20210830125459.qk62gb5ak6xij4ug@amnesia> (raw)
In-Reply-To: <42c5e32a-edb9-08a3-f37f-9def9583f5fc@oneunified.net>
On Sun, Aug 29, 2021 at 01:13:53PM -0600, Raymond Burkholder wrote:
> On 8/29/21 12:35 PM, Dmitrii Banshchikov wrote:
> > The patchset is based on the patches from David S. Miller [1] and
> > Daniel Borkmann [2].
> >
> > The main goal of the patchset is to prepare bpfilter for
> > iptables' configuration blob parsing and code generation.
>
> The referenced patches are from 2018. Since then, and since this is
> bpf-next, places like [1] indicate that we are moving on from iptables
> towards nftables.
>
> Any thoughts?
I'm not sure what kind of thoughts you expect.
If your question is why to use an outdated interface the answer
is - this is just a starting point and nothing prevents us from
having our own interface in future .
>
> [1] https://wiki.archlinux.org/title/Iptables
>
--
Dmitrii Banshchikov
next prev parent reply other threads:[~2021-08-30 12:55 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 18:35 [PATCH bpf-next v2 00/13] bpfilter Dmitrii Banshchikov
2021-08-29 18:35 ` [PATCH bpf-next v2 01/13] bpfilter: Add types for usermode helper Dmitrii Banshchikov
2021-08-29 18:35 ` [PATCH bpf-next v2 02/13] bpfilter: Add logging facility Dmitrii Banshchikov
2021-08-29 18:35 ` [PATCH bpf-next v2 03/13] tools: Add bpfilter usermode helper header Dmitrii Banshchikov
2021-08-29 18:35 ` [PATCH bpf-next v2 04/13] bpfilter: Add map container Dmitrii Banshchikov
2021-08-29 18:36 ` [PATCH bpf-next v2 05/13] bpfilter: Add codegen infrastructure Dmitrii Banshchikov
2021-08-29 18:36 ` [PATCH bpf-next v2 06/13] bpfilter: Add struct match Dmitrii Banshchikov
2021-08-29 18:36 ` [PATCH bpf-next v2 07/13] bpfilter: Add struct target Dmitrii Banshchikov
2021-08-29 18:36 ` [PATCH bpf-next v2 08/13] bpfilter: Add struct rule Dmitrii Banshchikov
2021-08-29 18:36 ` [PATCH bpf-next v2 09/13] bpfilter: Add struct table Dmitrii Banshchikov
2021-08-29 18:36 ` [PATCH bpf-next v2 10/13] bpfilter: Add table codegen Dmitrii Banshchikov
2021-08-29 18:36 ` [PATCH bpf-next v2 11/13] bpfilter: Add handling of setsockopt() calls Dmitrii Banshchikov
2021-08-29 18:36 ` [PATCH bpf-next v2 12/13] bpfilter: Add filter table Dmitrii Banshchikov
2021-08-30 19:45 ` Alexei Starovoitov
2021-08-30 20:54 ` Dmitrii Banshchikov
2021-08-30 23:45 ` Alexei Starovoitov
2021-08-31 12:52 ` Dmitrii Banshchikov
2021-08-31 15:45 ` Alexei Starovoitov
2021-08-29 18:36 ` [PATCH bpf-next v2 13/13] bpfilter: Handle setsockopts Dmitrii Banshchikov
2021-08-29 19:13 ` [PATCH bpf-next v2 00/13] bpfilter Raymond Burkholder
2021-08-30 12:54 ` Dmitrii Banshchikov [this message]
2021-08-31 1:56 ` Jamal Hadi Salim
2021-08-31 12:48 ` Dmitrii Banshchikov
2021-08-31 13:38 ` Jamal Hadi Salim
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=20210830125459.qk62gb5ak6xij4ug@amnesia \
--to=me@ubique.spb.ru \
--cc=bpf@vger.kernel.org \
--cc=ray@oneunified.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 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.