From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Cc: Geliang Tang <geliangtang@gmail.com>
Subject: [PATCH v3 mptcp-next 0/3] mptcp: minor out optimization
Date: Mon, 26 Jul 2021 12:55:26 +0200 [thread overview]
Message-ID: <cover.1627296764.git.pabeni@redhat.com> (raw)
This series implements a few ideas discussed in the past mtg,
specifcally:
https://github.com/multipath-tcp/mptcp_net-next/issues/15
https://github.com/multipath-tcp/mptcp_net-next/issues/42
The final goal is shrink the mptcp_out_options struct, which is
always zeroed by the plain TCP protocol in the output path.
This iteration covers the feedback provided by Geliang (many thanks!)
on v1:
- some code moved to new squash-to patch 1/3
- some cleanup in 2/3
please see the individual patch changelog for the details
Paolo Abeni (3):
Squash-to: "mptcp: move drop_other_suboptions check under pm lock"
mptcp: optimize out option generation
mptcp: shrink mptcp_out_options struct
include/net/mptcp.h | 26 +++--
net/mptcp/options.c | 227 +++++++++++++++++++++++--------------------
net/mptcp/pm.c | 9 +-
net/mptcp/protocol.h | 1 +
4 files changed, 142 insertions(+), 121 deletions(-)
--
2.26.3
next reply other threads:[~2021-07-26 10:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 10:55 Paolo Abeni [this message]
2021-07-26 10:55 ` [PATCH v3 mptcp-next 1/3] Squash-to: "mptcp: move drop_other_suboptions check under pm lock" Paolo Abeni
2021-07-27 4:27 ` Geliang Tang
2021-07-26 10:55 ` [PATCH v3 mptcp-next 2/3] mptcp: optimize out option generation Paolo Abeni
2021-07-27 4:33 ` Geliang Tang
2021-07-26 10:55 ` [PATCH v3 mptcp-next 3/3] mptcp: shrink mptcp_out_options struct Paolo Abeni
2021-07-28 0:40 ` [PATCH v3 mptcp-next 0/3] mptcp: minor out optimization Mat Martineau
2021-07-28 8:09 ` Matthieu Baerts
2021-07-28 10:46 ` Paolo Abeni
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.1627296764.git.pabeni@redhat.com \
--to=pabeni@redhat.com \
--cc=geliangtang@gmail.com \
--cc=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