Actions
Bug #1547
closedUnable to distinguish interface according to thread name
Status:
Closed
Priority:
Normal
Assignee:
-
Target version:
-
Affected Versions:
Effort:
Difficulty:
Label:
Description
In our use case we are trying to store statistics about each thread and interface.
Here is a hypothetical scenario. Lets have devices eth1 and eth11 and create more then 11 threads for each device. There could be thread name "RxAFPeth111" which could belong to 1st thread of eth11 or 11th thread of eth1. In OutputStats function is just thread name and we are not able to distinguish source of statistics.
I suggest to add "#" as separator into thread name. See attached patch.
Files
Updated by Jozef Mlich about 9 years ago
It seems this issue is addressed in ticket #1524. Feel free to close this ticket as a duplicate. I am not able to do this.
Updated by Peter Manev about 9 years ago
- Status changed from New to Closed
Closed duplicate as requested.
Actions