All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Krystad <peter.krystad at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH] mptcp: Remove flags field from struct mptcp_options_received
Date: Fri, 06 Dec 2019 08:55:00 -0800	[thread overview]
Message-ID: <78a39ed29a00923b938014117af9b28958380147.camel@linux.intel.com> (raw)
In-Reply-To: 2c5c11e0a9e8d465d9a64c38d61dd411ef2b2814.camel@redhat.com

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]


Davide, Matt -

Thanks Davide.

This patch and the other like it are all I plan to do for part 1 for
"optimizing struct mptcp_received_options". The other MPTCP options that
really grow the size are introduced after kselftest commit.

Now that we will be v1 past kselftest I will need to modify the ADD_ADDR
handling for v1 change, and this will then effect how the struct
mptcp_received_options is optimized.

Peter.


  
On Fri, 2019-12-06 at 09:31 +0100, Davide Caratti wrote:
> On Thu, 2019-12-05 at 15:43 -0800, Peter Krystad wrote:
> > This field is only used temporarily while parsing options,
> > use a local variable instead.
> > 
> > Also move key fields to final position and fix indents.
> > 
> > Formatted to apply directly to Handle MPTCP TCP options.
> > 
> > squashto: Handle MPTCP TCP options
> > 
> > Signed-off-by: Peter Krystad <peter.krystad(a)linux.intel.com>
> > ---
> >  include/linux/tcp.h |  7 +++----
> >  net/mptcp/options.c | 17 ++++++++---------
> >  2 files changed, 11 insertions(+), 13 deletions(-)
> 
> LGTM,
> 
> Acked-by: Davide Caratti <dcaratti(a)redhat.com>
> 
> 

             reply	other threads:[~2019-12-06 16:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-06 16:55 Peter Krystad [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-12-06 16:59 [MPTCP] Re: [PATCH] mptcp: Remove flags field from struct mptcp_options_received Matthieu Baerts
2019-12-06  8:31 Davide Caratti

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=78a39ed29a00923b938014117af9b28958380147.camel@linux.intel.com \
    --to=unknown@example.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.