All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mat Martineau <mathew.j.martineau@linux.intel.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Geliang Tang <geliangtang@gmail.com>,
	mptcp@lists.linux.dev,  Christoph Paasch <cpaasch@apple.com>,
	 Geliang Tang <geliangtang@xiaomi.com>
Subject: Re: [PATCH RFC mptcp-next 3/4] mptcp: round-robin packet scheduler support
Date: Wed, 8 Sep 2021 17:18:10 -0700 (PDT)	[thread overview]
Message-ID: <5397f14c-a48-c4b6-ddb8-80ab97e5dc44@linux.intel.com> (raw)
In-Reply-To: <bf211816c921732874fcc66cade7a86c2eaecfa8.camel@redhat.com>


On Tue, 7 Sep 2021, Paolo Abeni wrote:

> There is an import side question, already asked by Christoph, why the
> round robin? perhpas we should consider instead some different
> scheduler, known to perform well. @Christoph: which is the 'best'
> mptcp.org scheduler out there? blest?
>

This is the main question I have!

We've also discussed the idea of eBPF-based schedulers, so I've been 
thinking we would have one built-in scheduler and then allow alternatives 
(like round robin) via eBPF.

If there's a good use case for round robin maybe there's a solution here 
similar to what we did with the fullmesh path manager: could there be a 
configuration knob for the existing scheduler that makes it try to *not* 
use the last-used subflow, instead of favoring the last-used subflow?

--
Mat Martineau
Intel

  reply	other threads:[~2021-09-09  0:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 10:41 [PATCH RFC mptcp-next 0/4] round-robin packet scheduler support Geliang Tang
2021-09-07 10:41 ` [PATCH RFC mptcp-next 1/4] mptcp: add a new sysctl scheduler Geliang Tang
2021-09-07 10:59   ` Paolo Abeni
2021-09-07 10:41 ` [PATCH RFC mptcp-next 2/4] mptcp: add struct mptcp_sched_ops Geliang Tang
2021-09-07 11:04   ` Paolo Abeni
2021-09-07 22:24   ` kernel test robot
2021-09-07 10:41 ` [PATCH RFC mptcp-next 3/4] mptcp: round-robin packet scheduler support Geliang Tang
2021-09-07 11:16   ` Paolo Abeni
2021-09-09  0:18     ` Mat Martineau [this message]
2021-09-07 10:41 ` [PATCH RFC mptcp-next 4/4] selftests: mptcp: add round-robin testcase Geliang Tang

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=5397f14c-a48-c4b6-ddb8-80ab97e5dc44@linux.intel.com \
    --to=mathew.j.martineau@linux.intel.com \
    --cc=cpaasch@apple.com \
    --cc=geliangtang@gmail.com \
    --cc=geliangtang@xiaomi.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 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.