Messages in this thread | | | From | Keith Owens <> | Subject | Re: module choices affecting base kernel size??? | Date | Fri, 03 May 2002 11:28:57 +1000 |
| |
On Thu, 2 May 2002 20:57:40 -0400 (EDT), Tom Oehser <tom@toms.net> wrote: > >> Tom Oehser <tom@toms.net> wrote: >> >Changing all =m to =n in my config makes a 4K difference in the kernel size. > >On Fri, 3 May 2002, Keith Owens wrote: > >> The majority of modules have no effect on kernel size but some modules >> require base kernel code as well. This is typically common code or low >> level setup functions. You will find that those modules will not load >> now or will break. > >Great. I must have missed the list of exactly *which* modules do this... > >Any ideas on a reasonable way of how to identify them?
Not easy. Some of it is in the Makefiles, some of it is in the code. Looking for conditional EXPORT_SYMBOLS() will find some of the extra space, I don't know of any way of finding all of the extra code/data, apart from compiling and measuring.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |