| /f-stack/doc/ |
| H A D | F-Stack_Development_Guide.md | 3 …he bottleneck in modern network systems. Yet, the increasing demands of the Internet's growth dema…
5 F-Stack is an open source high performant network framework based on DPDK with the following charac…
7 1. Ultra high network performance which the network card can achieve under full load: 10 million co…
8 …function, and cut a great amount of irrelevant features. This greatly enhances network performance.
39 …network stacks based on DPDK to support the higher level application in the market. Some are will …
41 … and maintain a complete network stack will cost high. So the FreeBSD network stack was ported int…
43 … F-Stack uses a multi-process architecture. Following are the changes to the FreeBSD network stack.
|
| H A D | F-Stack_Nginx_APP_Guide.md | 3 F-Stack is an open source network framework based on DPDK. F-Stack supports standard Nginx as HTTP …
53 Determines whether server should run on kernel network stack or fstack.
61 Determines whether proxy should go through kernel network stack or fstack.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/firmware/ |
| H A D | intel,ixp4xx-network-processing-engine.yaml | 5 $id: "http://devicetree.org/schemas/firmware/intel,ixp4xx-network-processing-engine.yaml#"
25 - const: intel,ixp4xx-network-processing-engine
42 compatible = "intel,ixp4xx-network-processing-engine";
|
| /f-stack/freebsd/contrib/device-tree/src/powerpc/ |
| H A D | mpc885ads.dts | 97 device_type = "network";
105 linux,network-index = <0>;
109 device_type = "network";
117 linux,network-index = <1>;
200 device_type = "network";
209 linux,network-index = <2>;
|
| H A D | mgcoge.dts | 147 device_type = "network";
154 linux,network-index = <0>;
189 device_type = "network";
196 linux,network-index = <1>;
202 device_type = "network";
209 linux,network-index = <2>;
|
| H A D | adder875-uboot.dts | 93 device_type = "network";
101 linux,network-index = <0>;
105 device_type = "network";
113 linux,network-index = <1>;
|
| H A D | adder875-redboot.dts | 94 device_type = "network";
102 linux,network-index = <0>;
106 device_type = "network";
114 linux,network-index = <1>;
|
| H A D | ep8248e.dts | 155 device_type = "network";
163 linux,network-index = <0>;
168 device_type = "network";
176 linux,network-index = <1>;
|
| H A D | tqm8xx.dts | 110 device_type = "network";
117 linux,network-index = <1>;
180 device_type = "network";
187 linux,network-index = <0>;
|
| H A D | mpc866ads.dts | 77 device_type = "network";
85 linux,network-index = <0>;
159 device_type = "network";
167 linux,network-index = <1>;
|
| H A D | ep88xc.dts | 92 device_type = "network";
100 linux,network-index = <0>;
104 device_type = "network";
112 linux,network-index = <1>;
|
| H A D | mpc7448hpc2.dts | 87 linux,network-index = <0>;
89 device_type = "network";
100 linux,network-index = <1>;
103 device_type = "network";
|
| H A D | kmeter1.dts | 316 device_type = "network";
332 device_type = "network";
348 device_type = "network";
364 device_type = "network";
380 device_type = "network";
396 device_type = "network";
412 device_type = "network";
|
| /f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/xattr/ |
| H A D | setup.ksh | 37 svcs svc:/network/nis/client:default | grep online > /dev/null
40 svcadm disable -t svc:/network/nis/client:default
|
| /f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/privilege/ |
| H A D | setup.ksh | 39 svcs svc:/network/nis/client:default | grep online > /dev/null
42 svcadm disable svc:/network/nis/client:default
|
| /f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/delegate/ |
| H A D | setup.ksh | 41 if [[ "ON" == $(svcs -H -o sta svc:/network/nis/client:default) ]]; then
42 log_must svcadm disable -t svc:/network/nis/client:default
|
| /f-stack/ |
| H A D | README.md | 8 …he bottleneck in modern network systems. Yet, the increasing demands of the Internet's growth dema…
10 [F-Stack](http://www.f-stack.org/?from=github) is an open source high performant network framework …
12 1. Ultra high network performance which the network card can achieve under full load: 10 million co…
13 …function, and cut a great amount of irrelevant features. This greatly enhances network performance.
21 …f 2012. We faced several options: one is to continue to use the original network stack in the Linu…
25 …network access performance. Meanwhile, F-Stack was continuing to improve, being driven by our busi…
170 …ck team developed F-Stack which is a general network framework based on DPDK and provides ultra hi…
|
| /f-stack/dpdk/doc/guides/tools/ |
| H A D | devbind.rst | 30 Print the current status of all known network interfaces.
56 WARNING: This can lead to loss of network connection and should be used
72 While any user can run the ``dpdk-devbind.py`` script to view the status of the network ports,
73 binding or unbinding network ports requires root privileges.
95 To check status of all network ports, assign one to the vfio-pci driver and check status again::
|
| /f-stack/dpdk/doc/guides/sample_app_ug/ |
| H A D | multi_process.rst | 156 As the diagram shows, each process reads packets from each of the network ports in use.
172 … This parameter is used to configure the appropriate number of receive queues on each network port.
200 once the hugepage shared memory and the network ports are initialized,
214 In the primary instance, a memory pool is created for the packet mbufs and the network ports to be …
216 The structures for the initialized network ports are stored in shared memory and
231 giving the secondary process access to the hardware and software rings for each network port.
279 Since the server application stores configuration data in shared memory, including the network port…
308 The network ports for use by the processes are obtained by loading the network port drivers and pro…
310 automatically get access to the network ports using the settings already configured by the primary/…
312 Once all applications are initialized, the server operates by reading packets from each network por…
[all …]
|
| /f-stack/dpdk/doc/guides/nics/ |
| H A D | pcap_ring.rst | 71 * rx_iface: Defines a reception stream based on a network interface name.
78 * rx_iface_in: Defines a reception stream based on a network interface name.
85 * tx_iface: Defines a transmission stream based on a network interface name.
91 * iface: Defines a device mapping a network interface.
146 Read packets from a network interface and write them to a pcap file:
154 Read packets from a pcap file and write them to a network interface:
162 Forward packets through two network interfaces:
169 Enable 2 tx queues on a network interface:
177 Read only incoming packets from a network interface and write them back to the same network interfa…
212 The network interface provided to the PMD should be up. The PMD will return
[all …]
|
| H A D | dpaa2.rst | 33 DPAA2 is a hardware architecture designed for high-speed network
44 network ports to create functional objects/devices such as network
79 | -network interface -DPNI |
98 in creating a network interfaces.
163 Ethernet network interface functionality. This approach provides
168 network interface configuration on a system with 2 CPUs.
207 network interface configuration, and RX buffer pool configuration
270 The Ethernet driver configures the DPBPs associated with the network
388 interfaces needed to connect the DPAA2 network interface to
389 the network stack.
[all …]
|
| /f-stack/tools/netstat/ |
| H A D | if.c | 327 bool network = false, link = false; in intpr() local
393 network = true; in intpr()
418 link|network, 1); in intpr()
425 link|network, 0); in intpr()
427 link|network, 1); in intpr()
431 link|network, 0); in intpr()
|
| /f-stack/freebsd/contrib/device-tree/Bindings/devfreq/event/ |
| H A D | exynos-nocp.txt | 7 the network infrastructure to observer units. You can configure probes to
8 capture packets with header or data on the data request response network,
|
| /f-stack/freebsd/contrib/device-tree/Bindings/net/ |
| H A D | calxeda-xgmac.yaml | 11 internal machine "network fabric", which is set up, initialised and
14 traffic to external network ports.
|
| /f-stack/freebsd/contrib/device-tree/Bindings/clock/ |
| H A D | nuvoton,npcm750-clk.txt | 12 network. They are set on the device tree, but not used by the clock module. The
13 network devices use them directly.
40 Example: Required external clocks for network:
|