From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v2 mptcp-next] mptcp: add receive buffer auto-tuning
Date: Wed, 03 Jun 2020 16:39:41 +0200 [thread overview]
Message-ID: <20200603143941.GB28263@breakpoint.cc> (raw)
In-Reply-To: f67740d53f31df60e321dafeab195d020c53c3af.camel@redhat.com
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Davide Caratti <dcaratti(a)redhat.com> wrote:
> hello Florian,
>
> net-next will not be accepting patches for a while - but I would like to
> fix this on some tree, so that periodic tests can be run over there. So, I
> will rebase the fallback rework on top of the rx buffer auto-tuning patch.
Do you plan to submit your patches to net or net-next when it reopens?
If you are targetting net, it would be better to apply your patches to
the current mptcp-next tree as-is, so they don't need to be manged again
when submitted for net.
My plan wrt. autotuning is to send the selftest patch for net, and the
autotune one for net-next. So, to me it would make more sense for your
work to go into mptcp-next first. I would then apply the delta from
Christoph and send a new version for mptcp-next.
WDYT?
next reply other threads:[~2020-06-03 14:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 14:39 Florian Westphal [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-03 15:45 [MPTCP] Re: [PATCH v2 mptcp-next] mptcp: add receive buffer auto-tuning Christoph Paasch
2020-06-03 15:32 Florian Westphal
2020-06-03 15:08 Davide Caratti
2020-06-03 14:06 Davide Caratti
2020-05-29 22:41 Christoph Paasch
2020-05-29 20:10 Florian Westphal
2020-05-29 16:56 Christoph Paasch
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=20200603143941.GB28263@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.