Support v6 real servers in v4 pools and vice versa
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest20 patches 4 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/20 | ipvs: Add destination address family to netlink interfaceinclude/ include/ net/ | +44 | 0 replies | |
| 2/20 | ipvs: Supply destination addr family to ip_vs_{lookup_dest,find_dest}include/ net/ net/ +1 more | +30 | 0 replies | |
| 3/20 | ipvs: Pass destination address family to ip_vs_trash_get_destnet/ | +6 | 0 replies | |
| 4/20 | ipvs: Supply destination address family to ip_vs_conn_newinclude/ net/ net/ +2 more | +16 | 0 replies | |
| 5/20 | ipvs: prevent mixing heterogeneous pools and synchronizationinclude/ net/ | +19 | 0 replies | |
| 6/20 | ipvs: Pull out crosses_local_route_boundary logicnet/ | +77 | 0 replies | |
| 7/20 | ipvs: Pull out update_pmtu codenet/ | +11 | 0 replies | |
| 8/20 | ipvs: Add generic ensure_mtu_is_adequate to handle mixed poolsnet/ | +51 | 0 replies | |
| 9/20 | ipvs: support ipv4 in ipv6 and ipv6 in ipv4 tunnel forwardingnet/ net/ | +117 | 0 replies | |
| 10/20 | ipvs: address family of LBLC entry depends on svc familynet/ | +6 | 0 replies | |
| 11/20 | ipvs: address family of LBLCR entry depends on svc familynet/ | +6 | 0 replies | |
| 12/20 | ipvs: use correct address family in DH logsnet/ | +1 | 0 replies | |
| 13/20 | ipvs: use correct address family in LC logsnet/ | +1 | 0 replies | |
| 14/20 | ipvs: use correct address family in NQ logsnet/ | +2 | 0 replies | |
| 15/20 | ipvs: use correct address family in RR logsnet/ | +1 | 0 replies | |
| 16/20 | ipvs: use correct address family in SED logsnet/ | +2 | 0 replies | |
| 17/20 | ipvs: use correct address family in SH logsnet/ | +4 | 0 replies | |
| 18/20 | ipvs: use correct address family in WLC logsnet/ | +2 | 0 replies | |
| 19/20 | ipvs: use the new dest addr family fieldnet/ net/ net/ +1 more | +43 | 0 replies | |
| 20/20 | ipvs: Allow heterogeneous pools now that we support themnet/ | +20 | 0 replies |
Reviews trailers per patch
None of the 20 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Julian Anastasov |
|---|---|
| Series | A-b |
| 1/20 | |
| 2/20 | |
| 3/20 | |
| 4/20 | |
| 5/20 | |
| 6/20 | |
| 7/20 | |
| 8/20 | |
| 9/20 | |
| 10/20 | |
| 11/20 | |
| 12/20 | |
| 13/20 | |
| 14/20 | |
| 15/20 | |
| 16/20 | |
| 17/20 | |
| 18/20 | |
| 19/20 | |
| 20/20 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH net-next 00/20] Support v6 real servers in v4 pools and vice versa
The following patch set has been iterated upon in the lvs-devel mailing list. I am submitting it here per Julian's advice for inclusion in the net-next tree.
At Facebook we use ipip forwarding to deliver packets from our layer 4 ipvs load balancers to our layer 7 proxies. Today these layer 7 proxies are all dual stacked, so we can simply send v4 over v4 and v6 over v6. In the future, we're going to have v6-only layer 7 load balancers (no internal v4 address). To deal with this, we'll forward v4 packets in v6 tunnels. This patchset introduces the necessary functionality into ipvs.
The noteworthy limitation of this is that it is not compatible with state synchronization, so great care is taken to keep these things mutually exclusive.
This patchset includes changes that add an additional netlink attribute to destinations and changes that plumb the destination address family through parts of the code where it was assumed that it was the same as the service. Finally, there's a change that updates the transmit functions for tunneling to share common code and support v4 in v6 and vice versa.
Alex Gartrell (10):
ipvs: Add destination address family to netlink interface
ipvs: Supply destination addr family to ip_vs_{lookup_dest,find_dest}
ipvs: Pass destination address family to ip_vs_trash_get_dest
ipvs: Supply destination address family to ip_vs_conn_new
ipvs: prevent mixing heterogeneous pools and synchronization
ipvs: Pull out crosses_local_route_boundary logic
ipvs: Pull out update_pmtu code
ipvs: Add generic ensure_mtu_is_adequate to handle mixed pools
ipvs: support ipv4 in ipv6 and ipv6 in ipv4 tunnel forwarding
ipvs: Allow heterogeneous pools now that we support them
Julian Anastasov (10):
ipvs: address family of LBLC entry depends on svc family
ipvs: address family of LBLCR entry depends on svc family
ipvs: use correct address family in DH logs
ipvs: use correct address family in LC logs
ipvs: use correct address family in NQ logs
ipvs: use correct address family in RR logs
ipvs: use correct address family in SED logs
ipvs: use correct address family in SH logs
ipvs: use correct address family in WLC logs
ipvs: use the new dest addr family field
include/net/ip_vs.h | 15 +- include/uapi/linux/ip_vs.h | 3 + net/netfilter/ipvs/ip_vs_conn.c | 74 +++++-- net/netfilter/ipvs/ip_vs_core.c | 15 +- net/netfilter/ipvs/ip_vs_ctl.c | 112 +++++++--- net/netfilter/ipvs/ip_vs_dh.c | 2 +- net/netfilter/ipvs/ip_vs_ftp.c | 6 +- net/netfilter/ipvs/ip_vs_lblc.c | 12 +- net/netfilter/ipvs/ip_vs_lblcr.c | 12 +- net/netfilter/ipvs/ip_vs_lc.c | 2 +- net/netfilter/ipvs/ip_vs_nq.c | 3 +- net/netfilter/ipvs/ip_vs_proto_sctp.c | 2 +- net/netfilter/ipvs/ip_vs_proto_tcp.c | 2 +- net/netfilter/ipvs/ip_vs_rr.c | 2 +- net/netfilter/ipvs/ip_vs_sed.c | 3 +- net/netfilter/ipvs/ip_vs_sh.c | 8 +- net/netfilter/ipvs/ip_vs_sync.c | 13 +- net/netfilter/ipvs/ip_vs_wlc.c | 3 +- net/netfilter/ipvs/ip_vs_xmit.c | 388 +++++++++++++++++++++------------- 19 files changed, 453 insertions(+), 224 deletions(-)
Signature · 1 line
1.8.1