Earlier quoted context omitted.
This alphabetti spaghetti of boot flags is getting ridiculous, there seems to be no central list anywhere, just random snippets across the web. Why is there not a Linus rant when you really need one? :-(
lsmod modinfo ${somemodule} man lsmod man modinfo This is elementary level linux, you should know this.
Bisected: The Unfortunate Reason Linux 4.20 Is Running Slower
111–114 of 114 posts
Re: Bisected: The Unfortunate Reason Linux 4.20 Is Running Slower
#112Earlier quoted context omitted.
This alphabetti spaghetti of boot flags is getting ridiculous, there seems to be no central list anywhere, just random snippets across the web. Why is there not a Linus rant when you really need one? :-(
lsmod modinfo ${somemodule} man lsmod man modinfo This is elementary level linux, you should know this.
Re: Bisected: The Unfortunate Reason Linux 4.20 Is Running Slower
#113Earlier quoted context omitted.
Apparently the way to turn this and other mitigations off is the following mouthful: pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier Would it make sense to have a single flag to "run insecure but fast" that we can use on pure development machines, test servers and the like? My Intel development server only runs code I choose.
This alphabetti spaghetti of boot flags is getting ridiculous, there seems to be no central list anywhere, just random snippets across the web. Why is there not a Linus rant when you really need one? :-(
Re: Bisected: The Unfortunate Reason Linux 4.20 Is Running Slower
#114Earlier quoted context omitted.
Yes - but for their cost to increase by such a large factor, the only obvious thing I can think of is that their prediction is disabled. I didn't follow your comment about a "programmable pipeline". I don't think many or any of the Phoronix benchmarks are based on a pipeline with indirect branches at their core.
> I don't think many or any of the Phoronix benchmarks are based on a pipeline with indirect branches at their core. I think a bunch are. e.g. for instance FFMPEG / libavfilter which is basically a node graph set up at runtime. Don't know for cinebench since it's closed source, but Blender present in the benchmarks is also based around a nodal rendering architecture. Stuff like PHP / CGI also heavily depend on functi…
So I still doubt that that indirect branches are "dense" in those benchmarks: it just doesn't make sense since the core work they are doing are highly tuned encode/decode/whatever kernels, even if there is a control layer over top of that using indirect branches.