Observation:
Following example #2 in /example_zc/README.examples:
The interface name is passed in as "zc:eth2" to start the Balancer.
example:
# ./zbalance_ipc -i zc:eth2 -c 99 -n 2 -m 0 -g 1
In this case the max_packet_len(devices[0]) function call, passed into
pfring_zc_create_cluster() always returns 2048; no matter what the actual
MTU value is as set by ifconfig on eth2. Although balance_ipc still works
it is limited to a 2048 Byte packet on the receive; where a 5000 Byte
inbound packet is received as three packets.
Removing 'zc:' from "zc:eth2" in the interface name
allows max_packet_len(devices[0]) to return the correct MTU value; as set
by ifconfig. In this case zbalance_ipc still works BUT with the correct
MTU. Now inbound Jumbo packets work; a 5000 byte inbound packet is received
as a single packet.
example:
#./zbalance_ipc -i eth2 -c 99 -n 2 -m 0 -g 1
Explanation?
Following example #2 in /example_zc/README.examples:
The interface name is passed in as "zc:eth2" to start the Balancer.
example:
# ./zbalance_ipc -i zc:eth2 -c 99 -n 2 -m 0 -g 1
In this case the max_packet_len(devices[0]) function call, passed into
pfring_zc_create_cluster() always returns 2048; no matter what the actual
MTU value is as set by ifconfig on eth2. Although balance_ipc still works
it is limited to a 2048 Byte packet on the receive; where a 5000 Byte
inbound packet is received as three packets.
Removing 'zc:' from "zc:eth2" in the interface name
allows max_packet_len(devices[0]) to return the correct MTU value; as set
by ifconfig. In this case zbalance_ipc still works BUT with the correct
MTU. Now inbound Jumbo packets work; a 5000 byte inbound packet is received
as a single packet.
example:
#./zbalance_ipc -i eth2 -c 99 -n 2 -m 0 -g 1
Explanation?
