[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: 1449811774296.jpg (111 KB, 550x481)
111 KB
111 KB JPG
Does leaving CONFIG_RANDOM_TRUST_CPU unset when building Linux actually plug a hardware backdoor or am I being trolled into making the kernel slower?
>>
The kernel uses other inputs as well. This just controls if it uses additional hardware RNGs, like RDRAND.

Also it's not like RDRAND is fast by any measure. There's a good chance you're making the kernel slower by *enabling* it.
>>
>>108350842
AI slop
>>
>>108350889
RDRAND can save you from boot hangs if you have a configuration that truly doesn't have any other entropy source, but that's not likely for a desktop user.
>>
>>108350926
Yeah, but if you don't you're literally adding thousands of cycles of TP and LAT costs to your kernel on every single RDRAND.
>>
File: 1765880163449982.gif (1.29 MB, 320x320)
1.29 MB
1.29 MB GIF
>>108350842
>>
>>108350967
All fairness, Intel RDRAND 'only' takes ~500 cycles. It's AMD's putting it in microcode that takes 1k+.
>>
File: rdrand.png (52 KB, 1920x400)
52 KB
52 KB PNG
>>108350983
>~500 cycles
I need to see a source for this.
>>
File: crop.png (65 KB, 589x385)
65 KB
65 KB PNG
>>108351020
Reciprocal throughput in cycles is the second to last column.
https://www.agner.org/optimize/instruction_tables.pdf
>>
>>108350842
Lucky Star is a baby anime
>>
File: coffee_lake.png (31 KB, 1254x400)
31 KB
31 KB PNG
>>108351075
Yeah, I'm not buying it.



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.