Home
last modified time | relevance | path

Searched refs:driver (Results 1 – 25 of 55) sorted by relevance

123

/spdk/test/setup/
H A Dacl.sh16 local dev driver
18 while read -r _ dev _ _ _ driver _; do
20 [[ $driver == nvme ]] || continue
22 devs+=("$dev") drivers["$dev"]=$driver
28 local dev driver
32 driver=$(readlink -f "/sys/bus/pci/devices/$dev/driver")
H A Ddriver.sh46 local driver setup_driver marker
49 driver=$(pick_driver)
51 if [[ $driver == "No valid driver found" ]]; then
52 [[ $(setup output config) == "$driver"* ]]
56 echo "Looking for driver=$driver"
61 [[ $setup_driver == $driver ]] || fail=1
/spdk/scripts/common/setup/
H A Dinteractive.sh244 local bdf driver
258 while read -rp "Select driver ($bdf)> " driver; do
259 driver=${driver,,}
260 if [[ -z $driver ]]; then
263 if [[ $driver == "${pci_bus_driver["$bdf"]}" ]]; then
264 echo "$bdf already bound to $driver"
270 # Try to be nice and silently attempt to load the driver just in case
271 modprobe -q "$driver" || tru
[all...]
/spdk/test/external_code/accel/
H A DMakefile20 $(CC) $(COMMON_CFLAGS) -c -fPIC driver.c -o driver.o
21 $(CC) $(COMMON_CFLAGS) -shared module.o driver.o -o libaccel_external_driver.so
22 $(CC) $(COMMON_CFLAGS) -o driver app_driver.c -g -L. -laccel_external_driver \
31 $(CC) $(COMMON_CFLAGS) -o driver module.c driver.c app_driver.c \
/spdk/scripts/
H A Dsetup.sh31 echo "to a generic VFIO kernel driver. If VFIO is not available on the system, this script"
76 echo " Each device in PCI_BLOCKED will be ignored (driver won't be changed)."
81 echo " bind devices to the given driver."
123 local search_paths path driver
126 for driver in contigmem.ko nic_uio.ko; do
128 [[ -f $path/$driver ]] && continue 2
144 old_driver_name=${pci_bus_driver["$bdf"]:-no driver}
147 pci_dev_echo "$bdf" "Already using the $old_driver_name driver"
151 if [[ $old_driver_name != "no driver" ]]; then
152 echo "$bdf" > "/sys/bus/pci/devices/$bdf/driver/unbin
[all...]
H A Dcommon.sh72 local pci=$1 class=$2 vendor=$3 device=$4 driver=$5 mod=$6
85 if [[ -n $driver ]]; then
86 pci_bus_driver["$pci"]=$driver
137 local class vendor device driver mod
140 class=$(< "$pci/class") vendor=$(< "$pci/vendor") device=$(< "$pci/device") driver="" mod=""
141 driver=$(get_pci_driver_sysfs "${pci##*/}")
145 cache_pci "${pci##*/}" "$class" "$vendor" "$device" "$driver" "$mod"
165 # pci class vendor device driver
166 # lspci supports driver listing only under Linux, however, it's not
181 local chip driver
[all...]
H A Dqat_setup.sh38 Upstream intel_qat driver detected. Same version of the driver is seen
87 for driver in "${allowed_drivers[@]}"; do
88 if [ $driver == $driver_to_bind ]; then
151 if [[ -e $vf/driver ]]; then
152 old_driver=$(basename "$(readlink -f "$vf/driver")")
H A Drxe_cfg_small.sh114 local name link driver speed mtu ip rxe rxe_dev active_mtu
116 name="" link="" driver=""
126 if [[ -e $dev/device/driver ]]; then
127 driver=$(readlink -f "$dev/device/driver")
128 driver=${driver##*/}
131 driver=$(uevent "$dev" "DEVTYPE" "virtual")
151 "$driver" \
/spdk/lib/env_dpdk/22.11/
H A Dbus_pci_driver.h42 struct rte_pci_driver *driver; /**< PCI driver used in probing */ member
133 struct rte_driver driver; /**< Inherit core driver. */ member
165 void rte_pci_register(struct rte_pci_driver *driver);
171 (pci_drv).driver.name = RTE_STR(nm);\
184 void rte_pci_unregister(struct rte_pci_driver *driver);
H A Ddev_driver.h31 const struct rte_driver *driver; /**< Driver assigned after probing */ member
/spdk/lib/env_dpdk/22.07/
H A Drte_bus_pci.h73 struct rte_pci_driver *driver; /**< PCI driver used in probing */ member
163 struct rte_driver driver; /**< Inherit core driver. */ member
271 void rte_pci_register(struct rte_pci_driver *driver);
277 (pci_drv).driver.name = RTE_STR(nm);\
289 void rte_pci_unregister(struct rte_pci_driver *driver);
/spdk/test/nvme/perf/
H A DREADME.md38 #### --driver
40 Select between SPDK driver and kernel driver. The Linux Kernel driver has three configurations:
41 Default mode, Hybrid Polling and Classic Polling. The SPDK driver supports 2 fio_plugin modes: bdev…
42 … test with spdk, you will need to bind NVMe devics to the Linux uio_pci_generic or vfio-pci driver.
43 When running test with the Kernel driver, NVMe devices use the Kernel driver. The 5 valid values fo…
60 …U cores that will be used by fio to execute the performance test cases. When spdk driver is chosen,
69 If kernel driver is chosen then for each job with NVME device, all cpu cores with corresponding NUM…
H A Dcommon.sh139 local driver
140 driver=$(grep DRIVER /sys/bus/pci/devices/$bdf/uevent | awk -F"=" '{print $2}')
141 # Use this check to omit blocked devices ( not bound to driver with setup.sh script )
142 if [ "$driver" = "vfio-pci" ] || [ "$driver" = "uio_pci_generic" ]; then
510 echo "Waiting for full nvme driver reload..."
/spdk/lib/env_dpdk/
H A Dpci_event.c103 char driver[SPDK_UEVENT_MSG_LEN]; in parse_subsystem_event() local
111 memset(driver, 0, SPDK_UEVENT_MSG_LEN); in parse_subsystem_event()
126 snprintf(driver, sizeof(driver), "%s", buf); in parse_subsystem_event()
169 if (!strncmp(driver, "vfio-pci", 8)) { in parse_subsystem_event()
/spdk/doc/
H A Didxd.md21 passing in a value of `true` indicates that the IDXD kernel driver is loaded and
22 that SPDK will use work queue(s) surfaced by the driver. Passing in `false` means
23 that the SPDK user space driver will be used to initialize the hardware.
H A Dvirtio.md1 # Virtio driver {#virtio}
5 SPDK Virtio driver is a C library that allows communicating with Virtio devices.
8 The driver supports two different usage models:
14 The driver, just like the SPDK @ref vhost, is using pollers instead of standard
H A Daccel_fw.md52 Leveraging user space idxd driver: The DSA devices are managed by the SPDK user space
53 driver in a dedicated SPDK process, then the device cannot be shared by another
56 Leveraging kernel space driver: The DSA devices are managed by kernel
59 this usage is the kernel dependency, i.e., idxd kernel driver must be supported and loaded
81 will attempt to load the SPDK user-space idxd driver. To use the built-in
82 kernel driver on Linux, add the `-k` parameter. See the next section for
83 details on using the kernel driver.
93 **Additionally**, to use the kernel DSA driver from SPDK, users are required to possess
96 #### How to use kernel idxd driver {#accel_idxd_kernel}
98 There are several dependencies to leverage the Linux idxd driver for driving DSA devices.
[all …]
H A Duserspace.md20 the kernel driver from the device and on Linux is done by
22 SPDK then rebinds the driver to one of two special device drivers that come
24 [uio](https://www.kernel.org/doc/html/latest/driver-api/uio-howto.html) or
27 system that the device has a driver bound to it so it won't automatically try
28 to re-bind the default driver. They don't actually initialize the hardware in
49 into the current process, which allows the driver to perform
89 A user space driver, on the other hand, is embedded into a single application.
H A Dvmd.md1 # VMD driver {#vmd}
19 The driver is responsible for enumeration and hooking NVMe devices behind VMD
38 To enable VMD driver enumeration, the following steps are required:
/spdk/test/nvme/
H A Dhw_hotplug.sh
/spdk/test/external_code/
H A Dtest_make.sh50 run_test "external_run_accel_driver_shared" $_sudo $test_root/accel/driver \
51 --json $test_root/accel/driver.json
102 run_test "external_run_accel_driver_static" $_sudo $test_root/accel/driver \
103 --json $test_root/accel/driver.json
/spdk/test/common/config/pkgdep/patches/dpdk/20.11/
H A Ddpdk_pci.patch1 Subject: [PATCH] pci/linux: free the device if no kernel driver configured
16 + } else { /* no kernel driver */
/spdk/scripts/perf/nvme/
H A DREADME7 …SPDK setup.sh script to unbind NVMe devices from the kernel driver and bind them to the uio driver.
/spdk/test/nvme/overhead/
H A DREADME2 and completion for both the SPDK NVMe driver and an AIO file handle.
23 desired, attach controllers individually to the kernel NVMe driver
/spdk/module/accel/dpdk_cryptodev/
H A Daccel_dpdk_cryptodev.c30 /* This controls how many ops will be dequeued from the crypto driver in one run
33 * as the ACCEL_DPDK_CRYPTODEV_AESNI_MB driver for example does all the crypto work on dequeue whereas the
34 * QAT driver just dequeues what has been completed already.
134 enum accel_dpdk_cryptodev_driver_type driver;
220 SPDK_ERRLOG("Unsupported driver %s\n", driver_name); in accel_dpdk_cryptodev_set_driver()
224 SPDK_NOTICELOG("Using driver %s\n", driver_name); in accel_dpdk_cryptodev_set_driver()
441 if (key->driver == ACCEL_DPDK_CRYPTODEV_DRIVER_MLX5_PCI) { in accel_dpdk_find_key_handle_in_channel()
602 assert(priv->driver < ACCEL_DPDK_CRYPTODEV_DRIVER_LAST); in accel_dpdk_cryptodev_process_task()
638 qp = crypto_ch->device_qp[priv->driver]; in accel_dpdk_cryptodev_process_task()
653 SPDK_ERRLOG("Failed to find a key handle, driver in accel_dpdk_cryptodev_process_task()
133 enum accel_dpdk_cryptodev_driver_type driver; global() member
1448 enum accel_dpdk_cryptodev_driver_type driver; accel_dpdk_cryptodev_key_init() local
[all...]

123