* Reserved memory estimation for crashkernel=
@ 2014-02-10 10:23 Louis Bouchard
2014-02-14 7:21 ` Atsushi Kumagai
0 siblings, 1 reply; 2+ messages in thread
From: Louis Bouchard @ 2014-02-10 10:23 UTC (permalink / raw)
To: kexec@lists.infradead.org
Hello,
I would be interested to know if there is a semi-accurate way to evaluate the
amount of memory that needs to be reserved and passed to the crashkernel=
parameter ?
I understand that it is very specific to the environment (system configuration,
kernel options, etc) but if we could at least know how much memory will be
required by makedumpfile it would be a good start.
Maybe we can imagine an enhancement to makedumpfile to have it evaluate a value
that could provide some kind of estimate.
TIA,
Kind regards,
...Louis
--
Louis Bouchard
Software engineer,
Ubuntu
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Reserved memory estimation for crashkernel=
2014-02-10 10:23 Reserved memory estimation for crashkernel= Louis Bouchard
@ 2014-02-14 7:21 ` Atsushi Kumagai
0 siblings, 0 replies; 2+ messages in thread
From: Atsushi Kumagai @ 2014-02-14 7:21 UTC (permalink / raw)
To: Louis Bouchard; +Cc: kexec@lists.infradead.org
Hello Louis,
On 2014/02/10 19:24:05, kexec <kexec-bounces@lists.infradead.org> wrote:
> Hello,
>
> I would be interested to know if there is a semi-accurate way to evaluate the
> amount of memory that needs to be reserved and passed to the crashkernel=
> parameter ?
>
> I understand that it is very specific to the environment (system configuration,
> kernel options, etc) but if we could at least know how much memory will be
> required by makedumpfile it would be a good start.
Almost all the memory required by makedumpfile is used for the bitmap,
and its maximum size can be calculated as:
((system memory size / page size) / 8) * 2 [byte]
Additional requirement size will be a few MByte at most, so estimating
for makedumpfile is easy.
Moreover, makedumpfile can work even with lower memory since the cyclic mode
was introduced. Then, the performance degradation caused by multi-cycle
processing is very small according to the report below:
https://lkml.org/lkml/2013/3/26/914
(Please see the "Performance degradation in cyclic mode" paragraph.)
Thanks
Atsushi Kumagai
>
> Maybe we can imagine an enhancement to makedumpfile to have it evaluate a value
> that could provide some kind of estimate.
>
> TIA,
>
> Kind regards,
>
> ...Louis
> --
> Louis Bouchard
> Software engineer,
> Ubuntu
>
> _______________________________________________
> kexec mailing list
> kexec@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/kexec
>
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-02-14 7:28 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-10 10:23 Reserved memory estimation for crashkernel= Louis Bouchard
2014-02-14 7:21 ` Atsushi Kumagai
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.