You are not logged in.
Pages: 1
Has anyone come across a website that gets into detail about all the options in the kernel .config and which yield the best performance?
I've recompiled my own kernel and changed some settings, but there are too many and most are not documented in much detail in gconfig. My boot time became 5 seconds faster, I'm looking to optimize the kernel even more.
Offline
I agree that there's not enough documentation. Sites like LWN, the kernel mailing list, and KernelNewbies help somewhat, but not enough.
The kernel help seems more oriented to kernel hackers themselves than power users (both the ? button and the Documentation folder).
Let's discuss kernel configs in here!
Last edited by Ranguvar (2009-03-02 12:20:26)
Offline
That'd be great. I tried the same before and referred to google every once in a while. I'll try to put together some resources.
Offline
Well, there's the usual, disable everything you don't and won't use (ppp, slip, other network cards, raid, lvm, etc), then perhaps compile it with essential modules in the kernel (filesystem, sd/hd controllers etc).
Can one live without an initrd on Arch?
Offline
If you compile the options you don't need as modules, will they really make much of a difference, performance-wise, if you don't load them?
Dylon
Offline
If you compile the options you don't need as modules, will they really make much of a difference, performance-wise, if you don't load them?
No they won't, you'll just save (little) space
Offline
Can one live without an initrd on Arch?
Of course. Arch, and many other distros, use initramfs (not initrd, btw) for boot-time support when using the stock kernel. If you build your own, you can build your boot-time requirements into the kernel i.e. not as modules.
There are exceptions e.g. encrypted root needs an init image.
Offline
Fackamato wrote:Can one live without an initrd on Arch?
Of course. Arch, and many other distros, use initramfs (not initrd, btw) for boot-time support when using the stock kernel. If you build your own, you can build your boot-time requirements into the kernel i.e. not as modules.
There are exceptions e.g. encrypted root needs an init image.
initramfs, of course , initrd is etched into my memory since early Debian days...
The initramfs only contains the stuff in /etc/mkinitcpio.conf right?
Offline
mkinitcpio.conf controls the configurable elements of the init image. The rest of it is common to all images created by mkinitcpio.
Offline
I can't compile my SATA drivers into the kernel, can only select them as 'M' in the kernel config.
CONFIG_ATA_PIIX: │
│ │
│ This option enables support for ICH5/6/7/8 Serial ATA │
│ and support for PATA on the Intel ESB/ICH/PIIX3/PIIX4 series │
│ host controllers. │
│ │
│ If unsure, say N. │
│ │
│ Symbol: ATA_PIIX [=m] │
│ Prompt: Intel ESB, ICH, PIIX3, PIIX4 PATA/SATA support │
│ Defined at drivers/ata/Kconfig:104 │
│ Depends on: ATA && ATA_SFF && PCI │
│ Location: │
│ -> Device Drivers │
│ -> Serial ATA (prod) and Parallel ATA (experimental) drivers (ATA [=m]) │
│ -> ATA SFF support (ATA_SFF [=y])
Offline
Are ATA && ATA_SFF && PCI built into the kernel?
Offline
Are ATA && ATA_SFF && PCI built into the kernel?
Thanks, that was it
Offline
Can one live without an initrd on Arch?
Yes. Just make sure to compile in (not modules) your drive controller and file system drivers, and *viola* no initrd=imagefile needed.
"If the data structure can't be explained on a beer coaster, it's too complex." - Felix von Leitner
Offline
Then you can disable generation of initramfs images in your install and in your kconfig.
Offline
_Real_ men don need no steenkin modules! initcpio's for noooobs!!!
Offline
I never really got booting without initramfs to work :\
Me neither. Mind you, I've never made much of an effort to figure out what was going wrong. I usually just think, "F**k it; modules aren't that bad," and rebuild.
And further to what others have said above, not building modules you don't need doesn't just save space, it saves time, too. The last couple of times I built a kernel here, I actually didn't expect it to boot because the compilation finished so quickly - I was sure something must have gone wrong somewhere.
0 Ok, 0:1
Offline
Ye, that's as far as I'm concerned the best reason to remove modules. To save time for compilation harhar. Well. I've tried shaving off some obvious modules I don't need, but some places in the kernel config, I have no clue of what I can, or can not remove without breaking the kernel or usability of the system :\ I wish there was some tool to build a kernel config based on what hardware the program autodetects or something to give you an idea at least
Offline
Ye, that's as far as I'm concerned the best reason to remove modules. To save time for compilation
harhar. Well. I've tried shaving off some obvious modules I don't need, but some places in the kernel config, I have no clue of what I can, or can not remove without breaking the kernel or usability of the system :\ I wish there was some tool to build a kernel config based on what hardware the program autodetects or something to give you an idea at least
That should be (fairly) easy. Just do an lspci and match with the kernel config options. However, we need to compile some extra modules anyway, say, if you plug in your gamepad, or a camera, or something else. Or if you find you want to mess with NFS one day... or LVM.
Offline
NFS and LVM are fairly major changes that I probably wouldn't mind building a new kernel for (or use the stock kernel temporarily to get them up and running), but I always leave in pretty much every USB driver, because you never know what you might plug in.
0 Ok, 0:1
Offline
Pages: 1