From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Matthieu Baerts <matthieu.baerts@tessares.net>
Cc: MPTCP Upstream <mptcp@lists.linux.dev>
Subject: Re: Checksum support: default behaviour
Date: Fri, 11 Jun 2021 21:05:55 -0700 (PDT) [thread overview]
Message-ID: <c8d3563b-4495-b151-645f-305e4192c2c@linux.intel.com> (raw)
In-Reply-To: <4582ad38-e8d5-e639-1ebe-688727329f51@tessares.net>
On Fri, 11 Jun 2021, Matthieu Baerts wrote:
> Hello,
>
> With the current checksum support series from Geliang and Paolo
> available in our tree, the default behaviour is not to use this checksum
> feature.
>
> Should we eventually do the opposite and have it enabled by default?
>
> I do understand this has a cost in terms of performances but this could
> help detecting nasty middleboxes, i.e. the ones that modify the TCP
> packets without modifying MPTCP options if needed.
>
> On the other hand, I don't have numbers showing if these middleboxes are
> rare or not.
>
> But also, the main issue I see if we enable the checksum support by
> default is that we are no longer able to talk to servers not supporting
> it (<5.13), no?
>
> WDYT?
>
I lean toward leaving checksums off by default, based on what I've heard
from community members. It sounds like large deployments haven't seen
checksums catch many problems? Some actual data about the frequency of
checksum failures would really help.
Your last point about connecting to older upstream kernels is also an
important one. I'd rather keep it possible to connect to those kernels
using default configuration options unless it's too risky to do so.
--
Mat Martineau
Intel
next prev parent reply other threads:[~2021-06-12 4:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-11 14:59 Checksum support: default behaviour Matthieu Baerts
2021-06-12 4:05 ` Mat Martineau [this message]
2021-06-14 10:39 ` Paolo Abeni
2021-06-14 15:58 ` Matthieu Baerts
2021-06-14 15:54 ` Matthieu Baerts
2021-06-18 14:23 ` 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=c8d3563b-4495-b151-645f-305e4192c2c@linux.intel.com \
--to=mathew.j.martineau@linux.intel.com \
--cc=matthieu.baerts@tessares.net \
--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;
as well as URLs for NNTP newsgroup(s).