Hi,
I´ve checked a scenario where 2 contexts are created. For each context, I´ve created 64 commands queues. 64 is less than 69 for each context, but the total sum of both contexts is higher than 69. The program continues to crash when 69 commands queues are created overall. Addiotinally, I've changed the parameter GPU_MAX_COMMAND_QUEUES with the command: export GPU_MAX_COMMAND_QUEUES=128 , but I haven't had success.
Hi nibal, I´ve checked syslog but I haven´t seen anything strange.
I wrote this b4 you tested it on a different system. Was looking for a hardware problem, but the chance of the same thing happening in 2 different system is none. Plz ignore.
Yes, as I checked on multiple GPUs, the number of max. command queues seems constant. Also, indeed there is no effect of .GPU_MAX_COMMAND_QUEUES.
I guess, someone from runtime team may provide better insights in this regard. I'll check and get back to you.
Sorry for this delayed reply.
As I've come to know that indeed the number of max. host-side command queues is a hard limit and it is currently set to 70 per-process (69 with a zero based counting). So, the above observation was reasonable.
Regards,
dipak wrote:
Sorry for this delayed reply.
As I've come to know that indeed the number of max. host-side command queues is a hard limit and it is currently set to 70 per-process (69 with a zero based counting). So, the above observation was reasonable.
Regards,
Hmm. So the error code CL_OUT_OF_RESOURCES is correct in this case. We assumed wrongly it was memory, when in fact it was number of queues 😞
Hi dipak !! Don´t worry. Thank you so much for your reply.
Hi dipak !! thank you for your help as well. :-).
Hi dipak, excuse me for the delay of this question. Do you know any document where the statement about the limit of command queues per-process is reported?. Your statement is truth but now I am writting an article and I have to write a reference for this.
Sorry, I'm not aware of any such. I came to know that information from relevant team.
AFAIK, the limit is there because the OCL conformance test expects a predictable amount of queues. The limit is implementation dependent and may vary in future. So, I've doubt that there is any such document publicly available.
Regards,