From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: mptcp@lists.linux.dev
Subject: Re: [PATCH mptcp-next 0/2] mptcp: a couple of cleanups
Date: Wed, 8 Dec 2021 17:03:40 -0800 (PST) [thread overview]
Message-ID: <19906159-80c5-e657-9e5e-d94891e81478@linux.intel.com> (raw)
In-Reply-To: <cover.1638811854.git.pabeni@redhat.com>
On Mon, 6 Dec 2021, Paolo Abeni wrote:
> The first patch was already shared as RFC, this iteration
> addresses a couple of bugs there.
>
> The second patch removes a bunch of conditionals and atomic
> operations in the fast path, but the performance impact is
> actually below noise level. Still I think it's worthy, as the
> unneeded atomic operations are confusing.
>
> Paolo Abeni (2):
> mptcp: cleanup MPJ subflow list handling
> mptcp: avoid atomic bit manipulation when possible
>
> net/mptcp/pm_netlink.c | 3 -
> net/mptcp/protocol.c | 149 ++++++++++++++++++-----------------------
> net/mptcp/protocol.h | 31 ++++-----
> net/mptcp/sockopt.c | 24 ++-----
> net/mptcp/subflow.c | 9 ++-
> 5 files changed, 89 insertions(+), 127 deletions(-)
Looks good to me:
Reviewed-by: Mat Martineau <mathew.j.martineau@linux.intel.com>
Matthieu, note that this patch set depends on the "mptcp: improve subflow
creation on errors" patches.
--
Mat Martineau
Intel
next prev parent reply other threads:[~2021-12-09 1:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 17:34 [PATCH mptcp-next 0/2] mptcp: a couple of cleanups Paolo Abeni
2021-12-06 17:34 ` [PATCH mptcp-next 1/2] mptcp: cleanup MPJ subflow list handling Paolo Abeni
2021-12-06 17:34 ` [PATCH mptcp-next 2/2] mptcp: avoid atomic bit manipulation when possible Paolo Abeni
2021-12-09 1:03 ` Mat Martineau [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-06 18:30 [PATCH mptcp-next 0/2] mptcp: a couple of cleanups Paolo Abeni
2023-03-07 16:28 ` Matthieu Baerts
2023-03-07 17:41 ` Matthieu Baerts
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=19906159-80c5-e657-9e5e-d94891e81478@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=mptcp@lists.linux.dev \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.