Home
last modified time | relevance | path

Searched refs:device (Results 1 – 25 of 516) sorted by relevance

12345678910>>...21

/dpdk/drivers/event/opdl/
H A Dopdl_evdev_init.c510 if (device->opdl[i]) in destroy_queues_and_rings()
527 struct opdl_queue *queue = &device->queue[device->nb_queues]; in initialise_queue()
536 device->q_map_ex_to_in[queue->external_qid] = device->nb_queues; in initialise_queue()
543 device->nb_queues++; in initialise_queue()
555 "%s_%u", device->service_name, device->nb_opdls); in create_opdl()
557 device->opdl[device->nb_opdls] = in create_opdl()
562 device->socket); in create_opdl()
564 if (!device->opdl[device->nb_opdls]) { in create_opdl()
571 device->nb_opdls++; in create_opdl()
622 if (device->nb_ports != device->max_port_nb) { in create_queues_and_rings()
[all …]
H A Dopdl_evdev_xstats.c25 if (!device->do_validation) in opdl_xstats_init()
40 device->port_xstat[index].id = index; in opdl_xstats_init()
53 if (!device->do_validation) in opdl_xstats_uninit()
56 memset(device->port_xstat, in opdl_xstats_uninit()
58 sizeof(device->port_xstat)); in opdl_xstats_uninit()
72 if (!device->do_validation) in opdl_xstats_get_names()
107 if (!device->do_validation) in opdl_xstats_get()
140 if (!device->do_validation) in opdl_xstats_get_by_name()
149 device->port_xstat[i].stat.name, in opdl_xstats_get_by_name()
153 if (device->port_xstat[i].value) in opdl_xstats_get_by_name()
[all …]
H A Dopdl_evdev.c198 p->opdl = device; in opdl_port_setup()
204 device->nb_ports++; in opdl_port_setup()
252 if (device->nb_q_md > device->max_queue_nb) { in opdl_queue_setup()
301 device->q_md[device->nb_q_md].ext_id = queue_id; in opdl_queue_setup()
302 device->q_md[device->nb_q_md].type = type; in opdl_queue_setup()
303 device->q_md[device->nb_q_md].setup = 1; in opdl_queue_setup()
304 device->nb_q_md++; in opdl_queue_setup()
473 device->started = 0; in opdl_stop()
520 (device->nb_queues - device->nb_opdls), in opdl_start()
543 memset(&device->s_md, in opdl_close()
[all …]
/dpdk/doc/guides/nics/
H A Dfail_safe.rst8 virtual device that allows using device supporting hotplug, without modifying
42 A sub-device can be any DPDK device, including possibly another fail-safe device.
55 sub-device.
59 In case where the sub-device is also used as an allowed device, using ``-a``
162 own device iterator.
184 missing sub-device.
207 Fallback device
210 The fail-safe will fail-over onto this device when the preferred device is
213 Preferred device
217 When this device is plugged, it is always used as emitting device.
[all …]
H A Davp.rst8 The Accelerated Virtual Port (AVP) device is a shared memory based device
13 etc.). The platform offers the virtio device type as the default device when
14 launching a virtual machine or creating a virtual machine port. The AVP device
15 is a specialized device available to customers that require increased
21 supports a subset of the full Ethernet device API to enable the application to
22 use the standard device configuration functions and packet receive/transmit
28 significantly improved throughput and latency over other device types.
30 The AVP device implementation is integrated with the QEMU/KVM live-migration
44 * Up to 8 receive and transmit queues per device,
/dpdk/doc/guides/prog_guide/
H A Dlink_bonding_poll_mode_drv_lib.rst136 The librte_net_bond bonded device are compatible with the Ethernet device API
146 After a slave device is added to a bonded device slave is stopped using
150 device. If RSS is enabled for bonding device, this mode is also enabled on new
238 device and then all further slaves added to the bonded device must support
241 A bonding device must have a minimum of one slave before the bonding device
260 bonded device to read.
278 configuration of the bonded device on being added to a bonded device.
355 APIs but at least one slave device must be added to the link bonding device
360 bonding device then the link status of the bonding device will go down.
373 each device. Each device can have multiple options arranged in a comma
[all …]
H A Dregexdev.rst7 The RegEx library provides a RegEx device framework for management and
31 their PCI device identifier, each unique PCI BDF (bus/bridge, device,
42 - A unique device index used to designate the RegEx device in all functions
45 - A device name used to designate the RegEx device in console messages, for
55 - Resetting the device into a well-known default state.
58 The rte_regexdev_configure API is used to configure a RegEx device.
73 /**< Maximum matches per scan configured on this device.
86 /**< Number of rules per group to configure on this device.
94 /**< Number of groups to configure on this device.
118 Each Regex device should be configured with the rule database.
[all …]
H A Ddmadev.rst7 The DMA library provides a DMA device framework for management and provisioning
15 The DMA framework provides a generic DMA device framework which supports both
41 PCI BDF (bus/bridge, device, function). Specific physical DMA controllers, like
51 Each DMA device, whether physical or virtual is uniquely designated by two
54 - A unique device index used to designate the DMA device in all functions
57 - A device name used to designate the DMA device in console messages, for
65 can be used to get the device info and supported features.
67 Silent mode is a special device capability which does not require the
86 device and start the hardware processing of them:
115 The statistics from a dmadev device can be got via the statistics functions,
[all …]
H A Drawdev.rst10 In terms of device flavor (type) support, DPDK currently has ethernet
12 (virtual device) support.
14 For a new type of device, for example an accelerator, there are not many
24 library or EAL for each device type. This library provides a generic set of
34 to a large subset of device types. None of the operations are mandatory to
42 * Statistics - Fetch arbitrary device statistics
46 to/from device driver. This can be achieved by maintaining context
50 other well known device types like eth and crypto:
81 rawdev DevF ID and take control of device
82 * Applications can then continue using the device through rawdev API
[all …]
/dpdk/lib/security/
H A Drte_security_driver.h36 typedef int (*security_session_create_t)(void *device,
47 typedef int (*security_session_destroy_t)(void *device,
62 typedef int (*security_session_update_t)(void *device,
75 typedef unsigned int (*security_session_get_size)(void *device);
88 typedef int (*security_session_stats_get_t)(void *device,
107 typedef int (*security_set_pkt_metadata_t)(void *device,
124 typedef int (*security_get_userdata_t)(void *device,
137 void *device);
/dpdk/drivers/bus/auxiliary/linux/
H A Dauxiliary.c39 dev->device.name = dev->name; in auxiliary_scan_one()
40 dev->device.bus = &auxiliary_bus.bus; in auxiliary_scan_one()
47 dev->device.numa_node = tmp; in auxiliary_scan_one()
49 dev->device.numa_node = -1; in auxiliary_scan_one()
51 dev->device.numa_node = 0; in auxiliary_scan_one()
64 if (rte_dev_is_probed(&dev2->device) && in auxiliary_scan_one()
65 dev2->device.devargs != dev->device.devargs) { in auxiliary_scan_one()
67 rte_devargs_remove(dev2->device.devargs); in auxiliary_scan_one()
/dpdk/doc/guides/vdpadevs/
H A Dsfc.rst17 ef100 device can be configured in the net device or vDPA mode.
19 device is to be used in vDPA mode. If this parameter is not specified, device
20 will be probed by net/sfc driver and will used as a net device.
22 This PMD uses libefx (common/sfc_efx) code to access the device firmware.
61 The following per-device parameters can be passed via EAL PCI device
69 Choose the mode of operation of ef100 device.
70 **net** device will work as network device and will be probed by net/sfc driver.
71 **vdpa** device will work as vdpa device and will be probed by vdpa/sfc driver.
72 If this parameter is not specified then ef100 device will operate as network device.
101 dot and a PCI device identifier (``XXXX:XX:XX.X``) to the prefix.
H A Difc.rst10 directly by DMA. Besides, it supports dirty page logging and device state
17 IFCVF's vendor ID and device ID are same as that of virtio net pci device,
18 with its specific subsystem vendor ID and device ID. To let the device be
20 device is to be used in vDPA mode, rather than polling mode, virtio PMD will
21 skip when it detects this message. If no this parameter specified, device
22 will not be used as a vDPA device, and it will be driven by virtio PMD.
26 the driver probe a new container is created for this device, with this
30 The device argument "sw-live-migration=1" will configure the driver into SW
32 thread when LM happens, this thread will help device to log dirty pages. Thus
53 This function gets called when virtio driver stops device in VM.
[all …]
/dpdk/drivers/bus/vmbus/
H A Dvmbus_channel.c84 const struct rte_vmbus_device *dev = chan->device; in rte_vmbus_chan_signal_tx()
221 vmbus_set_event(chan->device, chan); in rte_vmbus_chan_signal_read()
319 device->device.numa_node); in vmbus_chan_create()
324 chan->device = device; in vmbus_chan_create()
346 uio_res = vmbus_uio_find_resource(device); in rte_vmbus_chan_open()
352 err = vmbus_chan_create(device, device->relid, 0, in rte_vmbus_chan_open()
353 device->monitor_id, new_chan); in rte_vmbus_chan_open()
355 device->primary = *new_chan; in rte_vmbus_chan_open()
362 if (vmbus_uio_subchannels_supported(device, device->primary)) in rte_vmbus_max_channels()
391 const struct rte_vmbus_device *device = chan->device; in rte_vmbus_chan_close() local
[all …]
/dpdk/drivers/bus/vdev/
H A Drte_bus_vdev.h23 struct rte_device device; /**< Inherit core device */ member
31 container_of(ptr, struct rte_vdev_device, device)
34 container_of(ptr, const struct rte_vdev_device, device)
36 #define RTE_ETH_DEV_TO_VDEV(eth_dev) RTE_DEV_TO_VDEV((eth_dev)->device)
41 if (dev && dev->device.name) in rte_vdev_device_name()
42 return dev->device.name; in rte_vdev_device_name()
49 if (dev && dev->device.devargs) in rte_vdev_device_args()
50 return dev->device.devargs->args; in rte_vdev_device_args()
H A Dvdev.c149 if (!vdev->device.driver) { in vdev_dma_map()
174 if (!vdev->device.driver) { in vdev_dma_unmap()
286 dev->device.bus = &rte_vdev_bus; in insert_vdev()
288 dev->device.name = devargs->name; in insert_vdev()
302 dev->device.devargs = devargs; in insert_vdev()
345 if (!dev->device.driver) { in vdev_remove_driver()
533 dev->device.bus = &rte_vdev_bus; in vdev_scan()
534 dev->device.devargs = devargs; in vdev_scan()
536 dev->device.name = devargs->name; in vdev_scan()
587 if (cmp(&dev->device, data) == 0) in rte_vdev_find_device()
[all …]
/dpdk/drivers/bus/vmbus/linux/
H A Dvmbus_bus.c126 SYSFS_VMBUS_DEVICES "/%s/uio", dev->device.name); in vmbus_get_uio_dev()
245 dev->device.bus = &rte_vmbus_bus.bus; in vmbus_scan_one()
246 dev->device.name = dev_name = strdup(name); in vmbus_scan_one()
247 if (!dev->device.name) in vmbus_scan_one()
294 dev->device.numa_node = tmp; in vmbus_scan_one()
297 dev->device.numa_node = SOCKET_ID_ANY; in vmbus_scan_one()
300 dev->device.devargs = vmbus_devargs_lookup(dev); in vmbus_scan_one()
375 vmbus_uio_irq_control(device, 1); in rte_vmbus_irq_mask()
380 vmbus_uio_irq_control(device, 0); in rte_vmbus_irq_unmask()
383 int rte_vmbus_irq_read(struct rte_vmbus_device *device) in rte_vmbus_irq_read() argument
[all …]
/dpdk/drivers/bus/fslmc/
H A Dfslmc_bus.c158 dev->device.bus = &rte_fslmc_bus.bus; in scan_one_fslmc_device()
209 dev->device.name = strdup(dev_name); in scan_one_fslmc_device()
210 if (!dev->device.name) { in scan_one_fslmc_device()
463 if (rte_dev_is_probed(&dev->device)) in rte_fslmc_probe()
466 if (dev->device.devargs && in rte_fslmc_probe()
469 dev->device.name); in rte_fslmc_probe()
474 (dev->device.devargs && in rte_fslmc_probe()
515 if (cmp(&dev->device, data) == 0) { in rte_fslmc_find_device()
517 dev->device.name); in rte_fslmc_find_device()
518 return &dev->device; in rte_fslmc_find_device()
[all …]
/dpdk/app/test/
H A Dtest_security.c254 void *device; member
299 void *device; member
329 void *device; member
353 void *device; member
383 void *device; member
414 void *device; member
449 void *device; member
460 mock_get_userdata(void *device, in mock_get_userdata() argument
484 void *device; member
555 .device = NULL,
[all …]
/dpdk/doc/guides/gpus/features/
H A Dcuda.ini7 Get device info = Y
8 Share CPU memory with device = Y
9 Allocate device memory = Y
11 CPU map device memory = Y
12 CPU unmap device memory = Y
H A Ddefault.ini10 Get device info =
11 Share CPU memory with device =
12 Allocate device memory =
14 CPU map device memory =
15 CPU unmap device memory =
/dpdk/drivers/bus/dpaa/
H A Ddpaa_bus.c173 dev->device.bus = &rte_dpaa_bus.bus; in dpaa_create_device_list()
198 dev->device.name = dev->name; in dpaa_create_device_list()
245 dev->device.name = dev->name; in dpaa_create_device_list()
268 dev->device.name = dev->name; in dpaa_create_device_list()
683 if (rte_dev_is_probed(&dev->device)) in rte_dpaa_bus_probe()
687 (dev->device.devargs && in rte_dpaa_bus_probe()
692 (dev->device.devargs && in rte_dpaa_bus_probe()
700 dev->device.driver = &drv->driver; in rte_dpaa_bus_probe()
734 if (cmp(&dev->device, data) == 0) { in rte_dpaa_find_device()
736 return &dev->device; in rte_dpaa_find_device()
[all …]
/dpdk/doc/guides/sample_app_ug/
H A Dvhost_blk.rst7 The vhost_blk sample application implemented a simple block device,
8 which used as the backend of Qemu vhost-user-blk device. Users can extend
9 the exist example to use other type of block device(e.g. AIO) besides
10 memory based block device. Similar with vhost-user-net device, the sample
22 This section shows the steps how to start a VM with the block device as
52 -device ide-hd,drive=disk,bootindex=0 \
54 -device vhost-user-blk-pci,packed=on,chardev=char0,num-queues=1 \
62 packed=on means the device support packed ring but need the guest kernel
/dpdk/drivers/bus/pci/
H A Dpci_common.c70 dev->device.devargs = devargs; in pci_name_set()
79 dev->device.name = dev->device.devargs->name; in pci_name_set()
82 dev->device.name = dev->name; in pci_name_set()
184 dev->device.numa_node); in rte_pci_probe_one_driver()
197 dev->device.numa_node = 0; in rte_pci_probe_one_driver()
203 dev->device.name); in rte_pci_probe_one_driver()
230 dev->device.name); in rte_pci_probe_one_driver()
241 dev->device.name); in rte_pci_probe_one_driver()
267 dev->device.numa_node); in rte_pci_probe_one_driver()
324 dev->device.driver = NULL; in rte_pci_detach_dev()
[all …]
/dpdk/doc/guides/tools/
H A Ddevbind.rst31 For each device, it displays the PCI domain, bus, slot and function,
32 along with a text description of the device. Depending upon whether the
33 device is being used by a kernel driver, the ``vfio-pci`` driver, or no
37 - any suitable drivers not currently using that device e.g. ``unused=vfio-pci``
44 Select the driver to use or "none" to unbind the device
48 Unbind a device (Equivalent to ``-b none``)
64 …Any Virtual Function device can be used with VFIO on its own, but physical devices will require ei…
67 …If your device is behind a PCI-to-PCI bridge, the bridge will then be part of the IOMMU group in w…
68 …Therefore, the bridge driver should also be unbound from the bridge PCI device for VFIO to work wi…
79 To display current device status::
[all …]

12345678910>>...21