Messages in this thread |  | | | Subject | Re: strange CRASH_DUMP dependencies | | From | (Eric W. Biederman) | | Date | Mon, 22 Aug 2005 18:56:49 -0600 |
| |
Adrian Bunk <bunk@stusta.de> writes:
>> > - Is there any sane reason for the dependency on EMBEDDED? >> > >> >> I believe this was introduced because large servers can have huge amount >> of memory (running into Tera Bytes) and saving all that memory might not be >> practical. Hence it was perceived that until some filtering mechanism is >> implemented, it is more suited for small systems. >>... > > It seems you have a wrong impression of what EMBEDDED in the kernel > does. > > There is _not_ a choice EMBEDDED/WORKSTATION/SERVER. > > EMBEDDED is an option that shows "save space at any cost" options. > > It allows you to tell gcc to generate slower but faster code or to > deselect options in the "do this only if you _really_ know what you are > doing" class.
And at the moment that is where building a crashdump capture kernel falls. "do this only if you really know what you are doing".
Eric
- 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/
|  |