From: Joerg Roedel <joro@8bytes.org>
To: Jerome Glisse <jglisse@redhat.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Core Kernel support for Compute-Offload Devices
Date: Sat, 1 Aug 2015 17:57:29 +0200 [thread overview]
Message-ID: <20150801155728.GC14980@8bytes.org> (raw)
In-Reply-To: <20150731161304.GA2039@redhat.com>
On Fri, Jul 31, 2015 at 12:13:04PM -0400, Jerome Glisse wrote:
> Hence scheduling here is different, on GPU it is more about
> a queue of several thousand thread and you just move things
> up and down on what need to be executed first. Then GPU have
> hw scheduling that constantly switch btw active thread this
> why memory latency is so well hidden on GPU.
Thats why I wrote "batch"-scheduler in the proposal. Its right that it
does not make sense to schedule out a GPU process, and some devices do
scheduling in hardware anyway.
But the Linux kernel still needs to decide which jobs are sent to the
offload device in which order, more like an io-scheduler.
There might be a compute job that only utilizes 60% of the device
resources, to the in-kernel scheduler could start another job there to
utilize the other 40%.
I think its worth a discussion if some common schedulers (like for
blk-io) make sense here too.
> I already implemented several version of it and posted for review
> couple of them. You do not want automatic migration because kernel
> as not enough informations here.
Some devices might provide that information, see the extended-access bit
of Intel VT-d.
Joerg
next prev parent reply other threads:[~2015-08-01 15:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 13:00 Joerg Roedel
2015-07-30 13:31 ` David Woodhouse
2015-07-30 13:54 ` Joerg Roedel
2015-07-31 16:34 ` Jerome Glisse
2015-08-03 18:51 ` David Woodhouse
2015-08-03 19:01 ` Jerome Glisse
2015-08-03 19:07 ` Andy Lutomirski
2015-08-03 19:56 ` Jerome Glisse
2015-08-03 21:10 ` Joerg Roedel
2015-08-03 21:12 ` David Woodhouse
2015-08-03 21:31 ` Joerg Roedel
2015-08-03 21:34 ` Jerome Glisse
2015-08-03 21:51 ` David Woodhouse
2015-08-04 18:11 ` Catalin Marinas
2015-08-03 22:10 ` Benjamin Herrenschmidt
2015-07-30 22:32 ` Benjamin Herrenschmidt
2015-08-01 16:10 ` Joerg Roedel
2015-07-31 14:52 ` Rik van Riel
2015-07-31 16:13 ` Jerome Glisse
2015-08-01 15:57 ` Joerg Roedel [this message]
2015-08-01 19:08 ` Jerome Glisse
2015-08-03 16:02 ` Joerg Roedel
2015-08-03 18:28 ` Jerome Glisse
2015-08-01 20:46 ` Arnd Bergmann
2015-08-03 16:10 ` Joerg Roedel
2015-08-03 19:23 ` Arnd Bergmann
2015-08-04 15:40 ` Christoph Lameter
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=20150801155728.GC14980@8bytes.org \
--to=joro@8bytes.org \
--cc=jglisse@redhat.com \
--cc=ksummit-discuss@lists.linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox