Eric W. Biederman wrote: > Matt Mackall <mpm@xxxxxxxxxxx> writes: > >> As much as I like kexec, it loses on memory footprint by about 100x. >> It's not appropriate for all use cases, especially things like >> consumer-grade wireless access points and phones. > > In general I agree. The cost of a second kernel and initrd can be > prohibitive in the smallest systems, and if you do a crash capture > with using a standalone app that is reinventing the wheel. > > That said. I can happily run kdump with only 16M-20M reserved. > So on many systems the cost is affordable. Understood. On some of my systems, the memory budget for the entire system is 10M. On most systems I work with, it is a struggle to reserve even 64K for this feature. -- Tim ============================= Tim Bird Architecture Group Chair, CE Linux Forum Senior Staff Engineer, Sony Corporation of America ============================= -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
