From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: luca abeni <luca.abeni@santannapisa.it>
Cc: Juri Lelli <juri.lelli@arm.com>,
peterz@infradead.org, linux-kernel@vger.kernel.org,
Tommaso Cucinotta <tommaso.cucinotta@santannapisa.it>
Subject: Re: On the unlikely off-chance that this is new news
Date: Wed, 12 Apr 2017 15:45:24 -0700 [thread overview]
Message-ID: <20170412224524.GN3956@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170412222808.153698f5@nowhere>
On Wed, Apr 12, 2017 at 10:28:08PM +0200, luca abeni wrote:
> On Wed, 12 Apr 2017 16:28:02 +0100
> Juri Lelli <juri.lelli@arm.com> wrote:
>
> > Hi Paul,
> >
> > On 12/04/17 08:15, Paul E. McKenney wrote:
> > > Hello!
> > >
> > > On the unlikely off-chance that this is new news...
> > >
> >
> > It is actually new news for me (it might be still unlikely for Peter,
> > Luca and Tommaso, that I Cc-ed).
>
> I did not know about this, thanks for sharing! The abstract looks
> interesting :)
> I still have to read the thesis, but at a first glance it looks like
> some kind of adaptive scheduling framework... Right?
They do have a specific algorithm, and I am not sure which of the
framework or the algorithm deserves the closest focus. My tendency
is to look at the algorithm. Any slob can create a framework!
(Getting everyone else to use it, now -that- is the trick.)
Thanx, Paul
> Luca
>
>
> >
> > > A Hannes Weisbach of TU Dresden published this masters thesis on
> > > quasi-real-time scheduling:
> > >
> > > http://os.inf.tu-dresden.de/papers_ps/weisbach-master.pdf
> > >
> > > If you have come across this, I would be interested in your
> > > thoughts.
> >
> > Thanks for the pointer. Definitely interesting Easter break reading.
> >
> > Best,
> >
> > - Juri
>
prev parent reply other threads:[~2017-04-12 22:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 15:15 Paul E. McKenney
2017-04-12 15:28 ` Juri Lelli
2017-04-12 16:17 ` Paul E. McKenney
2017-04-12 20:28 ` luca abeni
2017-04-12 22:45 ` Paul E. McKenney [this message]
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=20170412224524.GN3956@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@santannapisa.it \
--cc=peterz@infradead.org \
--cc=tommaso.cucinotta@santannapisa.it \
/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
all inboxes | Powered by JetHome®