From: Lauri Kasanen <cand@gmx.com>
To: libre-riscv-dev@lists.libre-riscv.org
Subject: Re: [libre-riscv-dev] Request for input and technical expertise for Systèmes Libres Amazon Alexa IOT Pitch 10-JUN-2020
Date: Mon, 8 Jun 2020 17:15:07 +0300
Message-ID: <20200608171507.e6e184efe3296e9c0b186e5f@gmx.com> (raw)
In-Reply-To: <20200608135554.54lyyd5wd3xlzi4m@topoi.pooq.com>
On Mon, 8 Jun 2020 09:55:54 -0400
Hendrik Boom <hendrik@topoi.pooq.com> wrote:
> And on avoiding data copying between CPU ad GPU:
>
> I believe the OpenGL API involves copying data from CPU buffers to GPU
> buffers, with the understanding that the CPU copies can be discarded
> while the GPU goes on with its copy.
>
> Having the same storage for both sets of buffers could obviously obviate
> these copies, except that software that uses this API will likely rely
> on being able to overwrite the CPU-side buffers with impunity. So the
> copy will still have to be done.
>
> Do I misunderstand OpenGL? Is Vulcan different? Will users want to
> bypass these libraries and use the graphics instructios directly? Or
> is there some other sublety I'm missing?
Your understanding is correct at a high level, one way of using OpenGL
will have to do that memcpy even on the Libresoc. Vulkan is explicit and
there are other ways in OpenGL too.
However you're missing the copy after that. On a traditional system,
using OpenGL that way, there will be a copy after the memcpy, to
transfer everything over PCI-E to the GPU. That's one of the copies that
Libresoc eliminates.
Intel and AMD APUs may also eliminate that, sharing the main RAM, but
integrating the GPU in the same package does not save them from
marshalling the commands. Etc.
- Lauri
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 23:42 Cole Poirier
2020-06-07 23:55 ` Luke Kenneth Casson Leighton
2020-06-08 0:29 ` Jacob Lifshay
2020-06-08 10:17 ` Staf Verhaegen
2020-06-08 11:13 ` Luke Kenneth Casson Leighton
2020-06-08 12:37 ` Staf Verhaegen
2020-06-08 13:55 ` Hendrik Boom
2020-06-08 14:15 ` Lauri Kasanen [this message]
2020-06-08 15:27 ` Luke Kenneth Casson Leighton
2020-06-09 1:17 ` Cole Poirier
2020-06-09 10:34 ` Luke Kenneth Casson Leighton
2020-06-09 19:01 ` Cole Poirier
2020-06-09 22:01 ` Hendrik Boom
2020-06-10 0:43 ` Cole Poirier
2020-06-10 0:44 ` Yehowshua
2020-06-10 2:46 ` Hendrik Boom
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=20200608171507.e6e184efe3296e9c0b186e5f@gmx.com \
--to=cand@gmx.com \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git