The problem in issue #2220 occurs because
count of max concurrent streams in test
exceeded a lot of times and Tempesta FW prints
warning on each event. printk can hungs for
a long time in console_unlock (more then 20s
!), moreover Tempesta FW hold socket lock all
this time. To solve this problem we change T_WARN
to T_DBG for this event to not print this message
for not debug build and also we impement new procfs stat (streams_reset) - count of streams which were reset by any reason. It can be useful to check why new requests dropped.
The problem in issue #2220 occurs because count of max concurrent streams in test exceeded a lot of times and Tempesta FW prints warning on each event.
printk
can hungs for a long time inconsole_unlock
(more then 20s !), moreover Tempesta FW hold socket lock all this time. To solve this problem we change T_WARN to T_DBG for this event to not print this message for not debug build and also we impement new procfs stat (streams_reset) - count of streams which were reset by any reason. It can be useful to check why new requests dropped.Closes #2220