Curbe is GEN's hardware resource, used to send kernel's constant information to hardware, such as kernel arguments. __gen_gpgpu_get_curbe_size is add by commit 43138b8d, it will return the used curbe size of this kernel. The hardware's curbe size has restriction, if kernel used curbe size larger then hardware's restriction, beignet will print this warning and trunk the used curbe size.
Thanks, Yang Rong From: Vaughan, Thomas E [mailto:tevau...@ball.com] Sent: Wednesday, January 31, 2018 11:59 PM To: Yang, Rong R <rong.r.y...@intel.com>; beignet@lists.freedesktop.org Subject: RE: warning, curbe size exceed limitation. Thanks for replying! I'm not writing any OpenCL code directly. I'm using the ArrayFire C++ library, which JIT generates OpenCL and compiles it when the process runs. That is, I have no OpenCL source code, and I don't write any C or C++ code that interacts with kernels directly or even knows what they are. My unit tests pass, though, and so it seems that the calculations are being done correctly. I wonder how ArrayFire decides on sizes of chunks of work, and I wonder how much of a performance hit I'm taking on Bay Trail because of this. Can you explain what "curbe" stands for and what's really going on in __gen_gpgpu_get_curbe_size()? -- Thomas E. Vaughan 720 201 7058 (cell) From: Yang, Rong R [mailto:rong.r.y...@intel.com] Sent: January 31, 2018 02:08 To: Vaughan, Thomas E <tevau...@ball.com<mailto:tevau...@ball.com>>; beignet@lists.freedesktop.org<mailto:beignet@lists.freedesktop.org> Subject: RE: warning, curbe size exceed limitation. Do you use this array as kernel's argument? If the argument's size exceeds the argument buffer's size, beignet will print this warning. And IVB's argument buffer size is larger than BayTrail. Thanks, Yang Rong From: Beignet [mailto:beignet-boun...@lists.freedesktop.org] On Behalf Of Vaughan, Thomas E Sent: Wednesday, January 31, 2018 2:04 AM To: beignet@lists.freedesktop.org<mailto:beignet@lists.freedesktop.org> Subject: [Beignet] warning, curbe size exceed limitation. Thanks to Rebecca Palmer and to Mark Thompson for replying to my last plea for help over the weekend. Now that I have started to get things working with the Atom GPU on Debian, I have noticed an odd message when I run some ArrayFire code that was tested on Ivy Bridge. My application prints out "warning, curbe size exceed limitation" in various places. For example, at one point I try to tile a 7x176 array into a 7x176x7 array, and that message is issued twice. Does anyone have a clue about what's going on? -- Thomas E. Vaughan 720 201 7058 (cell) This message and any enclosures are intended only for the addressee. Please notify the sender by email if you are not the intended recipient. If you are not the intended recipient, you may not use, copy, disclose, or distribute this message or its contents or enclosures to any other person and any such actions may be unlawful. Ball reserves the right to monitor and review all messages and enclosures sent to or from this email address. This message and any enclosures are intended only for the addressee. Please notify the sender by email if you are not the intended recipient. If you are not the intended recipient, you may not use, copy, disclose, or distribute this message or its contents or enclosures to any other person and any such actions may be unlawful. Ball reserves the right to monitor and review all messages and enclosures sent to or from this email address.
_______________________________________________ Beignet mailing list Beignet@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/beignet
