Netdev Archive on lore.kernel.org help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com> To: "Laura García Liébana" <nevola@gmail.com>, "John Fastabend" <john.fastabend@gmail.com> Cc: Lukas Wunner <lukas@wunner.de>, Pablo Neira Ayuso <pablo@netfilter.org>, Jozsef Kadlecsik <kadlec@netfilter.org>, Florian Westphal <fw@strlen.de>, Netfilter Development Mailing list <netfilter-devel@vger.kernel.org>, coreteam@netfilter.org, netdev@vger.kernel.org, Daniel Borkmann <daniel@iogearbox.net>, Alexei Starovoitov <ast@kernel.org>, Eric Dumazet <edumazet@google.com>, Thomas Graf <tgraf@suug.ch>, David Miller <davem@davemloft.net> Subject: Re: [PATCH nf-next v3 3/3] netfilter: Introduce egress hook Date: Fri, 04 Sep 2020 08:46:27 -0700 [thread overview] Message-ID: <5f5261535a32a_1932208c8@john-XPS-13-9370.notmuch> (raw) In-Reply-To: <CAF90-WgMiJkFsZaGBJQVVrmQz9==cq22NErpcWuE7z-Q+A8PzQ@mail.gmail.com> Laura García Liébana wrote: > Hi, > > On Thu, Sep 3, 2020 at 7:00 AM John Fastabend <john.fastabend@gmail.com> wrote: > > > [...] > > > > I don't think it actualy improves performance at least I didn't observe > > that. From the code its not clear why this would be the case either. As > > a nit I would prefer that line removed from the commit message. > > > > It hasn't been proven to be untrue either. huh? Its stated in the commit message with no reason for why it might be the case and I can't reproduce it. Also the numbers posted show such a slight increase (~1%) its likely just random system noise. Sorry maybe that was a joke? Just poured some coffee so might be missing it. > > > [...] > > > > Do you have plans to address the performance degradation? Otherwise > > if I was building some new components its unclear why we would > > choose the slower option over the tc hook. The two suggested > > use cases security policy and DSR sound like new features, any > > reason to not just use existing infrastructure? > > > > Unfortunately, tc is not an option as it is required to interact with > nft objects (sets, maps, chains, etc), more complex than just a drop. > Also, when building new features we try to maintain the application > stack as simple as possible, not trying to do ugly integrations. We have code that interacts with iptables as well. How I read the above is in your case you have a bunch of existing software and you want something slightly faster. Even if its not as fast the 10% overhead is OK in your case and/or you believe the overhead of all the other components is much higher so it will be lost in the noise. > I understand that you measure performance with a drop, but using this > hook we reduce the datapath consistently for these use cases and > hence, improving traffic performance. I measured drops because it was the benchmark provided in the patch series. Also it likely looks a lot like any DDOS that might be put there. You mentioned security policies which should probably include DDOS so I would expect drop performance to be at least a useful metric even if its not the only or most important in your case. Lets post a selftest that represents the use case so folks like myself can understand and benchmark correctly. This gives the extra benefit of ensuring we don't regress going forward and can add it to CI. > > Thank you for your time!
next prev parent reply other threads:[~2020-09-04 15:50 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-27 8:55 [PATCH nf-next v3 0/3] Netfilter egress hook Lukas Wunner 2020-08-27 8:55 ` [PATCH nf-next v3 1/3] netfilter: Rename ingress hook include file Lukas Wunner 2020-08-27 8:55 ` [PATCH nf-next v3 2/3] netfilter: Generalize ingress hook Lukas Wunner 2020-08-27 8:55 ` [PATCH nf-next v3 3/3] netfilter: Introduce egress hook Lukas Wunner 2020-08-28 18:52 ` John Fastabend 2020-09-03 5:00 ` John Fastabend 2020-09-04 8:54 ` Laura García Liébana 2020-09-04 15:46 ` John Fastabend [this message] 2020-09-05 11:13 ` Laura García Liébana 2020-09-04 16:21 ` Lukas Wunner 2020-09-04 21:14 ` Daniel Borkmann 2020-09-05 5:24 ` Lukas Wunner 2020-09-08 12:55 ` Daniel Borkmann 2020-09-11 7:42 ` Laura García Liébana 2020-09-11 16:27 ` Daniel Borkmann 2020-09-14 11:29 ` Laura García Liébana 2020-09-14 22:02 ` Daniel Borkmann 2020-09-17 10:28 ` Laura García Liébana 2020-09-18 20:31 ` Daniel Borkmann 2020-09-19 15:52 ` Pablo Neira Ayuso 2020-09-21 7:07 ` Laura García Liébana 2020-10-11 8:26 ` Lukas Wunner 2020-11-21 18:59 ` Pablo Neira Ayuso 2020-11-22 3:24 ` Alexei Starovoitov 2020-11-22 11:01 ` Pablo Neira Ayuso 2020-11-24 3:34 ` Alexei Starovoitov 2020-11-24 7:31 ` Lukas Wunner 2020-11-24 22:55 ` Alexei Starovoitov 2020-10-11 7:59 ` Lukas Wunner 2020-09-05 11:18 ` Laura García Liébana 2020-09-07 22:11 ` Daniel Borkmann 2020-09-08 6:19 ` Laura García Liébana 2020-09-08 11:46 ` Arturo Borrero Gonzalez 2020-09-08 13:27 ` Daniel Borkmann 2020-09-08 18:58 ` John Fastabend 2020-09-19 15:54 ` Pablo Neira Ayuso 2020-09-28 12:20 ` Lukas Wunner 2020-08-27 10:36 ` [PATCH nf-next v3 0/3] Netfilter " Laura García Liébana 2020-08-28 7:14 ` Daniel Borkmann 2020-08-28 9:14 ` Eric Dumazet
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=5f5261535a32a_1932208c8@john-XPS-13-9370.notmuch \ --to=john.fastabend@gmail.com \ --cc=ast@kernel.org \ --cc=coreteam@netfilter.org \ --cc=daniel@iogearbox.net \ --cc=davem@davemloft.net \ --cc=edumazet@google.com \ --cc=fw@strlen.de \ --cc=kadlec@netfilter.org \ --cc=lukas@wunner.de \ --cc=netdev@vger.kernel.org \ --cc=netfilter-devel@vger.kernel.org \ --cc=nevola@gmail.com \ --cc=pablo@netfilter.org \ --cc=tgraf@suug.ch \ /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: linkBe 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).