-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi David,
David Klempner wrote: > Actually, I side with the kernel developers on this; the fact that > they're hiding the VMSPLIT options is basically a subtle hint that they > don't want people using them who don't *really* know what they're doing. Like me .. hence all the questions ;-) I just want to be able to use my full RAM, as having 2GB and using < 1GB is just "uncool" ;-) > I strongly suggest using CONFIG_HIGHMEM, and sticking with the default > 3/1 split. (I mean, it's *slightly* slower, but on the other hand what > caused them to do this was random breaking of java that took a long time > to diagnose.) That said... OK. I definitely will keep this in mind. >> I noticed too that if I select the embedded option, but unselect all new >> options that come with it I still get the memory split options. Is this >> the right way to go? > > NO. As in, all of those options (with the exception of > CONFIG_KALLSYMS_EXTRA_PASS) default to yes, and all of those defaults > are very important. If you disable them, you will, for example, break > most of the kernel's logging (printk), lose the ability to get core > dumps, and lose futexes (which will break a lot of modern threading). > Basically, saying no to any option option on that page (with the > exception of the KALLSYMS stuff) *WILL* break your system. > > So, make sure that everything, except CONFIG_KALLSYMS_EXTRA_PASS, on > that page is enabled. (that might be what you meant in the first place, > of course, but it's worth making sure...) All you need to be able to > select the VMSPLIT options is CONFIG_EMBEDDED (that is, saying yes to > the "Configure standard kernel features (for small systems)" item) which > doesn't actually have any impact on the code. Sorry, but one thing remains unclear. Ignoring the fact that adding embedded extras to your kernel on a non-embedded system just to get the the VMSPLIT options is (in my opinion) confusing and unlogical, is this step actually needed considering I (according to your advice) would take the default VMSPLIT anyway? What I mean is simply: If I enable HIGHMEM4GB to allow the kernel to use my 2GB of RAM, do I still need to add the embedded options (as you explain above), or is simply using HIGHMEM4GB enough? It's maybe a tough question is ask, but you definitely seem to know exactly what you are talking about ;-) > Hope this helps. Is sure does! Any advice to the above question? With that I should be complete I think ;-) Where do you get your information from btw (I'm curious as I didn't find much via Google explaining as clear as you did)? Thanks again, Ralph -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (MingW32) iD8DBQFEmQt3Ct0ZF9kLPvYRAt69AKCe/ClqjzQHMTZ3yvuNQ9sXwVbFsQCeMdwb BREkUr+u9/o9K8ZImMCdJmM= =8vc3 -----END PGP SIGNATURE----- -- [email protected] mailing list
