CL_DEVICE_MAX_WORK_ITEM_SIZES on Intel core i3

CL_DEVICE_MAX_WORK_ITEM_SIZES on Intel core i3

Hi All,

When i discovery devices (after intstalling openCL intel SDK). I am getting following output...
Why is the CL_DEVICE_MAX_WORK_ITEMS_SIZES are reported 0 / 0 / 0 - what does it mean? could you pls explain whether following output is correct?

Number of platforms: 1

Number of devices in platform Intel OpenCL: 1--- Info for device Intel Core i3 CPU M 380 @ 2.53GHz : ---

CL_DEVICE_NAME: Intel Core i3CPU M 380 @2.53GHz

CL_DEVICE_VENDOR: Intel Corporation

CL_DRIVER_VERSION: 1.1

CL_DEVICE_TYPE: CL_DEVICE_TYPE_CPU

CL_DEVICE_MAX_COMPUTE_UNITS: 4

CL_DEVICE_MAX_WORK_ITEM_DIMENSIONS: 3

CL_DEVICE_MAX_WORK_ITEM_SIZES: 0 / 0 / 0

CL_DEVICE_MAX_WORK_GROUP_SIZE: 1024

CL_DEVICE_MAX_CLOCK_FREQUENCY: 2530 MHz

CL_DEVICE_ADDRESS_BITS: 64

CL_DEVICE_MAX_MEM_ALLOC_SIZE: 971 MByte

CL_DEVICE_GLOBAL_MEM_SIZE: 3887 MByte

CL_DEVICE_ERROR_CORRECTION_SUPPORT: no

CL_DEVICE_LOCAL_MEM_TYPE: global

CL_DEVICE_LOCAL_MEM_SIZE: 32 KByte

CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 128 KByte

CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_OUT_OF_ORDER_EXEC_MODE_ENABLE

CL_DEVICE_QUEUE_PROPERTIES: CL_QUEUE_PROFILING_ENABLE

CL_DEVICE_IMAGE_SUPPORT: 1

CL_DEVICE_MAX_READ_IMAGE_ARGS: 128

CL_DEVICE_MAX_WRITE_IMAGE_ARGS: 128

CL_DEVICE_SINGLE_FP_CONFIG: CL_FP_DENORM CL_FP_INF_NAN CL_FP_ROUND_TO_NEAREST

CL_DEVICE_2D_MAX_WIDTH 0

CL_DEVICE_2D_MAX_HEIGHT 0

CL_DEVICE_3D_MAX_WIDTH 0

CL_DEVICE_3D_MAX_HEIGHT 0

CL_DEVICE_3D_MAX_DEPTH 0

CL_DEVICE_PREFERRED_VECTOR_WIDTH_ CHAR 16, SHORT 8, INT 4, LONG 2, FLOAT 4, DOUBLE 2

Thanking you all.

3 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Hi,

Can you please post the code that queries this values?
What is the return value you have from the function?

Also the values for WIDTH/HEIGHT/DEPTH are wrong.
Thanks,
Evgeny

Thanks Evgeny for your reply. I am using JOCL wrapper. I am running samples fromhttp://www.jocl.org/samples/samples.htmlesp.JOCLDeviceQuery. Your answer seems to suggest that the problem is in JOCL implementation.

Leave a Comment

Please sign in to add a comment. Not a member? Join today