-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Florian,
the generic implementation serves 2 purposes, at least in my opinion. Firstly, in case the necessary hardware extension is not available on the target hardware, there is a backup default. Secondly, the generic implementation is usually easier to read and thus preferable as a reference. I know that this is a 'the code is the documentation' argument. But even though documentation might be really good, sometimes looking at the code just makes things clearer. happy hacking Johannes On 11.03.2014 23:08, Florian Kaltenberger wrote: > Hi Nathan and Abhishek, > > On 10/03/2014 23:22, West, Nathan wrote: >> Ah! So there was a slight miscommunication. Yes, porting the >> OpenAirInterfaces SIMD code to VOLK is a good option as well. The >> turbo channel coder/decoder is part of that. I've *briefly* >> looked at the code to see what is currently there, and it's my >> understanding that the work involved will be to write generic C >> implementations of vectorized code where the generic version does >> not exist. Beyond that porting to newer/different ISAs (AVX or >> NEON depending on your preference and hardware availability). I >> think Florian is on the gr-discuss mailing list, but I've CCed >> him to hopefully provide more details as he's more familiar with >> the original code base. > I only joined this mailing list recently, so I probably missed a > part of the discussion. Let me summarize briefly what > OpenAirInterface can provide. We have optimized SIMD (SSE4) > implementations of the LTE turbo encoder and decoder as well as the > LTE tail-biting Viterbi encoder and decoder. We also have the > 802.11 Viterbi encoder and decoder. The only functions for which we > have generic non-vectorized functional equivalents is the LTE turbo > decoder. I am not sure I understand why it is necessary to write > generic versions for the already optimized SIMD code. My idea was > to port the optimized SIMD code from OpenAirInterface to VOLK, such > that is can be used by GR applications. I am not familiar with VOLK > (yet) but this might just be as easy as writing a wrapper > function. As Nathan suggested, the more interesting part is > probably to upgrade the code to AVX2 or similar. > > Cheers, Florian. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJTH56MAAoJEO7fmkDsqywMb+AP/jNXrJoV7Cs6wY7Cx9AHkllM NEo1mxxBhaALsxWv9xwTImaGpA83guiBZ8o0CufYj65oN/i1mN8dUHgK9D/SlLSn GhWTZSBlBiVvIUtxFskDaAA0sqg/2Ae+iYoDKm0yxJerU49K5YGrTBFhzgl7i/r5 fZz+BIGPm29rP1kHyRfw/ROmonXOlz1z+jIR7PGK7DEQbw/Uy9eITchVVKMNsdjm X73+vJHF9UXftzbpwEF/CsgwWVnTvWEVy3YjvxaKRMET/2zQWtEJst51l+aVWFLp M4ejRtf4zmuSBx5JUMf0/eY1lnNWUkqdlcEaLkddalDwl5chkkfxtS+Gwd6YEqJH pdqIa7BfHMaPwrKJ/bX3Wp9u9czWcwI9c8A9GjxnFrASIy2g+QLzU21XDdmImFWm iqaOB0p+/y6bK/V91a4ZjL9gtTBRahlmlmB2EIcPsxlnW+PjJZKNPA833BkuqEE8 gU7w9diq5nbEQYhsvxeqz0WX16yZNwJlz98ane8+oZaVNt9JRI0cjuj0JX24EEPT 9wUfPkmnr1325NJISFJx8X7w2mAQV3zrf5Md1wOfI6Ls9Byfp8+WjeRYrTfzC95b kXvcTVID0XZdoTItSjQUEbbJAbl8IkfwWaQCNgHCcJzfZLdJ2hHy7RqpiBAkMmAv QzLU1GZSSHXzEPKUI1fM =INm4 -----END PGP SIGNATURE----- _______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
