| /f-stack/dpdk/usertools/ |
| H A D | meson.build | 5 'dpdk-devbind.py', 6 'dpdk-pmdinfo.py', 7 'dpdk-telemetry.py', 8 'dpdk-hugepages.py'
|
| /f-stack/dpdk/doc/guides/compressdevs/ |
| H A D | octeontx.rst | 70 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.1 71 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.2 72 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.3 73 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.4 74 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.5 75 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.6 76 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:00.7 77 ./usertools/dpdk-devbind.py -b vfio-pci 0001:04:01.0
|
| /f-stack/freebsd/contrib/openzfs/contrib/pyzfs/ |
| H A D | Makefile.am | 1 EXTRA_DIST = libzfs_core setup.py.in README LICENSE docs 7 $(PYTHON) setup.py build 27 $(PYTHON) $(builddir)/setup.py install \
|
| H A D | .gitignore | 3 setup.py
|
| /f-stack/dpdk/buildtools/ |
| H A D | meson.build | 6 list_dir_globs = find_program('list-dir-globs.py') 18 map_to_win_cmd = py3 + files('map_to_win.py') 19 sphinx_wrapper = py3 + files('call-sphinx-build.py')
|
| /f-stack/freebsd/contrib/openzfs/tests/test-runner/bin/ |
| H A D | .gitignore | 1 test-runner.py 2 zts-report.py
|
| H A D | Makefile.am | 5 test-runner.py \ 6 zts-report.py
|
| /f-stack/freebsd/contrib/openzfs/scripts/ |
| H A D | common.sh.in | 19 export TEST_RUNNER=${TEST_RUNNER:-$ZTS_DIR/test-runner/bin/test-runner.py} 20 export ZTS_REPORT=${ZTS_REPORT:-$ZTS_DIR/test-runner/bin/zts-report.py}
|
| H A D | zfs2zol-patch.sed | 21 s:usr/src/test/test-runner/cmd/run.py:tests/test-runner/cmd/test-runner.py:g
|
| /f-stack/dpdk/doc/guides/tools/ |
| H A D | hugepages.rst | 65 While any user can run the ``dpdk-hugpages.py`` script to view the 74 dpdk-hugpages.py -s 78 dpdk-hugpages.py -p 1G --setup 2G
|
| H A D | testbbdev.rst | 21 test-bbdev.py [-h] [-p TESTAPP_PATH] [-e EAL_PARAMS] [-t TIMEOUT] 52 ``./test-bbdev.py -c validation`` 55 ``./test-bbdev.py -c latency throughput`` 65 ``./test-bbdev.py -v app/test-bbdev/test_vectors/turbo_dec_test1.data`` 68 ``./test-bbdev.py -v turbo_dec_test1.data turbo_enc_test2.data`` 149 Thanks to the globbing functionality in python test-bbdev.py script allows to 156 …./test-bbdev.py -v app/test-bbdev/test_vectors/turbo_<enc/dec>_c<c>_k<k>_r<r>_e<e>_<extra-info>.da… 204 ./test-bbdev.py -v app/test-bbdev/turbo_*_default.data 254 ./test-bbdev.py -p ../../build/app/dpdk-test-bbdev 268 ./test-bbdev.py -p ../../build/app/dpdk-test-bbdev [all …]
|
| /f-stack/app/redis-5.0.5/src/ |
| H A D | lolwut5.c | 148 int px[4], py[4]; in lwDrawSquare() local 161 py[j] = round(cos(k) * size + y); in lwDrawSquare() 167 lwDrawLine(canvas,px[j],py[j],px[(j+1)%4],py[(j+1)%4],1); in lwDrawSquare()
|
| /f-stack/dpdk/doc/guides/cryptodevs/ |
| H A D | octeontx.rst | 90 by using dpdk-devbind.py script. The OCTEON TX crypto PF device need to be 95 Once the required VFs are enabled, dpdk-devbind.py script can be used to 102 ./usertools/dpdk-devbind.py -u <vf device no> 103 ./usertools/dpdk-devbind.py -b vfio-pci <vf device no>
|
| H A D | octeontx2.rst | 110 Another way to bind the VF would be to use the ``dpdk-devbind.py`` script: 115 ./usertools/dpdk-devbind.py -u 0002:10:00.1 116 ./usertools/dpdk-devbind.py -b vfio-pci 0002:10.00.1
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | lm_virtio_vhost_user.rst | 66 ./dpdk-devbind.py -b igb_uio 0000:02:00.0 73 ./dpdk-devbind.py -b igb_uio 0000:09:00.0 147 ./dpdk-devbind.py -b igb_uio 0000:03:00.0 154 ./dpdk-devbind.py -b igb_uio 0000:06:00.0 419 /root/dpdk/usertools/dpdk-devbind.py --status 426 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:03.0 427 /root/dpdk/usertools/dpdk-devbind.py -b igb_uio 0000:00:04.0 429 /root/dpdk/usertools/dpdk-devbind.py --status
|
| /f-stack/dpdk/doc/guides/regexdevs/ |
| H A D | octeontx2.rst | 31 for use. The script ``dpdk-devbind.py`` script included with DPDK can be 35 ``dpdk-devbind.py --status-dev regex`` can be used to see the state of
|
| /f-stack/app/redis-5.0.5/deps/jemalloc/ |
| H A D | run_tests.sh | 1 $(dirname "$)")/scripts/gen_run_tests.py | bash
|
| /f-stack/dpdk/doc/guides/bbdevs/ |
| H A D | acc100.rst | 113 2. Another way to bind PF with DPDK UIO driver is by using the ``dpdk-devbind.py`` tool 118 ./usertools/dpdk-devbind.py -b igb_uio 0000:06:00.0 175 BBDEV provides a test application, ``test-bbdev.py`` and range of test data for testing 200 ./test-bbdev.py -c validation -n 64 -b 1 -v ./ldpc_dec_default.data 201 ./test-bbdev.py -c validation -n 64 -b 1 -v ./ldpc_enc_default.data 204 The test application ``test-bbdev.py``, supports the ability to configure the PF device with 234 …./test-bbdev.py -e="-c 0xff0 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_defaul…
|
| H A D | fpga_5gnr_fec.rst | 98 2. Another way to bind PF with DPDK UIO driver is by using the ``dpdk-devbind.py`` tool 103 ./usertools/dpdk-devbind.py -b igb_uio 0000:06:00.0 229 BBDEV provides a test application, ``test-bbdev.py`` and range of test data for testing 252 ./test-bbdev.py -c validation -n 64 -b 1 -v ./ldpc_dec_default.data 253 ./test-bbdev.py -c validation -n 64 -b 1 -v ./ldpc_enc_default.data 256 The test application ``test-bbdev.py``, supports the ability to configure the PF device with 293 …./test-bbdev.py -e="-c 0xff0 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./ldpc_dec_defaul…
|
| H A D | fpga_lte_fec.rst | 97 2. Another way to bind PF with DPDK UIO driver is by using the ``dpdk-devbind.py`` tool 102 ./usertools/dpdk-devbind.py -b igb_uio 0000:06:00.0 228 BBDEV provides a test application, ``test-bbdev.py`` and range of test data for testing 251 ./test-bbdev.py -c validation -n 64 -b 8 -v ./turbo_dec_default.data 252 ./test-bbdev.py -c validation -n 64 -b 8 -v ./turbo_enc_default.data 255 The test application ``test-bbdev.py``, supports the ability to configure the PF device with 312 …./test-bbdev.py -e="-c 0xff0 -a${VF_PCI_ADDR}" -c validation -n 64 -b 32 -l 1 -v ./turbo_dec_defau…
|
| /f-stack/dpdk/ |
| H A D | .gitattributes | 3 *.py diff=python
|
| /f-stack/dpdk/doc/guides/linux_gsg/ |
| H A D | linux_drivers.rst | 62 ./usertools/dpdk-devbind.py -b vfio-pci 0000:86:00.0 224 a utility script called ``dpdk-devbind.py`` is provided in the ``usertools`` subdirectory. 232 should be loaded into the kernel before running the ``dpdk-devbind.py`` script. 250 While any user can run the ``dpdk-devbind.py`` script 258 ./usertools/dpdk-devbind.py --status 280 ./usertools/dpdk-devbind.py --bind=uio_pci_generic 04:00.1 286 ./usertools/dpdk-devbind.py --bind=uio_pci_generic eth1 292 ./usertools/dpdk-devbind.py --bind=ixgbe 82:00.0 297 In certain situations, using ``dpdk-devbind.py`` script
|
| /f-stack/freebsd/contrib/libsodium/packaging/dotnet-core/ |
| H A D | README.md | 8 as NuGet packages. The purpose of the `prepare.py` script in this directory is 19 See `prepare.py` for the complete list of supported platforms. 48 2. Run `python3 prepare.py <version>` to generate the `Makefile`, where
|
| /f-stack/dpdk/devtools/ |
| H A D | update-abi.sh | 45 devtools/update_version_map_abi.py {} \
|
| /f-stack/freebsd/contrib/libsodium/test/default/ |
| H A D | nacl-test-wrapper.sh | 29 SEL_LDR=$(find "$NACL_SDK_ROOT" -name sel_ldr.py | head -n 1)
|