From: Maxim Galaganov <max@internet.ru>
To: Paolo Abeni <pabeni@redhat.com>, mptcp@lists.linux.dev
Cc: Geliang Tang <geliang.tang@suse.com>,
Mat Martineau <mathew.j.martineau@linux.intel.com>
Subject: Re: apropos https://github.com/multipath-tcp/mptcp_net-next/issues/265
Date: Wed, 4 May 2022 17:30:36 +0300 [thread overview]
Message-ID: <3c85fe48-69fe-0655-2146-a4424e02f185@internet.ru> (raw)
In-Reply-To: <e69d4d2bead08317ad3af55ffe415b8f94877948.camel@redhat.com>
On 04.05.2022 12:52, Paolo Abeni wrote:
>
> Could you please additionally test the following patch? Kernel for both
> arches must be rebuilt.
>
> This should cause old x86 build with csum enabled to fallback to TCP
> while interoperating with new ones, which is ugly and bad, but - given
> that csum is disable by default - possibly still acceptable?!?
The results for me are as follows:
old x86_64 (5.17.5) + old mips (5.15.35) => reset
new x86_64 (5.18-rc5+patch) vs old mips (5.15.35) => works
new x86_64 (5.18-rc5+patch) vs new mips (5.15.35+patch) => works
old x86_64 (5.17.2) + new mips (5.15.35+patch) => reset
old x86_64 (5.17.2) + new x86_64 (5.18-rc5+patch) => reset
new x86_64 (5.18-rc5+patch) talking to itself => works
I edited the patch so that it applies to my kernels, and this might be
the reason I don't see fallback but see reset instead -- I don't have
"mptcp: TCP fallback for established connections" patches in my tree as
they are only in net-next yet. Or I may be doing something stupid.
Is there a way for an old box without infinite mapping support to
fallback an established connection in case of csum failure?
next prev parent reply other threads:[~2022-05-04 15:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 10:08 apropos https://github.com/multipath-tcp/mptcp_net-next/issues/265 Paolo Abeni
2022-05-03 18:37 ` apropos https://github.com/multipath-tcp/mptcp_net-next/issues/265 (checksums) Mat Martineau
2022-05-04 16:41 ` Matthieu Baerts
2022-05-03 20:41 ` apropos https://github.com/multipath-tcp/mptcp_net-next/issues/265 Maxim Galaganov
2022-05-03 23:47 ` Mat Martineau
2022-05-04 9:52 ` Paolo Abeni
2022-05-04 14:30 ` Maxim Galaganov [this message]
2022-05-06 1:11 ` Mat Martineau
2022-05-07 0:49 ` Mat Martineau
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=3c85fe48-69fe-0655-2146-a4424e02f185@internet.ru \
--to=max@internet.ru \
--cc=geliang.tang@suse.com \
--cc=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 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).