On Tue, Mar 31, 2015 at 05:28:11PM +0200, Tobias Klauser wrote:
> On 2015-03-31 at 11:29:58 +0200, Vadim Kochan wrote:
> > From: Vadim Kochan
> >
> > Trafgen uses all the online cpus even if number of packets specified
> > by -n is less than numbers of selected cpus.
> > Such behaviour leads to
On 2015-03-31 at 11:29:58 +0200, Vadim Kochan wrote:
> From: Vadim Kochan
>
> Trafgen uses all the online cpus even if number of packets specified
> by -n is less than numbers of selected cpus.
> Such behaviour leads to issues:
>
> - trafgen re-calculates number of packets per cpu which
>
Overall looks like this configuration has no problem writing over 6
Gbit/sec and can jump to 8-10 Gbit/sec with a minor packet loss. Now
remember it's just a 2.0Ghz.
Enabled RPS by doing
cd /sys/class/net/eth2/queues/rx-0
echo 8 > rps_cpus
So that packets are ACK'ed on core 1, processed on core
Sorry for the delay, I wanted to get the week started so I can return
to a production level of traffic :-)
On average, I can see between 4 - 5 Gbit/sec and netsniff does not
report any loss in the log now. There is around 3% loss in the NIC
statistics, visible in both ifpps and ifconfig.
>
> Than
From: Vadim Kochan
Trafgen uses all the online cpus even if number of packets specified
by -n is less than numbers of selected cpus.
Such behaviour leads to issues:
- trafgen re-calculates number of packets per cpu which
leads to rounding it to 0 then no packets will be sent.
- tr
