X-Git-Url: http://git.droids-corp.org/?a=blobdiff_plain;f=doc%2Fguides%2Fsample_app_ug%2Fipv4_multicast.rst;h=5e270411d3fb516e549f9c20c2ac2e09973f9220;hb=3006df511e6346d2e7d6e9ddf909283d41d2ae8a;hp=a9c9df81b924aca0b1dde04fa1bb048b68fb0b3e;hpb=d0dff9ba445e47199a420dd4b5451ec2860d3d3b;p=dpdk.git diff --git a/doc/guides/sample_app_ug/ipv4_multicast.rst b/doc/guides/sample_app_ug/ipv4_multicast.rst index a9c9df81b9..5e270411d3 100644 --- a/doc/guides/sample_app_ug/ipv4_multicast.rst +++ b/doc/guides/sample_app_ug/ipv4_multicast.rst @@ -32,7 +32,7 @@ IPv4 Multicast Sample Application ================================= The IPv4 Multicast application is a simple example of packet processing -using the Intel® Data Plane Development Kit (Intel® DPDK). +using the Data Plane Development Kit (DPDK). The application performs L3 multicasting. Overview @@ -76,7 +76,7 @@ To compile the application: export RTE_TARGET=x86_64-native-linuxapp-gcc -See the *Intel® DPDK Getting Started Guide* for possible RTE_TARGET values. +See the *DPDK Getting Started Guide* for possible RTE_TARGET values. #. Build the application: @@ -126,7 +126,7 @@ In this command: * The -q option assigns 1 queue to each lcore -Refer to the *Intel® DPDK Getting Started Guide* for general information on running applications +Refer to the *DPDK Getting Started Guide* for general information on running applications and the Environment Abstraction Layer (EAL) options. Explanation @@ -232,12 +232,12 @@ Thereafter, a destination Ethernet address is constructed: .. code-block:: c - /* construct destination ethernet address */ + /* construct destination Ethernet address */ dst_eth_addr = ETHER_ADDR_FOR_IPV4_MCAST(dest_addr); Since Ethernet addresses are also part of the multicast process, each outgoing packet carries the same destination Ethernet address. -The destination Ethernet address is constructed from the lower 23 bits of the multicast group ORed +The destination Ethernet address is constructed from the lower 23 bits of the multicast group OR-ed with the Ethernet address 01:00:5e:00:00:00, as per RFC 1112: .. code-block:: c