Lines Matching refs:bbdev

11 optimized libraries to appear as virtual bbdev devices.
33 Physical bbdev devices are discovered during the PCI probe/enumeration of the
53 All virtual bbdev devices support the following initialization parameters:
66 - A unique device index used to designate the bbdev device in all functions
67   exported by the bbdev API.
69 - A device name used to designate the bbdev device in console messages, for
77 From the application point of view, each instance of a bbdev device consists of
97 The configuration of each bbdev device includes the following operations:
103 The ``rte_bbdev_setup_queues`` API is used to setup queues for a bbdev device.
116 The ``rte_bbdev_intr_enable`` API is used to enable interrupts for a bbdev
127 Each bbdev devices queue is individually configured through the
169 The bbdev poll mode device driver library supports NUMA architecture, in which
178 virtual bbdev devices, if the baseband operation and data buffers are in local
183 operations or dequeuing operations on the same bbdev device since this would
195 identify what a bbdev is capable of performing that differs from one device to
196 another. For the full scope of the bbdev capability see the definition of the
203 A device reports its capabilities when registering itself in the bbdev framework.
247 Discovering the features and capabilities of a bbdev device poll mode driver
254 This allows the user to query a specific bbdev PMD and get all the device
280 performed using a burst oriented asynchronous API set. A queue on a bbdev
282 bbdev devices the enqueue burst API will place the operations to be processed
284 baseband operations is usually completed during the enqueue call to the bbdev
286 from the queue on the bbdev device, from physical devices this is usually
295 The burst enqueue API uses a bbdev device identifier and a queue
296 identifier to specify the bbdev device queue to schedule the processing on.
328 An encode bbdev operation is represented by ``rte_bbdev_enc_op`` structure,
330 containers for all necessary information required for the bbdev operation to be
331 processed on a particular bbdev device poll mode driver.
360 If bbdev operations are allocated from a bbdev operation mempool, see next
365 fields in the ``rte_bbdev_*_op`` structure which are then used by the bbdev PMD
372 The bbdev library provides an API set for managing bbdev operations which
374 that the bbdev operation is interleaved optimally across the channels and
385 allocate bbdev operations of a specific type from a given bbdev operation mempool.
408 The bbdev operation structure contains all the mutable data relating to
1092 bbdev framework, by giving a sample code performing a loop-back operation with a
1096 buffers using (**sw_turbo**) bbdev PMD.
1105     /* Get number of available bbdev devices */
1110     /* Create bbdev op pools */
1131         /* Configure all queues belonging to this bbdev device */
1139     /* Start bbdev device */
1205 The bbdev Library API is described in the *DPDK API Reference* document.