linux-kernel - Re: GPU scheduling

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1236921043.2553.11.camel@ht.satnam>
Date:	Fri, 13 Mar 2009 10:40:43 +0530
From:	Jaswinder Singh Rajput <jaswinder@...nel.org>
To:	Peter Teoh <htmldeveloper@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: GPU scheduling

On Fri, 2009-03-13 at 12:02 +0800, Peter Teoh wrote:
> Firstly I am a newbie in this area of GPU.   Does it make sense to
> talk about scheduling tasks on the GPU?   Not the graphics processing
> types of tasks, nor the parallel matrix calculation types, but those
> normally executed by CPU, so as to share workload along with the CPU?
> 
> I supposed the machine codes will be different, right?   But if the
> compiler can generate the opcodes for the GPU, and the GPU and CPU can
> detect concurrent use of memory bus address (for the implementation of
> spinlock - CPU/GPU synchronization), which is synonymous to GPU and
> CPU accessing the same memory for data/instructions, then I don't see
> there is any problem with the "GPU scheduler" implementation concept,
> right?   Or perhaps the hardware does not meet all these requirements?
>   Or any other problems which u can forsee?   (eg, GPU being
> prorietary, the opcodes may not be revealed/available, and therefore
> the internal schedulers is not known to us as well?)

Major issue is almost all GPUs are proprietary and they only provide
libraries for users and do not disclose internals.

And now latest GPUs are running blind race with having thousands of
cores.

--
JSR

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/