[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZWf2hdX9L8SZhvzB@MiWiFi-R3L-srv>
Date: Thu, 30 Nov 2023 10:42:13 +0800
From: Baoquan He <bhe@...hat.com>
To: Michal Hocko <mhocko@...e.com>
Cc: Jiri Bohac <jbohac@...e.cz>, Pingfan Liu <piliu@...hat.com>,
Tao Liu <ltao@...hat.com>, Vivek Goyal <vgoyal@...hat.com>,
Dave Young <dyoung@...hat.com>, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] kdump: crashkernel reservation from CMA
On 11/29/23 at 10:25am, Michal Hocko wrote:
> On Wed 29-11-23 15:57:59, Baoquan He wrote:
> [...]
> > Hmm, Redhat could go in a different way. We have been trying to:
> > 1) customize initrd for kdump kernel specifically, e.g exclude unneeded
> > devices's driver to save memory;
> > 2) monitor device and kenrel memory usage if they begin to consume much
> > more memory than before. We have CI testing cases to watch this. We ever
> > found one NIC even eat up GB level memory, then this need be
> > investigated and fixed.
>
> How do you simulate all different HW configuration setups that are using
> out there in the wild?
We don't simulate.
We do this with best effort with existing systems in our LAB. And
meantime partner company will test and report any OOM if they encounter.
Powered by blists - more mailing lists