packet (reference) in projects: f-stack

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

Searched refs:packet (Results 1 – 25 of 318) sorted by relevance

12 3 4 5 6 7 8 9 10 >>...13

/f-stack/dpdk/doc/guides/prog_guide/
H A D	pdump_lib.rst	9 The ``librte_pdump`` library provides a framework for packet capturing in DPDK. 15 between primary and secondary process for enabling/disabling packet capture on 18 The library provides the following APIs to initialize the packet capture framework, to enable 19 or disable the packet capture, and to uninitialize it. 22 This API initializes the packet capture framework. 25 This API enables the packet capture on a given port and queue. 33 This API disables the packet capture on a given port and queue. 39 This API uninitializes the packet capture framework. 45 The primary process using ``librte_pdump`` is responsible for initializing the packet 55 to enable or disable the packet capture over the multi process channel. [all …]
H A D	ip_fragment_reassembly_lib.rst	12 Packet fragmentation routines divide input packet into number of fragments. 14 points to the start of the IP header of the packet (i.e. L2 header is already stripped out). 15 To avoid copying of the actual packet's data zero-copy technique is used (rte_pktmbuf_attach). 20 * Indirect mbuf -- mbuf that is attached to the mbuf with the original packet. 38 Fragment table maintains information about already received fragments of the packet. 73 Functions. They either return a pointer to valid mbuf that contains reassembled packet, 74 or NULL (if the packet can't be reassembled for some reason). 89 #. Update the entry with new fragment information and check if a packet can be reassembled 90 (the packet's entry contains all fragments). 96 If at any stage of packet processing an error is encountered [all …]
H A D	traffic_metering_and_policing.rst	44 Traffic metering determines the color for the current packet (green, yellow, 46 object. The policer can do nothing, override the color the packet or drop the 47 packet. Statistics counters are maintained for MTR object, as configured. 49 The processing done for each input packet hitting an MTR object is: 51 * Traffic metering: The packet is assigned a color (the meter output color) 55 case the input packet already has an initial color (the input color), or in 62 * Drop the packet. 64 * Keep the same packet color: the policer output color matches the meter 67 * Recolor the packet: the policer output color is set to a different color 69 of the packet, which is set in the packet meta-data (i.e. struct
H A D	packet_distrib_lib.rst	8 while supporting single packet at a time operation. 19 one which sends one packet at a time to workers using 32-bits for flow_id, 35 …As it does so, it examines the "tag" -- stored in the RSS hash field in the mbuf -- for each packet 38 #. If the next packet in the input set has a tag which is already being processed by a worker, 39 then that packet will be queued up for processing by that worker 64 …e a worker lcore requests a new packet, the distributor assumes that it has completely finished wi… 69 No packet ordering guarantees are made about packets which do not share a common packet tag. 72 while allowing packet order within a packet flow -- identified by a tag -- to be maintained. 87 …re the cores which do the actual manipulation of the packets distributed by the packet distributor. 88 Each worker calls "rte_distributor_get_pkt()" API to request a new packet when it has finished proc… [all …]
H A D	rte_security.rst	50 crypto processing the packet is presented to host as a regular Rx packet 52 packet. e.g. In case of IPsec, the IPsec tunnel headers (if any), 53 ESP/AH headers will remain in the packet but the received packet 69 packet out. 121 crypto processing the packet is presented to the host as a regular Rx packet 124 ESP/AH headers will be removed from the packet and the received packet 130 done on the packet. 146 the packet out. The software should make sure that the buffer 205 will be removed from the packet and the decrypted packet may contain 568 security session which processed the packet. [all …]
H A D	generic_receive_offload_lib.rst	8 technique to reduce per-packet processing overheads. By reassembling 19 In the GRO library, there are many GRO types which are defined by packet 35 inner TCP/IPv4 or UDP/IPv4 packet. 99 GRO fails to merge packets when encounters packet reordering. 105 - capable of handling packet reordering 124 by packet reordering. 146 keeps packet information. 200 input packet, rather than parsing the packet header. Therefore, 204 packet. 209 - GRO library just supports to process the packet organized [all …]
H A D	generic_segmentation_offload_lib.rst	10 TCP Segmentation Offload (TSO), which reduces per-packet processing overhead. 14 reducing per-packet overhead. 44 #. Currently, the GSO library supports the following IPv4 packet types: 90 original packet. 106 - the input packet on which GSO is to be performed is represented by a 112 The GSO library traverses each segment of the input packet, and produces 174 To segment an outgoing packet, an application must: 179 used to store the GSO segments' packet headers. 182 used to locate GSO segments' packet payloads. 220 #. Check if the packet should be processed. Packets with one of the [all …]
H A D	qos_framework.rst	388 The sequence of steps per packet: 425 packet priority in order to yield the enqueue/drop decision for a specific packet 441 #. Read the packet length from the packet descriptor (mbuf structure). 485 where n is the packet length in bytes and h is the number of framing overhead bytes per packet. 502 Whenever a packet is scheduled, the NIC time is incremented with the packet length (including frami… 625 …\| \| \| bucket to send the full packet (packet bytes and framing overhead f… 719 …\| \| (on packet scheduling) \| from the bucket. The packet can only be sent if enough credits are… 720 …\| \| \| bucket to send the full packet (packet bytes and framing overhead … 1426 * Calculates a packet drop probability 1436 since the last packet was dropped. [all …]
H A D	mbuf_lib.rst	13 A rte_mbuf struct generally carries network packet buffers, but it can actually 37 where multiple buffers are required to hold the complete packet. 121 For instance, this is the case on RX side for the IEEE1588 packet 130 a vxlan-encapsulated tcp packet: 138 set out_ip checksum to 0 in the packet 147 set out_ip checksum to 0 in the packet 158 set in_ip checksum to 0 in the packet 169 set in_ip checksum to 0 in the packet 184 set in_ip checksum to 0 in the packet 199 set out_ip checksum to 0 in the packet [all …]
H A D	packet_framework.rst	28 For each incoming packet, the table defines the set of actions to be applied to the packet, 29 as well as the next stage to send the packet to. 39 provides the set of actions to be applied on the current packet, 40 as well as the next hop for the packet, which can be either another table, an output port or packet… 246 …\| \| \| For each lookup miss packet, the actions to be applied on the packet and a… 452 …irst CPU core (typically the CPU core that performs packet RX) extracts the key from the input pac… 453 …ey signature and saves both the key and the key signature in the packet buffer as packet meta-data. 1012 The action handler can decide to drop the input packet. 1188 …cket headers: Each packet typically has one or multiple headers. The headers are extracted from th… 1196 …explicitly written into the headers emitted into the output packet. The format of the packet meta-… [all …]
/f-stack/dpdk/doc/guides/sample_app_ug/
H A D	ip_reassembly.rst	7 The L3 Forwarding application is a simple example of packet processing using the DPDK. 18 The maximum allowed size of reassembled packet is 9.5 KB. 55 * --flowttl=TTL[(s\|ms)]: determines maximum Time To Live for fragmented packet. 56 If all fragments of the packet wouldn't appear within given time-out, 103 fragment extension header are present in the packet. 195 For each input packet, the packet forwarding operation is done by the l3fwd_simple_forward() functi… 199 or NULL (if the packet can't be reassembled for some reason). 201 (that is, the identification of the output interface for the packet) and 202 actual transmit of the packet. 219 if a packet can be reassembled (the packet's entry contains all fragments). [all …]
H A D	ipv4_multicast.rst	7 The IPv4 Multicast application is a simple example of packet processing 37 it looks only at the IPv4 destination address for any given packet. 147 /* Remove the Ethernet header from the input packet / 205 / Prepare output packet and send it out. / 234 / Put new packet into the output queue / 260 allocates a new buffer for the packet header and prepends it to the input packet. 262 Basically, the first approach reuses only the input packet's data, but creates its own copy of pack… 266 so we can safely modify the data pointer of the input packet. 268 and instead modify input packet's header in place. 301 / If requested, then make a new clone packet. */ [all …]
H A D	ip_frag.rst	7 The IPv4 Fragmentation application is a simple example of packet processing 9 The application does L3 forwarding with IPv4 and IPv6 packet fragmentation. 14 The application demonstrates the use of zero-copy buffers for packet fragmentation. 23 based on information read from the input packet's IP header. 33 Before forwarding, the input IP packet is fragmented to fit into the "standard" Ethernet* v2 MTU (1… 47 For each input packet, the packet forwarding decision 48 (that is, the identification of the output interface for the packet) is taken as a result of LPM lo… 49 If the IP packet size is greater than default output MTU, 50 then the input packet is fragmented and several fragments are sent via the output interface. 132 For example, for the input IPv4 packet with destination address: 100.10.1.1 and packet length 9198 … [all …]
H A D	l3_forward.rst	7 The L3 Forwarding application is a simple example of packet processing using 8 DPDK to demonstrate usage of poll and event mode packet I/O mechanism. 15 to implement packet forwarding using poll or event mode PMDs for packet I/O. 20 decision is made based on information read from the input packet. 23 implementation for packet I/O based on run time parameters. 95 …`` Optional, set to use software to analyze packet type. Without this option, hardware will check … 155 * The --mode option defines PMD to be used for packet I/O. 296 For each input packet, the packet forwarding operation is done by the l3fwd_simple_forward() 300 and the packet forwarding decision (that is, the identification of the output interface for the pac… 369 For each input packet, the packet forwarding operation is done by the l3fwd_simple_forward() functi… [all …]
H A D	qos_metering.rst	17 changing the color of the packet in a static manner depending on both the input and output colors o… 74 To simplify debugging (for example, by using the traffic generator RX side MAC address based packet… 93 … generated at line rate and all packets are 64 bytes Ethernet frames (IPv4 packet size of 46 bytes) 137 * GREEN: The packet's color is changed to green. 139 * YELLOW: The packet's color is changed to yellow. 141 * RED: The packet's color is changed to red. 143 * DROP: The packet is dropped. 147 * Every packet which input and output color are the same, keeps the same color. 149 * Every packet which color has improved is dropped (this particular case can't happen, so these v… 155 * To drop the packet, policer_table action has to be set to DROP.
H A D	intro.rst	36 enabled cores. This application doesn't do any packet forwarding but it is a 41 basic packet forwarding with DPDK. This allows you to test if your network 61 * :doc:`Hardware packet copying<ioat>`: The Hardware packet copying, 74 callbacks sample application is a packet forwarding application that 76 packets. The application calculates the latency of a packet between RX 77 (packet arrival) and TX (packet transmission) by adding callbacks to the RX 78 and TX packet processing functions.
/f-stack/dpdk/doc/guides/howto/
H A D	packet_capture_framework.rst	12 The DPDK packet capture framework was introduced in DPDK v16.07. The DPDK 13 packet capture framework consists of the DPDK pdump library and DPDK pdump 21 allow users to initialize the packet capture framework and to enable or 27 of enabling or disabling packet capture on DPDK ports. The ``dpdk-pdump`` tool 29 disabling of the packet capture on DPDK ports. 32 and the application that enables or disables the packet capture will 36 In DPDK the ``testpmd`` application can be used to initialize the packet 47 application which has the packet capture framework initialized already. In 48 dpdk, only ``testpmd`` is modified to initialize packet capture framework, 51 explicitly modify that application to call the packet capture framework [all …]
H A D	rte_flow.rst	52 /* set the dst ipv4 packet to the required value / 87 received packet with src ip = 176.80.50.4 88 received packet with src ip = 176.80.50.5 106 received packet with src ip = 176.80.50.4 148 / set the dst ipv4 packet to the required value */ 187 received packet with src ip = 176.80.50.4 188 received packet with src ip = 176.80.50.5 189 received packet with src ip = 176.80.50.6 209 received packet with src ip = 176.80.50.6 281 received packet with src ip = 176.80.50.4 sent to queue 2 [all …]
/f-stack/dpdk/examples/pipeline/examples/
H A D	l2fwd_pcap.cli	`8 pipeline PIPELINE0 port in 0 source MEMPOOL0 ./examples/packet.pcap 9 pipeline PIPELINE0 port in 1 source MEMPOOL0 ./examples/packet.pcap 10 pipeline PIPELINE0 port in 2 source MEMPOOL0 ./examples/packet.pcap 11 pipeline PIPELINE0 port in 3 source MEMPOOL0 ./examples/packet.pcap`
H A D	l2fwd_macswp_pcap.cli	`8 pipeline PIPELINE0 port in 0 source MEMPOOL0 ./examples/packet.pcap 9 pipeline PIPELINE0 port in 1 source MEMPOOL0 ./examples/packet.pcap 10 pipeline PIPELINE0 port in 2 source MEMPOOL0 ./examples/packet.pcap 11 pipeline PIPELINE0 port in 3 source MEMPOOL0 ./examples/packet.pcap`
H A D	vxlan_pcap.cli	`8 pipeline PIPELINE0 port in 0 source MEMPOOL0 ./examples/packet.pcap 9 pipeline PIPELINE0 port in 1 source MEMPOOL0 ./examples/packet.pcap 10 pipeline PIPELINE0 port in 2 source MEMPOOL0 ./examples/packet.pcap 11 pipeline PIPELINE0 port in 3 source MEMPOOL0 ./examples/packet.pcap`
/f-stack/freebsd/contrib/octeon-sdk/
H A D	cvmx-debug.c	439 cvmx_debug_strcpy(packet, tmp); in cvmx_debug_putcorepacket() 443 packet[6] = ' '; in cvmx_debug_putcorepacket() 444 packet[7] = core + '0'; in cvmx_debug_putcorepacket() 448 packet[6] = '1'; in cvmx_debug_putcorepacket() 449 packet[7] = core - 10 + '0'; in cvmx_debug_putcorepacket() 453 packet[6] = '2'; in cvmx_debug_putcorepacket() 454 packet[7] = core - 20 + '0'; in cvmx_debug_putcorepacket() 458 packet[6] = '3'; in cvmx_debug_putcorepacket() 459 packet[7] = core - 30 + '0'; in cvmx_debug_putcorepacket() 469 cvmx_debug_strcpy(packet, buf); in cvmx_debug_putpacket_hexint() [all …]
H A D	cvmx-pko.h	376 cvmx_buf_ptr_t packet, cvmx_pko_lock_t use_locking) in cvmx_pko_send_packet_finish() argument 384 packet.u64); in cvmx_pko_send_packet_finish() 424 … cvmx_buf_ptr_t packet, uint64_t addr, cvmx_pko_lock_t use_locking) in cvmx_pko_send_packet_finish3() argument 432 packet.u64, in cvmx_pko_send_packet_finish3() 765 cvmx_buf_ptr_t packet, cvmx_pko_lock_t use_locking) in cvmx_pko_send_packet_finish_pkoid() argument 773 packet.u64); in cvmx_pko_send_packet_finish_pkoid() 807 … cvmx_buf_ptr_t packet, uint64_t addr, cvmx_pko_lock_t use_locking) in cvmx_pko_send_packet_finish3_pkoid() argument 815 packet.u64, in cvmx_pko_send_packet_finish3_pkoid()
/f-stack/dpdk/doc/guides/nics/
H A D	vmxnet3.rst	30 The VMXNET3 PMD handles all the packet buffer memory allocation and resides in guest address space 32 The packet buffers and features to be supported are made available to hypervisor via VMXNET3 PCI co… 33 During RX/TX, the packet buffers are exchanged by their GPAs, 38 The driver pre-allocates the packet buffers and loads the command ring descriptors in advance. 39 The hypervisor fills those packet buffers on packet arrival and write completion ring descriptors, 41 After reception, the DPDK application frees the descriptors and loads new packet buffers for the co… 45 In the transmit routine, the DPDK application fills packet buffer pointers in the descriptors of th… 53 In release 1.6.0, the VMXNET3 PMD provides the basic functionality of packet reception and transmis… 75 Only cmd_ring_0 is used for packet buffers, one for each descriptor. 125 The packet reception and transmission flow path is:: [all …]
H A D	igc.rst	41 - The VLAN header in a packet that carries a single VLAN header is treated as the external VLAN. 43 - Foxville expects that any transmitted packet to have at least the external VLAN added by the 47 - If VLAN TX-OFFLOAD is enabled and the packet does not contain an external VLAN, the packet is 48 dropped, and if configured, the queue from which the packet was sent is disabled. 84 Add a rule to direct packet whose ``ether-type=0x801`` to queue 1: 90 Add a rule to direct packet whose ``ip-protocol=0x6(TCP), tcp_port=0x80`` to queue 1: 96 Add a rule to direct packet whose ``ip-protocol=0x6(TCP), SYN flag is set`` to queue 1:

12 3 4 5 6 7 8 9 10 >>...13

TaskScheduler
dpdk
expo
f-stack
freebsd-12.1
freebsd-13.1
freebsd-14.2
iperf
leveldb-1.20
libedit-20250104-3.1
libev
libevent-2.1.12
libpciaccess
libtiff-4.0.7
lighttpd1.4
linux-6.15
llvm-project-15.0.7
mOS-networking-stack
memcached-1.4.29
memcached-1.6.32
oneTBB
pciutils
potrace-1.14
redis-3.2.3
rocksdb-6.9
rust-libc-0.2.174
sqlite-3.40.0
tonic
vim-8.2.3635
webrtc
xiu
xnu-11215