void __4_4_13_3__Rate_Limiting() {
    /**
     * @group:       	4.4.13.3 Rate Limiting
     *
     * @description:	The device supports independent ingress and egress hardware rate limiting on each port. Normally these two features
     * 					are considered mutually exclusive, and users are discouraged from using both on the same port.
     * 					For 10BASE-Te, a rate setting above 10Mbps means the rate is not limited. Likewise, for 100BASE-TX, a rate setting
     * 					above 100Mbps means the rate is not limited. On the receive side, the data receive rate for each priority at each port
     * 					can be limited by setting up ingress rate control registers. On the transmit side, the data transmit rate for each priority
     * 					queue at each port can be limited by setting up egress rate control registers. The size of each frame has options to
     * 					include minimum inter-frame gap (IFG) or preamble byte, in addition to the data field (from packet DA to FCS).
     * 					For ingress rate limiting, the device provides options to selectively choose frames from all types, multicast, broadcast,
     * 					and flooded unicast frames. The data rate from those selected type of frames is counted. Packets are dropped at the
     * 					ingress port when the data rate exceeds the specified rate limit.
     * 					For egress rate limiting, the leaky bucket algorithm is applied to each output priority queue for shaping output traffic.
     * 					Inter-frame gap is stretched on a per frame base to generate smooth, non-burst egress traffic. The throughput of each
     * 					output priority queue is limited by the egress rate specified.
     * 					If any egress queue receives more traffic than the specified egress rate throughput, packets may be accumulated in the
     * 					output queue and packet memory. After the memory of the queue or the port is used up, packet dropping or flow control
     * 					will be triggered. As a result of congestion, the actual egress rate may be dominated by flow control/dropping at the
     * 					ingress end, and may be therefore slightly less than the specified egress rate.
     * 					To reduce congestion, it is a good practice to ensure that the egress bandwidth exceeds the ingress bandwidth.
     *
     */
}