• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
jeff8j

OpenCL Continuous Kernel?

4 posts in this topic

I am just starting to learn how to use opencl and from what I can tell there doesnt seem to be a way to run the kernel and read/write the buffers constantly I only see ways of running the kernel then getting the response and restarting the kernel which to me would seem like a huge waste if say some of the threads take longer than others wouldn’t the done ones have to sit around waiting?
0

Share this post


Link to post
Share on other sites
That's quite hard to read because there's no punctuation. Even though I'm reasonably sure where you intended your sentences to end, I'm confused. There's a question mark at the end but the sentences do not seem to form a question of any kind.
0

Share this post


Link to post
Share on other sites
It won't matter, if you have lots of work-items, which you should have. The threads that complete the kernel just restart and run it again for another work-item, so if you have a million work-items and a thousand threads it won't even be noticeable if one of those threads takes 100x longer than the others, as the others will run 1000 times anyway. If you only have as many work-items as there are cores, then yes all the others will wait for the slowest one, but if you have such a complex kernel that's run so few times then OpenCL probably isn't the right tool for the job. In that case, either do it on the CPU instead or try to change your kernel into a smaller kernel that runs 10x as many times and does part of the work each time. Edited by Erik Rufelt
0

Share this post


Link to post
Share on other sites
Hi Stroppy
your absolutely correct I wrote it on the way out the door and was pretty exhausted sorry about that.

Hi Erik
That does make sense I wasnt thinking about it that way until today and realize that I cant think of it as a function to a program but an entire program it self.

Another thought is what if I want results back as fast as possible then I would have to stop all the threads so the buffer could be read correct?
Then in that scenario it would have to restart the kernel since I had to stop everything to be read. Or is their a way to read the output but continue processing?
0

Share this post


Link to post
Share on other sites
You cannot interrupt a kernel in progress except by crashing the driver (and losing all your output buffers in the process). GPU's do not support that kind of execution yet. What I usually do when I need my application to be responsive is to design the kernels to do the absolute minimum amount of work possible in a single kernel enqueue, and just submit them to the card a lot faster, that way I can interrupt it CPU-side whenever and have everything stop quickly.

As for reading back, I suppose you could copy the output buffer to a temporary buffer (still GPU-side), keep launching your kernels and read from that, so that you could still get your card to work while DMA-copying the last execution's results to the CPU, but be wary that if your kernels finish faster than you can actually get your output back to the CPU (for a discrete card, that's generally 4GB/s bandwidth) you [i]will[/i] run out of buffer memory, so it's not a great idea.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0