| /f-stack/dpdk/doc/guides/prog_guide/ |
| H A D | pdump_lib.rst | 14 The library uses a generic multi process channel to facilitate communication 15 between primary and secondary process for enabling/disabling packet capture on 45 The primary process using ``librte_pdump`` is responsible for initializing the packet 47 multi process channel to facilitate communication with secondary process, so the 48 secondary process ``app/pdump`` tool is responsible for enabling and disabling the packet capture o… 53 …ry API ``rte_pdump_init()``, initializes the packet capture framework by creating the multi process 54 …nel using ``rte_mp_action_register()`` API. The primary process will listen to secondary process r… 55 to enable or disable the packet capture over the multi process channel. 59 the request to the primary process over the multi process channel. The primary process takes this r… 62 the rte_ring that secondary process have passed to these APIs. [all …]
|
| H A D | multi_proc_support.rst | 6 Multi-process Support 17 For now, there are two types of process specified: 35 To support these two process types, and other multi-process setups described later, 54 On application start-up in a primary or standalone process, 63 Refer to `Multi-process Limitations`_ for details of 86 DPDK multi-process support can be used to create a set of peer processes where each process perform… 134 Any network ports being used by one process should be blocked by every other process. 149 Multi-process Limitations 156 This makes secondary process startup process generally unreliable. Disabling 175 …to transfer the interrupt information from the primary process to any secondary process that needs… [all …]
|
| H A D | generic_receive_offload_lib.rst | 9 small packets into larger ones, GRO enables applications to process 20 types. One GRO type is in charge of process one kind of packets. For 31 6864 to process the IPv4 ID field. 50 which process N packets at a time. Using the lightweight mode API to 58 packets that ``rte_gro_reassemble_burst()`` can process in an invocation 114 fields (we call them as "key"). To process an input packet, the algorithm 189 We comply RFC 6864 to process the IPv4 ID field. Specifically, 206 - GRO library doesn't support to process the packets with IPv4 209 - GRO library just supports to process the packet organized
|
| H A D | packet_distrib_lib.rst | 32 …The process API call will poll all the worker cache lines to see what workers are requesting packe… 44 #. Once all input packets passed to the process API have either been distributed to workers 46 then the process API returns to the caller. 57 which should only be called on the lcore which also calls the process API. 71 Using the process and returned_pkts API, the following application workflow can be used, 81 are likely of less use that the process and returned_pkts APIS, and are principally provided to aid…
|
| H A D | lpm6_lib.rst | 75 or the subsequent tbl8s we might need to continue the lookup process in deeper levels of the tree. 81 By splitting the process in different tables/levels and limiting the number of tbl8s, 102 The first field can either contain a number indicating the tbl8 in which the lookup process should … 106 and whether the search process have finished or not respectively. 129 and the external entry flag to 0 (meaning the lookup process ends at this point, 140 (meaning the lookup process must continue since the rule hasn't been explored completely). 144 * Repeat the process until the tbl8 at the right level (depending on the depth) has been reached 154 By doing this we ensure that during the lookup process, if a rule matching the IP address exists, 165 The lookup process is much simpler and quicker. In this case: 176 * Repeat the process until either we find an invalid entry (lookup miss) or a valid entry with th…
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | multi_process.rst | 6 Multi-process Sample Application 30 Basic Multi-process Example 75 To run the secondary process to communicate with the primary process, 83 …ng the parameter altogether will cause the process to try and start as a primary rather than secon… 85 Once the process type is specified correctly, 106 The secondary process can be stopped and restarted without affecting the primary process. 138 Symmetric Multi-process Example 158 Each process reads a different RX queue on each port and so does not contend with any other process… 242 Client-Server Multi-process Example 264 The server process must be run initially as the primary process to set up all memory structures for… [all …]
|
| H A D | server_node_efd.rst | 42 Upon initializing, the frontend server node (process) creates a flow 46 The sample application assigns a specific target node_id (process) for each of 57 The main loop of the server process receives a burst of packets, then for 70 Upon initializing, the worker node (process) creates a flow table (a regular 117 they can access the queues created by the primary process to distribute packets. 135 The first process, the front-end server, creates and populates the EFD table, 229 After this, a new burst of packets is received and this process is 255 The second process, the back-end node, receives the packets from the shared 258 At initialization, it attaches to the server process memory, to have 266 "is server process running?\n"); [all …]
|
| /f-stack/dpdk/lib/librte_eal/windows/ |
| H A D | eal_memory.c | 270 HANDLE process; in eal_mem_reserve() local 279 process = GetCurrentProcess(); in eal_mem_reserve() 281 virt = VirtualAlloc2(process, requested_addr, size, in eal_mem_reserve() 318 HANDLE process; in eal_mem_commit() local 324 process = GetCurrentProcess(); in eal_mem_commit() 338 process, requested_addr, size, flags)) { in eal_mem_commit() 393 HANDLE process; in eal_mem_decommit() local 397 process = GetCurrentProcess(); in eal_mem_decommit() 444 HANDLE process; in mem_free() local 446 process = GetCurrentProcess(); in mem_free() [all …]
|
| H A D | eal_debug.c | 21 HANDLE process = GetCurrentProcess(); in rte_dump_stack() local 23 ret = SymInitialize(process, NULL, TRUE); in rte_dump_stack() 46 ret = SymFromAddr(process, address, &sym_disp, symbol_info); in rte_dump_stack() 60 ret = SymGetLineFromAddr64(process, address, &lin_disp, &line); in rte_dump_stack() 77 ret = SymCleanup(process); in rte_dump_stack()
|
| /f-stack/dpdk/lib/librte_ipsec/ |
| H A D | sa.c | 627 pf->process = esp_inb_tun_pkt_process; in lksd_none_pkt_func_select() 631 pf->process = esp_inb_trs_pkt_process; in lksd_none_pkt_func_select() 636 pf->process = (sa->sqh_len != 0) ? in lksd_none_pkt_func_select() 641 pf->process = (sa->sqh_len != 0) ? in lksd_none_pkt_func_select() 665 pf->process = esp_inb_tun_pkt_process; in cpu_crypto_pkt_func_select() 669 pf->process = esp_inb_trs_pkt_process; in cpu_crypto_pkt_func_select() 674 pf->process = (sa->sqh_len != 0) ? in cpu_crypto_pkt_func_select() 679 pf->process = (sa->sqh_len != 0) ? in cpu_crypto_pkt_func_select() 706 pf->process = inline_inb_tun_pkt_process; in inline_crypto_pkt_func_select() 748 pf->process = pkt_flag_process; in ipsec_sa_pkt_func_select() [all …]
|
| H A D | rte_ipsec.h | 45 uint16_t (*process)(const struct rte_ipsec_session *ss, member 158 return ss->pkt_func.process(ss, mb, num); in rte_ipsec_pkt_process()
|
| /f-stack/doc/ |
| H A D | F-Stack_Nginx_APP_Guide.md | 19 +----------------+ master process +---------------+ 37 woker process cycle woker process cycle 43 - a major addition to the worker process is fstack-handling:ff_init();ff_run(worker_process_cycle);… 73 the `reload` is not graceful, service will still be unavailable during the process of reloading.
|
| /f-stack/dpdk/doc/guides/howto/ |
| H A D | packet_capture_framework.rst | 22 disable packet capture. The library works on a multi process communication model and its 26 ``librte_pdump`` library. It runs as a DPDK secondary process and is capable 31 The application which initializes the packet capture framework will be a primary process 33 be a secondary process. The primary process sends the Rx and Tx packets from the DPDK ports 34 to the secondary process.
|
| /f-stack/app/nginx-1.16.1/src/os/unix/ |
| H A D | ngx_process.c | 474 char *process; in ngx_process_get_status() local 522 process = "unknown process"; in ngx_process_get_status() 528 process = ngx_processes[i].name; in ngx_process_get_status() 537 process, pid, WTERMSIG(status), in ngx_process_get_status() 542 process, pid, WTERMSIG(status)); in ngx_process_get_status() 548 process, pid, WEXITSTATUS(status)); in ngx_process_get_status() 555 process, pid, WEXITSTATUS(status)); in ngx_process_get_status()
|
| /f-stack/dpdk/buildtools/ |
| H A D | call-sphinx-build.py | 32 process = run(sphinx_cmd + ['-b', 'html', src, join(dst, 'html')], variable 39 sys.exit(process.returncode)
|
| /f-stack/app/redis-5.0.5/utils/ |
| H A D | redis_init_script.tpl | 6 echo "$PIDFILE exists, process is already running or crashed" 15 echo "$PIDFILE does not exist, process is not running"
|
| /f-stack/dpdk/doc/guides/tools/ |
| H A D | pdump.rst | 10 a DPDK secondary process and is capable of enabling packet capture on dpdk ports. 26 * The ``dpdk-pdump`` tool runs as a DPDK secondary process. It exits when 75 …in the primary process due to a bug in the ethdev library. Due to this bug, in a multi process con… 76 when the primary and secondary have different ports set, then the secondary process 77 …(here the ``dpdk-pdump`` tool) overwrites the ``rte_eth_devices[]`` entries of the primary process.
|
| /f-stack/dpdk/lib/librte_graph/ |
| H A D | node.c | 72 if (reg == NULL || reg->process == NULL) { in __rte_node_register() 94 node->process = reg->process; in __rte_node_register() 170 reg->process = node->process; in node_clone()
|
| /f-stack/freebsd/contrib/device-tree/Bindings/cpufreq/ |
| H A D | nvidia,tegra20-cpufreq.txt | 13 1. CPU process ID mask 17 1. CPU process ID mask
|
| /f-stack/freebsd/contrib/openzfs/ |
| H A D | NOTICE | 9 process disclosed, or represents that its use would not infringe privately owned 10 rights. Reference herein to any specific commercial product, process, or service
|
| /f-stack/dpdk/app/test-bbdev/ |
| H A D | test-bbdev.py | 14 def kill(process): argument 16 process.kill()
|
| /f-stack/dpdk/doc/guides/contributing/ |
| H A D | vulnerability.rst | 11 are in the scope of this security process (including experimental APIs). 46 as part of the security process. 51 as that can speed up the process considerably. 60 the reporting process must be followed anyway, as described below. 70 Area experts not members of the security team may be involved in the process. 90 using the standard patch process, once a CVE number has been assigned. 166 as described below. It must not be considered as the standard process. 199 OSS-security process <https://oss-security.openwall.org/wiki/mailing-lists/distros>` 318 * `A minimal security response process
|
| /f-stack/freebsd/contrib/libsodium/msvc-scripts/ |
| H A D | Makefile.am | 2 process.bat \
|
| /f-stack/dpdk/app/test/ |
| H A D | test_graph.c | 74 rte_node_process_t process; member 93 .process = test_node0_worker, 104 .process = test_node1_worker, 113 .process = test_node2_worker, 122 .process = test_node3_worker, 141 .process = test_node_worker_source, 151 .process = test_node0_worker,
|
| /f-stack/app/nginx-1.16.1/ |
| H A D | CHANGES | 16 *) Bugfix: a segmentation fault might occur in a worker process if 118 *) Bugfix: a segmentation fault might occur in a worker process when 337 process with PID different from 1 after its parent process has 1053 a worker process, or might have potential other impact 1718 process while handling a specially crafted request by 3282 signals to a process run in other session. 3491 occur in a worker process; the bug had appeared in 0.8.33. 5451 *) Bugfix: a segmentation fault occurred in worker process if 5711 to the master process identification number. 7265 handled by one process; the bug had appeared in 0.3.3. [all …]
|