9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Drawterm GPU (was: Software philosophy)
Date: Thu, 23 Sep 2021 21:50:49 -0400	[thread overview]
Message-ID: <1c42a137-c9ff-fd2d-6846-dbc65a18f791@fjrhome.net> (raw)
In-Reply-To: <220e868b-8403-4bd0-8a18-cecc308a1766@sirjofri.de>

Maybe /dev/gpgpu (general-purpose GPU) would be more to the point?


On 8/22/21 2:50 PM, sirjofri wrote:
>
> 22.08.2021 20:25:12 ori@eigenstate.org:
>
>> Quoth sirjofri <sirjofri+ml-9fans@sirjofri.de>:
>>>
>>> 22.08.2021 18:41:06 ori@eigenstate.org:
>>> Basically do software rendering on the GPU?
>>
>> Yes. Or software neural net evaluation on the GPU.
>> Or software video decoding on the GPU. Or software
>> image transforms on the GPU. Or software signal
>> processing on the GPU.
>>
>> If there's an interface to be selected, it needs
>> to be tractable to implement, *and* general purpose
>> enough for everything that wants to use it.
>>
>>> Well, it's totally possible. Even Nanite (the new system in Unreal 
>>> Engine
>>> 5) has its own rasterizer and I believe even its own base pass. Also
>>> Lumen does software rendering for global illumination.
>>>
>>> But for serious 3d AAA stuff we'd have to consider: Lumen is for 
>>> next-gen
>>> GPUs and Nanite for newer GPUs. We'll never reach their quality in
>>> realtime if we don't use the GPU features (built-in rasterizer, ...) to
>>> have enough free power for crazy software calculation.
>>
>> By the time any code is written, next-gen GPUs will be
>> previous-gen GPUs.
>>
>> General compute is what any hardware you buy a few years
>> from now will be doing -- and it's far more intersting
>> in terms of what capabilities it allows.
>>
>>> I like that /dev/compute approach, but may I suggest putting it below
>>> another directory /dev/gpu/compute so we have the ability to add
>>> /dev/gpu/{vertex,geometry,fragment,tessellation,pixel} later?
>>
>> I think supporting those is a cost we should not pay. It's
>> fundamentally solving a less general problem, and adds a
>> lot of complexity for the potential of a small performance
>> boost.
>>
>> We already have zero people sinking time into the slim
>> interface; sinking time into a fatter interface seems
>> like a bad idea.
> 
> Gotcha.
> 
> Maybe I'll find some time to implement some kind of gpufs or /dev/gpu
> (if it's general purpose I'd suggest renaming compute to gpu since
> "compute" could be anything. The computer does compute, wow.).
> 
> sirjofri

------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/Tad29bfc223dc4fbe-Mb1c40d6c9d3bca972decad36
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

  reply	other threads:[~2021-09-24  1:51 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-22 12:10 Stuart Morrow
2021-08-22 12:29 ` sirjofri
2021-08-22 13:44   ` Paul Lalonde
2021-08-22 13:53     ` Eli Cohen
2021-09-01  0:29       ` kokamoto
2021-09-01  7:35         ` sirjofri
2021-09-02  5:01           ` kokamoto
2021-09-02  5:21             ` Eli Cohen
2021-09-03 23:06               ` kokamoto
2021-08-22 14:57     ` sirjofri
2021-08-22 16:45       ` ori
2021-08-22 15:47     ` Bakul Shah
2021-08-22 16:23       ` Paul Lalonde
2021-08-22 19:04         ` Bakul Shah
2021-08-22 19:09           ` Paul Lalonde
2021-08-23  4:13             ` Bakul Shah
2021-08-23  5:23               ` sirjofri
2021-08-22 16:41     ` ori
2021-08-22 17:29       ` sirjofri
2021-08-22 18:25         ` ori
2021-08-22 18:50           ` sirjofri
2021-09-24  1:50             ` Frank D. Engel, Jr. [this message]
2021-08-22 21:10           ` Philip Silva via 9fans
  -- strict thread matches above, loose matches on Subject: below --
2021-08-18 22:00 [9fans] Software philosophy Eli Cohen
2021-08-22  2:46 ` kokamoto
2021-08-22  3:16   ` Eli Cohen
2021-08-22  7:07     ` [9fans] Drawterm GPU (was: Software philosophy) sirjofri
2021-08-22 10:04       ` Frank D. Engel, Jr.
2021-08-22 11:49         ` sirjofri
2021-08-22 12:24           ` Chris McGee

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=1c42a137-c9ff-fd2d-6846-dbc65a18f791@fjrhome.net \
    --to=fde101@fjrhome.net \
    --cc=9fans@9fans.net \
    /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;
as well as URLs for NNTP newsgroup(s).