Part of the Khronos Group

The Industry's Foundation for High Performance Graphics

from games to virtual reality, mobile phones to supercomputers

Page 2 of 2 FirstFirst 12
Results 11 to 13 of 13

Thread: Are two OpenGL contexts still necessary for concurrent copy and render?

  1. #11
    Intern Newbie
    Join Date
    Nov 2008
    Does the silence mean no one knows?

  2. #12
    Junior Member Regular Contributor
    Join Date
    May 2013
    One of the reasons I hate GL_ARB_buffer_storage is that you can't specify the memory location except for the stupid hint.
    If you could it would be easy to use one system memory buffer, access it with easy read/write and then use glCopyBufferSubData (ARB_copy_buffer) to move it over to a vram buffer. That would pretty much ensure that the DMA copy engine would be used and no CPU/GPU cycles would be wasted.

  3. #13
    Senior Member OpenGL Pro Aleksandar's Avatar
    Join Date
    Jul 2009
    Quote Originally Posted by Prune View Post
    Does the silence mean no one knows?
    Why don't you try and share with us the findings. Catch for a few seconds what happens on your system when the transfer is active, and analyze with GPUView.
    What I can confirm is that Fermi really has three hardware queues, and some actions are done in parallel (other queues are used for Desktop Window Manager in the cases I saw).

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts