Intel GPU Driver Tries To Rip Out FBDEV Support

[Ericg]

Use top to see what's hogging your CPU.
Building the kernel, unless you're building 99% of all modules, should be well under 10M. 2-3 on a strong machine.

BTW, what's your machine hardware configuration (unless I missed it).

- Gilboa

I gotta recompile anyway to test a patch, so I'll see what happens.


Machine configuration:

CPU is an Intel i5-2467M clocked at 1.6GHz, dual-core + HT
Ondemand goveror
4GB's of RAM
3.2GB's of SWAP
HDD's is an SSD, i forget what make and model though.
Only other speed-bump i could really think of would be to move the sources to /tmp and compile it in /tmp. Since /tmp is tmpfs, shouldn't that run the entire compile straight in RAM instead of hitting the SSD?

[gilboa]

I gotta recompile anyway to test a patch, so I'll see what happens.


Machine configuration:

CPU is an Intel i5-2467M clocked at 1.6GHz, dual-core + HT
Ondemand goveror
4GB's of RAM
3.2GB's of SWAP
HDD's is an SSD, i forget what make and model though.
Only other speed-bump i could really think of would be to move the sources to /tmp and compile it in /tmp. Since /tmp is tmpfs, shouldn't that run the entire compile straight in RAM instead of hitting the SSD?

30m with an SSD?!?!?!
Does your ssd mount options include discard?
Do you have encryption on your build directory?


EDIT:
Come to think about you, are testing oldconfig, right?
I'm so used to building the kernel with optimized (read: small) configuration, I forgot how huge the default .config is.
... So, given the (as far as I remember) size of default configuration, 30m on a fairly low-end machine is more-or-less OK.

However, the build is very IO intensive, at least on my Xeon workstation (12C/24T, 36GB, 6x300GB in RAID6) the software RAID is the main limiting factor when building the kernel.
The SSD should have been able to improve this figure by a fairly large margin.

- Gilboa

[Ericg]

30m with an SSD?!?!?!
Does your ssd mount options include discard?
Do you have encryption on your build directory?

- Gilboa

Yes; and No.

Discard isn't necessary for some SSD's, as its handled by the firmware automatically, unfortunately for me... in this one, it is not. Therefore I have to specify it at mount time, or let cron/systemd handle it.

No encryption on the build directory, but btrfs is set to compress

And yes its oldconfig -- fedora default config, as such im sure just about every module is set to be compiled lol

[gilboa]

Just ran oldconfig.

$ make -j 24
real 11m1.545s
user 83m40.261s
sys 10m17.770s

$ find | grep .ko$ | wc -l
2479

Given the huge number of (default) modules, 30+ on a low end (read: mobile) i5 is acceptable.

EDIT:
Noticed my kernel build was still using my secure (encrypted) ccache. Recreated a new ccache home in unencrpyted partition and redid the build on fresh new kernel copy.
(Also bumped the jobs number... just in-case)

$ make -j 36
real 5m4.928s
user 89m12.660s
sys 10m51.218s

- Gilboa

[Ericg]

Just ran oldconfig.

$ make -j 24
real 11m1.545s
user 83m40.261s
sys 10m17.770s

$ find | grep .ko$ | wc -l
2479

Given the huge number of (default) modules, 30+ on a low end (read: mobile) i5 is acceptable.

EDIT:
Noticed my kernel build was still using my secure (encrypted) ccache. Recreated a new ccache home in unencrpyted partition and redid the build on fresh new kernel copy.
(Also bumped the jobs number... just in-case)

$ make -j 36
real 5m4.928s
user 89m12.660s
sys 10m51.218s

- Gilboa

compiling in RAM, and a localmodconfig cut the compile time down to about 15-20minutes (forgot to add time onto the end, just kept an eye on the clock)

Thanks for all your helps guys. Much appreciated.