-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Documentation] Programming Model, Kernel Programming guide #1388
Conversation
Documentation preview: show. |
922a7a9
to
67400a3
Compare
executes a single addition. Note that the array sizes for the input and output | ||
arguments are equal to the size of the execution range. For very large arrays, | ||
the design will not scale as there is usually an upper bound for the range size | ||
depending on device. For most current Intel GPU devices, the maximum range size | ||
is 2^32 and a kernel requesting more work items than that bound will not | ||
execute. As such, programmers need to consider the size of the data and the | ||
access patterns for their kernels before scheduling a range kernel. The maximum | ||
number of work items can be queried programmatically as shown in | ||
:ref:`ex_max_work_item`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this chunk can be better explained in terms of maximum range limit instead of maximum array size because you have always have arrays larger than max range and map multiple array elements to a single work-item.
Moreover, this piece of text seems like a better fit in the below section where semantic rules are explained.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have restructured the section. Hopefully, it reads better now.
docs/source/user_guide/kernel_programming/writing-range-kernel.rst
Outdated
Show resolved
Hide resolved
86636d9
to
02523ca
Compare
@adarshyoga can you please give the Kernel programming guide a read once more. I have updated the all the section except the |
7c6906a
to
b189e38
Compare
b189e38
to
f82360b
Compare
Documentation preview removed. |
[Documentation] Programming Model, Kernel Programming guide 8e3b63d
Adds new material to the kernel programming guide and the programming model sections.
Fixes #1042