nic_router: change max_packets_per_signal default

According to a benchmarking series on Zynq (base-hw) and x260 (base-nova) using
test-nic_perf_router, increasing the 'max_packets_per_signal' has a significant
effect on the packet throughput. By increasing the default value from 32
to 150, we could gain a few hundred Mbit/s. Increasing the value further
does not seem to have such a strong effect, though.

genodelabs/genode#4555
This commit is contained in:
Johannes Schlatow 2022-07-20 10:27:19 +02:00 committed by Christian Helmuth
parent a2b74af59a
commit e2086ac8e4
2 changed files with 2 additions and 2 deletions

View File

@ -793,7 +793,7 @@ this can lead to starvation of the other interfaces. Thus, the maximum number
of packets handled per signal is limited by default. This limit can be
configured as follows (default value shown):
! <config max_packets_per_signal="32">
! <config max_packets_per_signal="150">
When set to zero, the limit is deactivated, meaning that the router always
handles all available packets of an interface.

View File

@ -111,7 +111,7 @@ Configuration::Configuration(Env &env,
Interface_list &interfaces)
:
_alloc { alloc },
_max_packets_per_signal { node.attribute_value("max_packets_per_signal", (unsigned long)32) },
_max_packets_per_signal { node.attribute_value("max_packets_per_signal", (unsigned long)150) },
_verbose { node.attribute_value("verbose", false) },
_verbose_packets { node.attribute_value("verbose_packets", false) },
_verbose_packet_drop { node.attribute_value("verbose_packet_drop", false) },