From: Geliang Tang <geliangtang at gmail.com>
To: mptcp at lists.01.org
Subject: [MPTCP] [MPTCP][PATCH v3 mptcp-next 0/2] mptcp: add the address ID assignment bitmap and testcase
Date: Tue, 08 Dec 2020 21:42:28 +0800 [thread overview]
Message-ID: <cover.1607434427.git.geliangtang@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
v3:
- call find_next_zero_bit() again for the invalid id.
- use "for (i = id; ..." in mptcp_nl_cmd_dump_addrs.
- add a wrap around testcase.
v2:
- use BITS_PER_LONG macro.
- add back the callback argument in cmd_dump_addrs.
- add a testcase.
Closes: https://github.com/multipath-tcp/mptcp_net-next/issues/117
Geliang Tang (2):
mptcp: add the address ID assignment bitmap
selftests: mptcp: add testcases for setting the address ID
net/mptcp/pm_netlink.c | 65 ++++++++++++++-----
.../testing/selftests/net/mptcp/pm_netlink.sh | 41 +++++++++++-
2 files changed, 86 insertions(+), 20 deletions(-)
--
2.26.2
reply other threads:[~2020-12-08 13:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1607434427.git.geliangtang@gmail.com \
--to=mptcp@lists.linux.dev \
/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