Home
last modified time | relevance | path

Searched refs:backend (Results 1 – 25 of 44) sorted by relevance

12

/f-stack/freebsd/contrib/device-tree/Bindings/display/
H A Dallwinner,sun4i-a10-display-backend.yaml19 - allwinner,sun4i-a10-display-backend
20 - allwinner,sun5i-a13-display-backend
21 - allwinner,sun6i-a31-display-backend
22 - allwinner,sun7i-a20-display-backend
23 - allwinner,sun8i-a23-display-backend
24 - allwinner,sun8i-a33-display-backend
25 - allwinner,sun9i-a80-display-backend
49 - description: The backend module clock
50 - description: The backend DRAM clock
192 display-backend@1e60000 {
[all …]
H A Dallwinner,sun4i-a10-display-engine.yaml15 either directly the backend or the frontend) is represented as an
/f-stack/dpdk/doc/guides/howto/
H A Dvirtio_user_for_container_networking.rst26 The virtual device, virtio-user, with unmodified vhost-user backend, is designed
48 to vhost backend. But it's not feasible for a container, as a process, to share
49 all virtual memory regions to backend. So only those virtual memory regions
50 (aka, hugepages initialized in DPDK) are sent to backend. It restricts that only
102 file to share with vhost backend.
104 under this option which cannot be reopened to share with vhost backend.
109 will bring confusion when sharing hugepage files with backend by name.
H A Dvirtio_user_as_exceptional_path.rst10 backend, as a high performance solution for IPC (Inter-Process Communication)
13 Virtio_user with vhost-kernel backend is a solution for exceptional path,
H A Dlm_virtio_vhost_user.rst305 -object memory-backend-file,id=mem,size=1024M,mem-path=/mnt/huge,share=on \
381 -object memory-backend-file,id=mem,size=1024M,mem-path=/mnt/huge,share=on \
H A Dopenwrt.rst128 -object memory-backend-file,id=mem,size=2048M,mem-path=/tmp/hugepages,share=on \
/f-stack/dpdk/doc/guides/sample_app_ug/
H A Dvdpa.rst8 vDPA backend. vDPA stands for vhost Data Path Acceleration which utilizes
18 backend and verify network connection & live migration.
100 vDPA supports cross-backend live migration, user can migrate SW vhost backend
101 VM to vDPA backend VM and vice versa. Here are the detailed steps. Assume A is
H A Dvhost_blk.rst8 which used as the backend of Qemu vhost-user-blk device. Users can extend
49 -m $mem -object memory-backend-file,id=mem,size=$mem,\
H A Dvhost_crypto.rst8 which used as the backend of Qemu vhost-user-crypto device. Similar with
70 -m $mem -object memory-backend-file,id=mem,size=$mem,\
H A Dvhost.rst56 -m $mem -object memory-backend-file,id=mem,size=$mem,mem-path=/dev/hugepages,share=on \
215 backend enables "builtin-net-driver", "--socket-mem" option should be
/f-stack/dpdk/doc/guides/cryptodevs/
H A Dvirtio.rst30 only support indirect buffers to communication with the virtio backend.
32 chaining algorithm since the vhost crypto backend only these algorithms
/f-stack/dpdk/doc/guides/windows_gsg/
H A Dbuild_dpdk.rst17 with the Ninja backend.
72 If using Ninja, download and install the backend from
/f-stack/dpdk/doc/guides/vdpadevs/
H A Difc.rst9 works as a HW vhost backend which can send/receive packets to/from virtio
47 This function gets called to set up HW data path backend when virtio driver
/f-stack/dpdk/doc/guides/nics/
H A Dvirtio.rst12 Vhost is a kernel acceleration module for virtio qemu backend.
56 * Features of mac/vlan filter are supported, negotiation with vhost/backend are needed to support…
57 … When backend can't support vlan filter, virtio app on guest should not enable vlan filter in order
84 Qemu standard backend without vhost support isn't tested, and probably isn't supported.
355 driver, and works as a HW vhost backend. This argument is used to specify
377 It is used to specify a path to connect to vhost backend.
398 backend.
402 It is used to enable the server mode when using vhost-user backend.
H A Dkni.rst18 There is no physical device backend for the virtual KNI device.
62 backend device by default.
H A De1000em.rst90 The Qemu provides several choices for the emulated network device backend.
91 … Most commonly used is a TAP networking backend that uses a TAP networking device in the host.
/f-stack/freebsd/contrib/device-tree/Bindings/crypto/
H A Dhisilicon,hip07-sec.txt9 Region 0 has registers to control the backend processing engines.
/f-stack/app/nginx-1.16.1/
H A DCHANGES740 handshake to a backend.
1453 backend response header line.
1475 backend response while caching.
1660 backend responses.
2114 *) Bugfix: in backend usage accounting.
2453 backend returned incorrect response.
2953 if SSL connection to backend was used.
2995 and proxies to an HTTPS backend.
4804 name received from backend.
6501 first request to a backend only.
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/sound/
H A Damlogic,gx-sound-card.yaml68 dai-link representing backend links should have at least one subnode.
H A Damlogic,axg-sound-card.txt42 - codec: dai-link representing backend links should have at least one subnode.
/f-stack/freebsd/contrib/device-tree/Bindings/reserved-memory/
H A Dramoops.txt6 is named "ramoops" after the backend, rather than "pstore" which is the
/f-stack/dpdk/doc/guides/prog_guide/
H A Dvhost_lib.rst14 For QEMU, this is done by using the ``-object memory-backend-file,share=on,...``
22 messages (passed through a Unix domain socket file) to tell the backend all
207 Enable or disable zero copy feature of the vhost crypto backend.
350 with accelerated backend.
/f-stack/freebsd/contrib/device-tree/src/arm/
H A Dsun8i-a23.dtsi66 compatible = "allwinner,sun8i-a23-display-backend";
H A Dsun8i-a33.dtsi365 compatible = "allwinner,sun8i-a33-display-backend";
366 /* A33 has an extra "SAT" module packed inside the display backend */
H A Dsun9i-a80.dtsi643 be0: display-backend@3200000 {
644 compatible = "allwinner,sun9i-a80-display-backend";
683 be1: display-backend@3240000 {
684 compatible = "allwinner,sun9i-a80-display-backend";

12