Home
last modified time | relevance | path

Searched refs:user (Results 1 – 25 of 207) sorted by relevance

123456789

/dpdk/lib/eal/include/generic/
H A Drte_spinlock.h187 volatile int user; /**< core id using lock, -1 for unused */ member
205 slr->user = -1; in rte_spinlock_recursive_init()
219 if (slr->user != id) { in rte_spinlock_recursive_lock()
221 slr->user = id; in rte_spinlock_recursive_lock()
234 slr->user = -1; in rte_spinlock_recursive_unlock()
253 if (slr->user != id) { in rte_spinlock_recursive_trylock()
256 slr->user = id; in rte_spinlock_recursive_trylock()
H A Drte_ticketlock.h130 int user; /**< core id using lock, TICKET_LOCK_INVALID_ID for unused */ member
150 __atomic_store_n(&tlr->user, TICKET_LOCK_INVALID_ID, __ATOMIC_RELAXED); in rte_ticketlock_recursive_init()
165 if (__atomic_load_n(&tlr->user, __ATOMIC_RELAXED) != id) { in rte_ticketlock_recursive_lock()
167 __atomic_store_n(&tlr->user, id, __ATOMIC_RELAXED); in rte_ticketlock_recursive_lock()
182 __atomic_store_n(&tlr->user, TICKET_LOCK_INVALID_ID, in rte_ticketlock_recursive_unlock()
201 if (__atomic_load_n(&tlr->user, __ATOMIC_RELAXED) != id) { in rte_ticketlock_recursive_trylock()
204 __atomic_store_n(&tlr->user, id, __ATOMIC_RELAXED); in rte_ticketlock_recursive_trylock()
/dpdk/doc/guides/howto/
H A Dvirtio_user_as_exceptional_path.rst9 The virtual device, virtio-user, was originally introduced with vhost-user
11 and user space container networking.
30 send/receive packets to/from user space DPDK applications, which has little
31 impact on user space polling thread (except that it might enter into kernel
34 The overview of an application using virtio-user as exceptional path is shown
41 Overview of a DPDK app using virtio-user as exceptional path
64 with outside, and one virtio-user to communicate with kernel.
H A Dvirtio_user_for_container_networking.rst26 The virtual device, virtio-user, with unmodified vhost-user backend, is designed
27 for high performance user space container networking or inter-process
30 The overview of accelerating container networking by virtio-user is shown
37 Overview of accelerating container networking by virtio-user
76 #. Start a testpmd on the host with a vhost-user port.
84 #. Start a container instance with a virtio-user port.
H A Dlm_virtio_vhost_user.rst223 Hit Enter key. This brings the user to the testpmd prompt.
288 DISK_IMG="/home/user/disk_image/virt1_sml.disk"
315 -netdev type=vhost-user,id=net1,chardev=chr0,vhostforce \
318 -netdev type=vhost-user,id=net2,chardev=chr1,vhostforce \
357 # Script for use with vhost user sample application
364 DISK_IMG="/home/user/disk_image/virt1_sml.disk"
391 -netdev type=vhost-user,id=net1,chardev=chr0,vhostforce \
394 -netdev type=vhost-user,id=net2,chardev=chr1,vhostforce \
H A Dtelemetry.rst20 is run by a root user).
51 #. When connected, the script displays the following, waiting for user input::
57 #. The user can now input commands to send across the socket, and receive the
95 When multiple DPDK process instances are running on a system, the user will
/dpdk/doc/guides/sample_app_ug/
H A Dvhost_blk.rst8 which used as the backend of Qemu vhost-user-blk device. Users can extend
10 memory based block device. Similar with vhost-user-net device, the sample
15 Development Kit, https://github.com/spdk/spdk) vhost-user-blk target,
16 for DPDK vhost library used in storage area, user can take SPDK as
54 -device vhost-user-blk-pci,packed=on,chardev=char0,num-queues=1 \
58 You must check whether your Qemu can support "vhost-user-blk" or not,
H A Dvdpa.rst7 The vdpa sample application creates vhost-user sockets by using the
17 This section shows the steps of how to start VMs with vDPA vhost-user
39 /tmp/vhost-user-, then the socket files will be named as /tmp/vhost-user-<n>
89 -netdev type=vhost-user,id=vdpa,chardev=char0 \
96 Suggest to use QEMU 3.0.0 which extends vhost-user for vDPA.
100 vDPA supports cross-backend live migration, user can migrate SW vhost backend
H A Dvhost_crypto.rst8 which used as the backend of Qemu vhost-user-crypto device. Similar with
9 vhost-user-net and vhost-user-scsi device, the sample application used
51 the user wants to use LKCF in the guest, this feature shall be turned off.
75 -object cryptodev-vhost-user,id={obj_id},chardev={chardev_id} \
80 You must check whether your Qemu can support "vhost-user-crypto" or not.
H A Dvmdq_dcb_forwarding.rst18 address, VLAN ID and VLAN user priority fields.
20 Then, DCB places each packet into one of queues within that group, based upon the VLAN user priorit…
46 In Linux* user space, the application can display statistics with the number of packets received on…
75 … user@target:~$ ./<build_dir>/examples/dpdk-vmdq_dcb -l 0-3 -n 4 -- -p 0x3 --nb-pools 32 --nb-tcs 4
105 and dividing up the possible user priority values equally among the individual queues
107 if the number of pools is 32, then the user priority fields are allocated 2 to a queue.
108 If 16 pools are used, then each of the 8 user priority fields is allocated to its own queue within …
110 then the user priority fields are allocated 2 to one tc, and a tc has 2 queues mapping to it, then
120 :start-after: Dividing up the possible user priority values. 8<
121 :end-before: >8 End of dividing up the possible user priority values.
[all …]
H A Dvhost.rst60 -netdev type=vhost-user,id=hostnet1,chardev=char1 \
65 For basic vhost-user support, QEMU 2.2 (or above) is required. For
107 Specifies the vhost-user socket file path.
110 DPDK vhost-user will act as the client mode when such option is given.
162 A very simple vhost-user net driver which demonstrates how to use the generic
166 This parameter is used to specify DMA type for async vhost-user net driver which
171 Async vhost-user net driver will be used if --dmas is set. For example
209 DPDK virtio-user PMD can be the replacement of QEMU.
216 added at virtio-user PMD side as a startup item.
/dpdk/doc/guides/prog_guide/
H A Dvhost_lib.rst7 The vhost library implements a user space virtio net server allowing the user
8 to manipulate the virtio ring directly. In another words, it allows the user
136 vhost-user driver could be vhost-user net, yet it could be something else,
137 say, vhost-user SCSI.
186 the end of initializing a vhost-user driver.
204 Frees the memory and vhost-user message handlers created in
285 Vhost-user Implementations
289 vhost-user implementation has two options:
291 * DPDK vhost-user acts as the server.
299 * DPDK vhost-user acts as the client.
[all …]
H A Dkernel_nic_interface.rst122 bound to any particular core, but the user can set the core affinity for
248 user to specify the interface name, set the MTU size, set an explicit or
265 There are currently four callbacks for which the user can register
275 Called when the user changes the MTU size of the KNI
281 Called when the user changes the MAC address of the KNI interface.
282 For example, when the user runs ``ip link set address <MAC>
283 dev <ifaceX>``. If the user sets this callback function to NULL,
291 Called when the user changes the promiscuity state of the KNI
292 interface. For example, when the user runs ``ip link set promisc
293 [on|off] dev <ifaceX>``. If the user sets this callback function to
[all …]
H A Dprofile_app.rst70 get a wall clock counter in user space. Typically it runs at a lower clock frequency than the CPU c…
79 at CPU frequency. However, access to the PMU cycle counter from user space is
81 cycle counter for user space access by configuring the PMU from the privileged
99 In order to enable ``PMU`` based ``rte_rdtsc()``, user needs to configure the
/dpdk/doc/guides/nics/
H A Dvhost.rst8 The user can handle virtqueues as one of normal DPDK port.
26 * Don't need to stop RX/TX, when the user wants to stop a guest or a virtio-net driver on guest.
31 The user can specify below arguments in `--vdev` option.
72 The user can register an event callback handler with ``rte_eth_dev_callback_register()``.
104 -netdev vhost-user,id=net0,chardev=chr0,vhostforce,queues=1 \
H A Dfeatures.rst56 * **[uses] user config**: ``dev_conf.intr_conf.lsc``.
71 * **[uses] user config**: ``dev_conf.intr_conf.rmv``.
94 * **[uses] user config**: ``dev_conf.intr_conf.rxq``.
279 * **[uses] user config**: ``dev_conf.rx_adv_conf.rss_conf``.
331 * **[uses] user config**: ``dev_conf.rx_adv_conf.vmdq_dcb_conf``.
332 * **[uses] user config**: ``dev_conf.rx_adv_conf.vmdq_rx_conf``.
333 * **[uses] user config**: ``dev_conf.tx_adv_conf.vmdq_dcb_tx_conf``.
334 * **[uses] user config**: ``dev_conf.tx_adv_conf.vmdq_tx_conf``.
354 * **[uses] user config**: ``dev_conf.rx_adv_conf.vmdq_dcb_conf``.
355 * **[uses] user config**: ``dev_conf.rx_adv_conf.dcb_rx_conf``.
[all …]
H A Dtxgbe.rst123 Use to set PHY link mode and enable FFE parameters for user debugging.
129 PHY parameter used for user debugging. Setting other values to
134 PHY parameter used for user debugging. Setting other values to
139 PHY parameter used for user debugging. Setting other values to
156 to any number of user-defined rules.
/dpdk/doc/guides/cryptodevs/
H A Dchacha20_poly1305.rst23 To build DPDK with the Chacha20-poly1305 PMD the user is required to download
25 and compile it on their user system before building DPDK.
29 After downloading the library, the user needs to unpack and compile it
75 In order to enable this virtual crypto PMD, user must:
79 To use the PMD in an application, user must:
H A Daesni_mb.rst86 To build DPDK with the AESNI_MB_PMD the user is required to download the multi-buffer
88 and compile it on their user system before building DPDK.
144 In order to enable this virtual crypto PMD, user must:
148 To use the PMD in an application, user must:
176 * 12 bytes: used mainly for IPsec, as it requires 12 bytes from the user, which internally
178 (no padding required from the user)
H A Dzuc.rst35 To build DPDK with the ZUC_PMD the user is required to download the multi-buffer
37 and compile it on their user system before building DPDK.
41 After downloading the library, the user needs to unpack and compile it
89 In order to enable this virtual crypto PMD, user must:
93 To use the PMD in an application, user must:
H A Dsnow3g.rst35 To build DPDK with the SNOW3G_PMD the user is required to download the multi-buffer
37 and compile it on their user system before building DPDK.
41 After downloading the library, the user needs to unpack and compile it
89 In order to enable this virtual crypto PMD, user must:
93 To use the PMD in an application, user must:
H A Dkasumi.rst36 To build DPDK with the KASUMI_PMD the user is required to download the multi-buffer
38 and compile it on their user system before building DPDK.
42 After downloading the library, the user needs to unpack and compile it
90 In order to enable this virtual crypto PMD, user must:
94 To use the PMD in an application, user must:
H A Daesni_gcm.rst40 To build DPDK with the AESNI_GCM_PMD the user is required to download the multi-buffer
42 and compile it on their user system before building DPDK.
96 In order to enable this virtual crypto PMD, user must:
100 To use the PMD in an application, user must:
/dpdk/doc/guides/compressdevs/
H A Dzlib.rst37 * To build DPDK with ZLIB library, the user is required to download the ``libz`` library.
45 * Once downloaded, the user needs to build the library.
56 To use the PMD in an application, user must:
/dpdk/doc/guides/mempool/
H A Dcnxk.rst61 Since this configuration is per application, the end user needs to
82 devices available in the system. In order to avoid, the end user to bind the
85 device. In case, if end user need to run mempool as a standalone device
86 (without ethdev or eventdev), end user needs to bind a mempool device using

123456789