Summary:	ASTERISK-25842: Move from linked lists to another type
Reporter:	Badalian Vyacheslav (slavon)	Labels:
Date Opened:	2016-03-13 07:06:36	Date Closed:	2016-03-13 13:45:11
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Core/General
Versions:	13.7.2	Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Hello dev. I vote on the care of using a linked list. You must use the combined aligned memory area for storing the list so that you can use vectorization and avx, avx2, avx256 optimizations. For example smaller lists may be held without locks in a single pass. Ie the operation will be the Atomic. A linked list does not allow vectorization and search all the elements by design. I propose, in order not to alter ABI add an array-reference to the head and SIMD to use it as an assistant. I can implement the option, but to be honest a little on a clean gcc is not convenient. That the command asterisk thinks of OpenMP to work with SIMD? i think we may use some like this {code} # aligned 8 struct head { struct * before: struct[512] ptr_array; struct * after: } {code} use 512 is optimal for avx2 multicore, in futere we may change it to 1024 pointers in struct
Comments:	By: Asterisk Team (asteriskteam) 2016-03-13 07:06:37.581-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Joshua C. Colp (jcolp) 2016-03-13 13:45:12.017-0500 Before opening an issue on the issue tracker this type of thing should be discussed on the asterisk-dev mailing list as it has far reaching consequences and should be discussed first.