From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: RFCv2 for netdev: what's missing?
Date: Tue, 01 Oct 2019 17:34:24 +0200 [thread overview]
Message-ID: <20191001153424.GF14819@breakpoint.cc> (raw)
In-Reply-To: 4a7f4996-eac5-2601-2a8f-ff720b9bec4f@tessares.net
[-- Attachment #1: Type: text/plain, Size: 1492 bytes --]
Matthieu Baerts <matthieu.baerts(a)tessares.net> wrote:
> > For RFC I think it depends on how much work you want to
> > get yourself into right now, as it would need to be squashed, sending
> > it as extra patch is strange.
>
> In general. It is linked to my message I sent on the thread linked to
> the patch:
Ah, thanks for the pointer.
> > The main part of this patch is removing the parsing of the checksum
> > option. But in the commits where this is introduced, we also parse
> > other possible options we could have and we act differently if one
> > option is not supported. And in these commits, it makes sense to do
> > that.
> >
> > We could see that as "we are parsing stuff we don't need". But we are
> > already doing that for the "backup" bit for example. Or for the
> > "MP_JOIN" while we don't support it when subflow_request_sock
> > structure is introduced, etc.
> >
> > In other words, do we really need to remove this code linked to the
> > checksum? If we plan never to support it, it makes sense. But I guess
> > in the near future, we will want to support it, no?
> >
> > So should I continue applying this patch?
Oh, OK. I thought the consensus was to not support checksums.
If we're going to add it for the initial mptcp v1 submission, the code
should be kept.
OTOH, if we're going to add checksums later on -- after initial
upstreaming -- I think its better to remove it now and resurrect it later
once someone adds the feature.
next reply other threads:[~2019-10-01 15:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 15:34 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-04 11:25 [MPTCP] Re: RFCv2 for netdev: what's missing? Matthieu Baerts
2019-10-03 19:21 Florian Westphal
2019-10-03 8:12 Paolo Abeni
2019-10-03 7:46 Florian Westphal
2019-10-03 0:39 Mat Martineau
2019-10-02 23:55 Mat Martineau
2019-10-02 23:41 Mat Martineau
2019-10-02 21:11 Matthieu Baerts
2019-10-01 23:07 Mat Martineau
2019-10-01 20:26 Paolo Abeni
2019-10-01 19:40 Matthieu Baerts
2019-10-01 19:28 Matthieu Baerts
2019-10-01 17:21 Mat Martineau
2019-10-01 16:23 Mat Martineau
2019-10-01 16:14 Peter Krystad
2019-10-01 16:07 Paolo Abeni
2019-10-01 15:14 Matthieu Baerts
2019-10-01 15:07 Matthieu Baerts
2019-10-01 15:00 Florian Westphal
2019-10-01 14:58 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=20191001153424.GF14819@breakpoint.cc \
--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.