All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: mptcp@lists.linux.dev
Subject: [PATCH v2 mptcp-next 0/4] mptcp: minor receive path optimization
Date: Thu, 19 Aug 2021 17:16:13 +0200	[thread overview]
Message-ID: <cover.1629386016.git.pabeni@redhat.com> (raw)

This series aims at closing:

https://github.com/multipath-tcp/mptcp_net-next/issues/42

The relevant code is introduced by patch 4/4.

Do do the above in hopefully clean way, the series needs some
changes to the input options struct. That means a lot of
noise in the option-related code in the previous patches,
anyhow no functional change is intended here.

v1 -> v2:
 - fixed = -> |= (Mat)
 - fixed bug in ADD_ADDR processing (still in 3/4)

Paolo Abeni (4):
  mptcp: do not set unconditionally csum_reqd on incoming opt
  mptcp: better binary layout for mptcp_options_received
  mptcp: consolidate in_opt sub-options fields in a bitmask
  mptcp: optimize the input options processing.

 net/mptcp/options.c  | 140 +++++++++++++++++++------------------------
 net/mptcp/protocol.c |   4 +-
 net/mptcp/protocol.h |  36 ++++++-----
 net/mptcp/subflow.c  |  40 +++++++------
 4 files changed, 104 insertions(+), 116 deletions(-)

-- 
2.26.3


             reply	other threads:[~2021-08-19 15:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 15:16 Paolo Abeni [this message]
2021-08-19 15:16 ` [PATCH v2 mptcp-next 1/4] mptcp: do not set unconditionally csum_reqd on incoming opt Paolo Abeni
2021-08-19 15:16 ` [PATCH v2 mptcp-next 2/4] mptcp: better binary layout for mptcp_options_received Paolo Abeni
2021-08-19 15:16 ` [PATCH v2 mptcp-next 3/4] mptcp: consolidate in_opt sub-options fields in a bitmask Paolo Abeni
2021-08-19 15:16 ` [PATCH v2 mptcp-next 4/4] mptcp: optimize the input options processing Paolo Abeni
2021-08-20  0:24   ` Mat Martineau
2021-08-20  7:58     ` Paolo Abeni
2021-08-20  8:02       ` Matthieu Baerts
2021-08-20  8:05 ` [PATCH v2 mptcp-next 0/4] mptcp: minor receive path optimization 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=cover.1629386016.git.pabeni@redhat.com \
    --to=pabeni@redhat.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 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.