Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bnieuwen
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
by
bnieuwen
4y ago
As the sibling said those numbers are very configurable. e.g. around the x86 handhelds there are tinkerers running their U/P class chips at anywhere from 5W configured to 30+W configured (and with the appropriate cooling could totally
2.
▲
by
bnieuwen
4y ago
Actually Phoronix has power benchmarks for the ACPI power profiles[1]. Seems like a boost to ~28W or so with a long term average of 22-23W. (Note that this is SoC package power instead of the full laptop though, but that is pretty typical,
3.
▲
by
bnieuwen
4y ago
Are we sure this is actually 4 cores and not a reporting error? AFAICT with some surface Googling Apple doesn't sell the M2 with cores disabled does it? Also 4 cores 8 threads is suspicious given that AFAIU the M2 doesn't have SMT
4.
▲
by
bnieuwen
4y ago
So there are two parts to this: the app producing the image in the application window and then the windowing system combining multiple windows together to form the final image you see on screen. The former gets done in process (using e.g. G
5.
▲
by
bnieuwen
4y ago
The problem with containers and graphics drivers is that those drivers have an userspace component. This depends on the hardware (e.g. AMD vs. Intel vs. NVidia all have different drivers of course) and in the case of NVidia this has to be e
6.
▲
by
bnieuwen
4y ago
A random attempt: Typically the application wants to draw stuff on the GPU. To do this it calls into the GPU driver, which builds a big memory buffer in some implementation-defined format that instructs the GPU what to do, and then the driv
7.
▲
by
bnieuwen
4y ago
There have been exploits and there will probably be more in the future, see e.g. https://googleprojectzero.blogspot.com/2020/09/attacking-qua...
8.
▲
by
bnieuwen
8y ago
I think the keyword might be an 8k executable, not 8k of code. If I compile the example with clang on my box (linux x86_64) I get a 17K executable, for which the .text section (containing pretty much the runnable code)is 0x291 (661) bytes w