Searched refs:CLI (Results 1 – 16 of 16) sorted by relevance
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | pipeline.rst | 14 Each pipeline is built through the CLI, either by invoking commands one by one, or through a CLI sc… 15 The CLI can also be used to update the pipeline tables or poll the pipeline statistics. 34 * Argument: Path to the CLI script file to be run at application startup. 35 No CLI script file will run at startup if this argument is not present. 109 The main thread is creating and managing all the application objects based on CLI input.
|
| H A D | ip_pipeline.rst | 22 Pipelines are created and managed through Command Line Interface (CLI): 27 * All the application objects are created and managed through CLI commands: 47 * Argument: Path to the CLI script file to be run at application startup. 48 No CLI script file will run at startup if this argument is not present. 125 The main thread is creating and managing all the application objects based on CLI input. 211 Command Line Interface (CLI)
|
| H A D | vm_power_management.rst | 73 - A CLI for changing frequency from within a VM is also included 83 - CLI: For adding VM channels to monitor, inspecting and changing channel 276 The application requires exactly two cores to run. One core for the CLI 284 After successful initialization, the VM Power Manager CLI prompt appears: 299 executing operations on a VM within the CLI. VMs do not have to be 302 It is possible to issue several commands from the CLI to manage VMs. 351 Print to the CLI information on the specified VM. The information lists 433 The distribution also provides a guest CLI for validating the setup. 435 For both ``l3fwd-power`` and the guest CLI, the host application must use 568 After successful initialization, the VM Power Manager Guest CLI prompt [all …]
|
| /f-stack/freebsd/contrib/zstd/ |
| H A D | TESTING.md | 13 - `tests/playTests.sh` on x86_64, without the tests on long data (CLI tests) 25 - Valgrind Test (`make -C tests valgrindTest`) (testing CLI and fuzzer under valgrind)
|
| H A D | CHANGELOG | 422 Fixed : CLI -d output to stdout by default when input is stdin (#322) 423 Fixed : CLI correctly detects console on Mac OS-X 424 Fixed : CLI supports recursive mode `-r` on Mac OS-X 435 CLI supports legacy formats v0.4+ 468 Modified : default compression level for CLI is now 3 486 fixed : CLI displays system error message when destination file cannot be created (#231). Reported …
|
| /f-stack/freebsd/contrib/zstd/programs/ |
| H A D | README.md | 4 Command Line Interface (CLI) can be created using the `make` command without any additional paramet… 5 There are however other Makefile targets that create different variations of CLI: 6 - `zstd` : default CLI supporting gzip-like arguments; includes dictionary builder, benchmark, and … 8 - `zstd-small` : CLI optimized for minimal size; no dictionary builder, no benchmark, and no suppor… 9 - `zstd-compress` : version of CLI which can only compress into zstd format 10 - `zstd-decompress` : version of CLI which can only decompress zstd format 91 CLI supports aggregation of parameters i.e. `-b1`, `-e18`, and `-i1` can be joined into `-b1e18i1`. 120 Usage of the dictionary builder and created dictionaries with CLI: 128 CLI includes in-memory compression benchmark module for zstd. 229 This functionality can be useful when `zstd` CLI is invoked in a way that doesn't allow passing arg…
|
| /f-stack/tools/libxo/doc/ |
| H A D | faq.rst | 28 generate XML that is rendered by the CLI (think: login shell) into 30 the CLI, and ensures that all components emit XML, and that it is 44 which is feed to the CLI, where data from the ODL files tell is 109 a JUNOS-like CLI to do the rendering, and we can't depend on
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | softnic.rst | 217 The Soft NIC firmware, for example- `softnic/firmware.cli`, consists of following CLI commands 218 for creating and managing software based NIC pipelines. For more details, please refer to CLI 320 firmware specifies CLI commands for port configuration, pipeline creation, 322 the flow rules can be added through the testpmd CLI.
|
| H A D | mlx5.rst | 1539 as IP), the following commands must be entered from its CLI to get the same 1659 - Using testpmd CLI:
|
| /f-stack/freebsd/i386/i386/ |
| H A D | vm86.c | 69 #define CLI 0xfa macro 321 case CLI: in vm86_emulate()
|
| /f-stack/app/redis-5.0.5/deps/ |
| H A D | README.md | 58 …is-cli and redis-benchmark behave as expecteed, since we have no tests for CLI utilities currently.
|
| /f-stack/dpdk/doc/guides/rel_notes/ |
| H A D | release_2_1.rst | 85 * Implementation of the command line interface (CLI) for each pipeline type 86 has been moved to the separate compilation unit. Syntax of pipeline CLI 92 * Master pipeline with CLI interface has been added.
|
| H A D | release_16_07.rst | 189 * Streamline the CLI code.
|
| H A D | release_2_2.rst | 199 using CLI commands.
|
| /f-stack/dpdk/doc/guides/testpmd_app_ug/ |
| H A D | testpmd_funcs.rst | 69 will execute all CLI commands contained within the file immediately before 76 CLI commands to be read from /home/ubuntu/flow-create-commands.txt 91 Read all CLI commands from /home/ubuntu/flow-create-commands.txt 107 Read all CLI commands from /home/ubuntu/flow-create-commands.txt
|
| /f-stack/app/redis-5.0.5/ |
| H A D | 00-RELEASENOTES | 1584 CLI Help text loop verifies arg count
|