All of lore.kernel.org
 help / color / mirror / Atom feed
From: 'Christoph Paasch' <cpaasch at apple.com>
To: mptcp at lists.01.org
Subject: Re: [MPTCP] [RFC] MPTCP Path Management Generic Netlink API
Date: Tue, 13 Mar 2018 11:26:06 -0700	[thread overview]
Message-ID: <20180313182606.GI74937@MacBook-Pro-4.local> (raw)
In-Reply-To: 01fe01d3ba45$c830fdc0$5892f940$@froemmgen.de

[-- Attachment #1: Type: text/plain, Size: 869 bytes --]

On 12/03/18 - 22:04:59, Alexander Frömmgen wrote:
> Hi
> 
> > How do you plan to handle schedulers? Given the good experimental results
> of the min-RTT-first scheduler, will that be the only option? Or will it
> remain as a kernel module due to the time-sensitive nature of scheduling?
> 
> We experimented with a programmable scheduler in the Kernel, which enables
> timely scheduling decisions and a lot of flexibility. Details are available
> at https://progmp.net and you might want to directly test a scheduler at
> http://progmp.net/progmp.html 
> 
> Our current setup contains a lot of additional logic in the Kernel (e.g.,
> lexer, parser). While this has some benefits, I think that the eBPF-based
> part of our work should be sufficient  for most application scenarios.

I would love to see a patch-submission :-)


Cheers,
Christoph


             reply	other threads:[~2018-03-13 18:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-13 18:26 'Christoph Paasch' [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-03-13 18:24 [MPTCP] [RFC] MPTCP Path Management Generic Netlink API Christoph Paasch
2018-03-12 21:10 Stephen Brennan
2018-03-12 20:55 Stephen Brennan
2018-03-12 17:27 Othman, Ossama
2018-03-12  3:27 Christoph Paasch
2018-03-12  3:25 Christoph Paasch
2018-03-08 23:46 Stephen Brennan
2018-03-08 20:48 Othman, Ossama

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=20180313182606.GI74937@MacBook-Pro-4.local \
    --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.