template <typename BuilderImpl>class WireTableBaseBuilder
Defined at line 9622 of file fidling/gen/sdk/fidl/fuchsia.sysmem2/fuchsia.sysmem2/cpp/fidl/fuchsia.sysmem2/cpp/wire_types.h
Public Methods
::fuchsia_sysmem2::wire::BufferCollectionInfo Build ()Build and return the table. The builder should not be used after this.
bool has_settings ()void clear_settings ()Clears the settings field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fuchsia_sysmem2::wire::SingleBufferSettings & settings ()These settings apply to all the buffers in the initial buffer
allocation.
This field will always be set by sysmem.
BuilderImpl & settings (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fuchsia_sysmem2::wire::SingleBufferSettings>> elem)These settings apply to all the buffers in the initial buffer
allocation.
This field will always be set by sysmem.
bool has_buffers ()void clear_buffers ()Clears the buffers field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
::fidl::VectorView< ::fuchsia_sysmem2::wire::VmoBuffer> & buffers ()VMO handles (and vmo_usable_start offset) for each buffer in the
collection.
The size of this vector is the buffer_count (buffer_count is not sent
separately).
All buffer VMO handles have identical size and access rights. The size
is in settings.buffer_settings.size_bytes.
The VMO access rights are determined based on the usages which the
client specified when allocating the buffer collection. For example, a
client which expressed a read-only usage will receive VMOs without write
rights. In addition, the rights can be attenuated by the parameter to
BufferCollectionToken.Duplicate() calls.
This field will always have VmoBuffer(s) in it, even if the participant
specifies usage whieh does not require VMO handles. This permits such a
participant to know the vmo_usable_start values, in case that's of any
use to the participant.
This field will always be set by sysmem, even if the participant doesn't
specify any buffer usage (but the [`fuchsia.sysmem2/VmoBuffer.vmo`]
sub-field within this field won't be set in that case).
BuilderImpl & buffers (Wrapper_Ignore_Me_< ::fidl::ObjectView< ::fidl::VectorView< ::fuchsia_sysmem2::wire::VmoBuffer>>> elem)VMO handles (and vmo_usable_start offset) for each buffer in the
collection.
The size of this vector is the buffer_count (buffer_count is not sent
separately).
All buffer VMO handles have identical size and access rights. The size
is in settings.buffer_settings.size_bytes.
The VMO access rights are determined based on the usages which the
client specified when allocating the buffer collection. For example, a
client which expressed a read-only usage will receive VMOs without write
rights. In addition, the rights can be attenuated by the parameter to
BufferCollectionToken.Duplicate() calls.
This field will always have VmoBuffer(s) in it, even if the participant
specifies usage whieh does not require VMO handles. This permits such a
participant to know the vmo_usable_start values, in case that's of any
use to the participant.
This field will always be set by sysmem, even if the participant doesn't
specify any buffer usage (but the [`fuchsia.sysmem2/VmoBuffer.vmo`]
sub-field within this field won't be set in that case).
bool has_buffer_collection_id ()void clear_buffer_collection_id ()Clears the buffer_collection_id field.
This method should be used sparingly, such as only during tests, as it has
O(number_of_fields) complexity.
uint64_t & buffer_collection_id ()This number is unique among all logical buffer collections per boot.
This ID number will be the same for all BufferCollectionToken(s),
BufferCollection(s), and BufferCollectionTokenGroup(s) associated with
the same logical buffer collection (derived from the same root token
created with fuchsia.sysmem2.Allocator.CreateSharedCollection, or with
CreateNonSharedCollection).
The same ID can be retrieved from a BufferCollectionToken,
BufferCollection, or BufferCollectionTokenGroup using
GetBufferCollectionId (at the cost of a round-trip to sysmem and back).
This field will always be set by sysmem.
BuilderImpl & buffer_collection_id (Wrapper_Ignore_Me_< ::fidl::ObjectView<uint64_t>> elem)This number is unique among all logical buffer collections per boot.
This ID number will be the same for all BufferCollectionToken(s),
BufferCollection(s), and BufferCollectionTokenGroup(s) associated with
the same logical buffer collection (derived from the same root token
created with fuchsia.sysmem2.Allocator.CreateSharedCollection, or with
CreateNonSharedCollection).
The same ID can be retrieved from a BufferCollectionToken,
BufferCollection, or BufferCollectionTokenGroup using
GetBufferCollectionId (at the cost of a round-trip to sysmem and back).
This field will always be set by sysmem.
Protected Methods
void WireTableBaseBuilder< ::fuchsia_sysmem2::wire::BufferCollectionInfo, BuilderImpl> (::fidl::ObjectView< ::fidl::WireTableFrame< ::fuchsia_sysmem2::wire::BufferCollectionInfo>> && frame)