From: Phil Sutter <phil@nwl.cc>
To: "Serguei Bezverkhi (sbezverk)" <sbezverk@cisco.com>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: Numen with reference to vmap
Date: Wed, 4 Dec 2019 16:17:38 +0100 [thread overview]
Message-ID: <20191204151738.GR14469@orbyte.nwl.cc> (raw)
In-Reply-To: <AFC93A41-C4DD-4336-9A62-6B9C6817D198@cisco.com>
Hi,
On Wed, Dec 04, 2019 at 01:47:47PM +0000, Serguei Bezverkhi (sbezverk) wrote:
> Thank you for your reply. It is very unfortunate indeed. Here is the scenario where I thought to use a non-anonymous vmap.
>
> Each k8s service can have 0, 1 or more associated endpoints, backends (pods providing this service). 0 endpoint already taken care of in filter prerouting hook. When there are 1 or more, proxy needs to load balance incoming connections between endpoints.I thought to create vmap per service with 1 rule per service . When an endpoint gets updated (add/deleted) which could happen anytime then the only vmap get corresponding update and my hope was that automagically load balancing will be adjusted to use updated endpoints list.
>
> With what you explained, I am not sure if dynamic load balancing is possible at all. If numgen work only with static anonymous vmap and fixed modulus , the only way to address this dynamic nature of endpoints is to recreate service rule everytime when number of endpoints changes (recalculate modulus and entries in vmap). I suspect it is way less efficient.
Well, if you have a modulus of, say, 5 and your vmap contains only
entries 0 to 3 your setup is broken anyway. So I guess you will need to
adjust modulus along with entries in vmap at all times.
What is the iptables-equivalent you want to replace? Maybe that serves
as inspiration for how to solve it in nftables.
> What will happen to dataplane and packets in transit when the rule will be deleted and then recreated? I suspect it might result in dropped packets, could you please comment on the possible impact?
Well, you could replace the rule in a single transaction, that would
eliminate the timespan the rule doesn't exist. AFAICT, this is RCU-based
so packets will either hit the old or the new rule then.
Cheers, Phil
next prev parent reply other threads:[~2019-12-04 15:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 0:54 Numen with reference to vmap Serguei Bezverkhi (sbezverk)
2019-12-04 10:18 ` Phil Sutter
2019-12-04 13:47 ` Serguei Bezverkhi (sbezverk)
2019-12-04 15:17 ` Phil Sutter [this message]
2019-12-04 15:42 ` Serguei Bezverkhi (sbezverk)
2019-12-04 15:56 ` Phil Sutter
2019-12-04 16:13 ` Serguei Bezverkhi (sbezverk)
2019-12-04 17:00 ` Phil Sutter
2019-12-04 17:31 ` Arturo Borrero Gonzalez
2019-12-04 17:49 ` Serguei Bezverkhi (sbezverk)
2019-12-04 21:05 ` Serguei Bezverkhi (sbezverk)
2019-12-04 22:32 ` Phil Sutter
2019-12-17 0:51 ` Serguei Bezverkhi (sbezverk)
2019-12-17 12:29 ` Phil Sutter
2019-12-17 14:05 ` Serguei Bezverkhi (sbezverk)
2019-12-17 16:41 ` Phil Sutter
2019-12-18 17:01 ` Serguei Bezverkhi (sbezverk)
2019-12-18 17:24 ` Phil Sutter
2019-12-18 19:43 ` Serguei Bezverkhi (sbezverk)
2019-12-18 19:58 ` Laura Garcia
2019-12-18 20:54 ` Serguei Bezverkhi (sbezverk)
2019-12-19 10:48 ` Phil Sutter
2019-12-19 14:59 ` Serguei Bezverkhi (sbezverk)
2019-12-19 15:45 ` Phil Sutter
2019-12-19 16:00 ` Serguei Bezverkhi (sbezverk)
2019-12-19 18:19 ` Serguei Bezverkhi (sbezverk)
2020-01-04 12:30 ` Serguei Bezverkhi (sbezverk)
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=20191204151738.GR14469@orbyte.nwl.cc \
--to=phil@nwl.cc \
--cc=netfilter-devel@vger.kernel.org \
--cc=sbezverk@cisco.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).