All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Maximilian Krüger" <maximilian.krueger@fau.de>
To: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	linux-kernel@vger.kernel.org
Subject: [RFC] sched: low latency feedback to userspace
Date: Mon, 9 May 2016 12:18:54 +0200	[thread overview]
Message-ID: <5730640E.9050503@fau.de> (raw)

I am planning to extend the CFS as part of my master thesis. I want 
user-threads to allow to decide whether to enter a critical section or 
call sched_yield()
For tight synchronized workloads it might be useful, to only start 
certain short tasks, when they still can be completed in the current 
time slice without being interrupted by the scheduler.
Since low latency is key, my current plan is to use a shared-mapped page 
for signaling and only use a syscall for the setup. I'd be curious, if 
you might find this useful in general and if there is a chance for 
getting this accepted upstream, given my benchmarks can prove gives the 
intended benefits.

While these are very general questions, I have one detail question 
concerning how good the chances for getting this upstream are. Would you 
prefer, if I implemented the setup with an additional syscall, or as an 
extensions of existing syscalls (probably sched_setattr, sched_getattr).
greetings,
Maximilian Krüger

             reply	other threads:[~2016-05-09 10:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 10:18 Maximilian Krüger [this message]
2016-05-09 11:18 ` [RFC] sched: low latency feedback to userspace Peter Zijlstra
2016-05-09 13:03   ` Maximilian Krüger
2016-05-09 13:42     ` Peter Zijlstra

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=5730640E.9050503@fau.de \
    --to=maximilian.krueger@fau.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    /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.