config: Optimize for speed not size

We don't care that much about binary sizes. What we care much more about is performance.

Example from openssl benchmark on Turris Omnia:

-blowfish cbc     31828.77k    34072.13k    34575.86k    34862.61k    34960.07k    34880.97k
+blowfish cbc     44087.01k    48574.86k    50495.69k    50045.71k    50657.71k    50395.53k

-aes-256 cbc      34569.29k    36977.21k    38553.42k    38331.73k    38312.02k    38460.17k
+aes-256 cbc      37079.18k    40329.57k    41345.76k    41927.39k    41947.61k    41910.39k

changed milestone to %Turris OS 6.3.0

requested review from @jschlehofer

assigned to @jschlehofer

changed the description

assigned to @mvasilek and unassigned @jschlehofer

requested review from @mvasilek and removed review request for @jschlehofer

I do have one question, though. Why this is not done globally even for Turris 1.x routers? Since our requirement was to use at least 8 GB / 16 GB microSD card for booting, we don't care about the size there as well. The problematic part would be (as we managed) to have booting from the internal storage.

Example from OpenSSL benchmark is good, but in the commit description as as well in the merge request, there should be mentioned how much the size differs.

added 21 commits

• 18f20500...a359a298 - 20 commits from branch hbk
• 737ab279 - config: Optimize for speed not size

Compare with previous version

resolved all threads

merged