[SOLVED] generic kernel for -currrent with 8GB ram: how much of a time saving?
SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
> Tracy Tiger
The very fact that I asked the question belies a lingering reticence which I have no reason to keep and every reason to jettison!
If I can configure my own conky and use my own aliases, and keep my system -current, I guess it is high time I switched to full play/experiment mode in slackware, then bring home the goodies to others.
But as Tracy suggests above: why not try it as an experiment?
Of course. Also, it is recommended that you switch to the generic kernel after you install the system. If you look here for example, you will find the following:
Use one of the provided generic kernels for daily use. Do not report
bugs until/unless you have reproduced them using one of the stock
generic kernels. You will need to create an initrd in order to boot
the generic kernels - see /boot/README.initrd for instructions.
The huge kernels are primarily intended as "installer" and "emergency"
kernels in case you forget to make an initrd.
I often experiment with kernels and therefore the huge configuration is always my first choice, since I don't want to rebuild the initrd every time I have compiled a new kernel. I couldn't notice any difference in performance between huge and generic kernels. There may be a difference in boot time, but since I boot from a fast SSD this is not noticeable for me.
You should get a larger performance increase (although it shouldn't actually not be that large) with compiling a kernel optimized for your CPU than with switching to generic.
You will get a greater performance increase going from 32-bit to 64-bit than from compiling your own custom kernel.
The huge kernel boots extremely slowly on older computers and slightly more slowly on newer computers, compared to generic. This is because it has to be loaded into RAM. As the huge kernel is huge, it takes a very long time on older computers.
generic kernel for current brings no noticeable performance increase
I followed Pat's readme and created the initrd-tree, the initrd.gz, adjusted lilo.conf settings by adding the appropriate line in the right spot, then re-ran lilo before going for reboot.
I didn't physically time both boot sequences, however, I am satisfied (by having had to reboot an inordinate number of times due to noob-klutz, that it is the same (certainly the time the splash on xfce is the same, though I expect this is incidental, since it is X starting up)
I guess my next target is Tobi's suggestion to build a machine-customized kernel (though even as i type those words, it seems like a "bridge too far" for the moment; maybe not; I'll have a look at it Tobi
thanks to all respondents!
PS incidentally: how can I be 100% sure that I am running the generic kernel?
I tried uname -a but that didn't provide such information