To create a pipe object, call the function
const cl_pipe_properties* properties,
|clCreatePipe is missing before version 2.0.
context is a valid OpenCL context used to create the pipe object.
flags is a bit-field that is used to specify allocation and usage information such as the memory arena that should be used to allocate the pipe object and how it will be used. The Memory Flags table describes the possible values for flags. Only
CL_MEM_can be specified when creating a pipe object. If the value specified for flags is 0, the default is used which is
HOST_ NO_ ACCESS
HOST_ NO_ ACCESS
pipe_packet_size is the size in bytes of a pipe packet.
pipe_max_packets specifies the pipe capacity by specifying the maximum number of packets the pipe can hold.
properties specifies a list of properties for the pipe and their corresponding values. Each property name is immediately followed by the corresponding desired value. The list is terminated with 0. Currently, in all OpenCL versions, properties must be
errcode_ret will return an appropriate error code. If errcode_ret is
NULL, no error code is returned.
clCreatePipe returns a valid non-zero pipe object and errcode_ret is set
CL_SUCCESS if the pipe object is created successfully.
Otherwise, it returns a
NULL value with one of the following error values
returned in errcode_ret:
CL_INVALID_if context is not a valid context.
CL_INVALID_if no devices in context support pipes.
CL_INVALID_if values specified in flags are not as defined above.
CL_INVALID_if properties is not
CL_INVALID_if pipe_packet_size is 0 or the pipe_packet_size exceeds
CL_DEVICE_value specified in the Device Queries table for all devices in context or if pipe_max_packets is 0.
PIPE_ MAX_ PACKET_ SIZE
CL_MEM_if there is a failure to allocate memory for the pipe object.
OBJECT_ ALLOCATION_ FAILURE
CL_OUT_if there is a failure to allocate resources required by the OpenCL implementation on the device.
CL_OUT_if there is a failure to allocate resources required by the OpenCL implementation on the host.
OF_ HOST_ MEMORY
Pipes follow the same memory consistency model as defined for buffer and image objects. The pipe state i.e. contents of the pipe across kernel-instances (on the same or different devices) is enforced at a synchronization point.
For more information, see the OpenCL Specification
This page is extracted from the OpenCL Specification. Fixes and changes should be made to the Specification, not directly.