diff options
author | David S. Miller <davem@davemloft.net> | 2021-03-13 04:47:46 +0300 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2021-03-13 04:47:46 +0300 |
commit | 7c678829efa89e23a8556f5e4d9621c51995fb6e (patch) | |
tree | 41536ba695917e42bb3c74c12bae49f3f74db39d /net/dns_resolver | |
parent | e9e90a70cc2d5690b84c7ca2f604e09a85222bb1 (diff) | |
parent | d2c4333a801c73a8bc2e4bde75b573e2d1014436 (diff) | |
download | linux-7c678829efa89e23a8556f5e4d9621c51995fb6e.tar.xz |
Merge branch 'mptcp-Include-multiple-address-ids-in-RM_ADDR'
Mat Martineau says:
====================
mptcp: Include multiple address ids in RM_ADDR
Here's a patch series from the MPTCP tree that extends the capabilities
of the MPTCP RM_ADDR header.
MPTCP peers can exchange information about their IP addresses that are
available for additional MPTCP subflows. IP addresses are advertised
with an ADD_ADDR header type, and those advertisements are revoked with
the RM_ADDR header type. RFC 8684 allows the RM_ADDR header to include
more than one address ID, so multiple advertisements can be revoked in a
single header. Previous kernel versions have only used RM_ADDR with a
single address ID, so multiple removals required multiple packets.
Patches 1-4 plumb address id list structures around the MPTCP code,
where before only a single address ID was passed.
Patches 5-8 make use of the address lists at the path manager layer that
tracks available addresses for both peers.
Patches 9-11 update the selftests to cover the new use of RM_ADDR with
multiple address IDs.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/dns_resolver')
0 files changed, 0 insertions, 0 deletions