Received: by 2002:a05:7412:b10a:b0:f3:1519:9f41 with SMTP id az10csp29056rdb; Wed, 29 Nov 2023 18:43:15 -0800 (PST) X-Google-Smtp-Source: AGHT+IGxUYe9aIq2svD5nirLG+Ghj2AHj/ptpUWdiVFhguAVXf84TFp+kSmKvWd2XilBPSEoDoqU X-Received: by 2002:a05:6a00:a0b:b0:6be:559:d030 with SMTP id p11-20020a056a000a0b00b006be0559d030mr21216645pfh.19.1701312194785; Wed, 29 Nov 2023 18:43:14 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1701312194; cv=none; d=google.com; s=arc-20160816; b=ZP6bhzNZZzUc9/T7K0N3F0EiPXvExodTR632IUnO/W1zCWKHG3ufTxo+3c/F/sCNXL 8tZ2oOVm/GXG9Iw7CJWoNpTmnRcKqj00aC6zY4CkkZyFOr1iNXl6YF8GYkubsWQ1BsZ1 KBYVm/TZsj2tphWEHpI86Cf9WZOKti6TFDSmcgSeo1TWOHHBZThGIDHfVR7YKtzvWp+F LUiIRkuCzKiFPZUXCga1hNNarPhySjrBVrZ5gvYdn6TTpeGwky+sY80JY+/WG89V7vam BA+nWO3Gjt2ZpPOmfzdGSlwh6p05wMqbOr3PLcm1aaS6loSWNq8CgrhezMQ6wkG5lH03 Uz7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=OlnSo+MSVJ02cRZKA4QKHS15/hcZAeTG8jw5g53iRBQ=; fh=JJT9NTPZpdyYRfisKVfBlcRWUzVtYJGea5NGLKWFboU=; b=DWsONop2WkhCU6kJm93qfkz/tBop/rRH6Fi0Oj+HYzkgDgu/9hsUhw8PTylZluXnsF GGQ+FLH46I3+dUngbZPa5irJsJjJvg4nvw5Hqrjkl2WcF3pEgXHiBYTRY2FG9xc+uYJ8 eRmyPRVm/MKd4TpJDsFs2Q42LP1oVVCD/Jy8Ya0ba+dYBZqrJhxdiMM/t3wvzYTYRsU6 4inhLFo9VOKJsUjnhejgMyRP1cb/G3ocFgzKcFd8xp/l2Hh32+kOW1HMDvWW6TpOt3+n 5aKL4h1bXbkJtCYSzkhe7UHYR2uafxRk5n71OsSb9uc1X7ILLnIPTfkcPsKJwVz6TdZ+ zq/A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=eI1j77Y5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from groat.vger.email (groat.vger.email. [2620:137:e000::3:5]) by mx.google.com with ESMTPS id bo23-20020a056a02039700b005c5e28c3529si245332pgb.600.2023.11.29.18.43.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 29 Nov 2023 18:43:14 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) client-ip=2620:137:e000::3:5; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=eI1j77Y5; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:5 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by groat.vger.email (Postfix) with ESMTP id 7ABBE802ACC9; Wed, 29 Nov 2023 18:43:12 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at groat.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344232AbjK3Cmr (ORCPT + 99 others); Wed, 29 Nov 2023 21:42:47 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55756 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235028AbjK3Cmd (ORCPT ); Wed, 29 Nov 2023 21:42:33 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 57AD01FEF for ; Wed, 29 Nov 2023 18:42:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1701312141; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=OlnSo+MSVJ02cRZKA4QKHS15/hcZAeTG8jw5g53iRBQ=; b=eI1j77Y5sjEtITGstFSkNxSa/AiGbCAocyrOIrYPNaR1gRZ2g5/LXflNwaToicxW9Sbgwy EGTX/TCFwhCIMHLEwruiJnbeGyuhpm8cCEWgcyWGmSZrUN6/YrYSSSXMMfv+CbW4wfX2bh VoWTpOyx4gPWw7JJD/3rsVHn6WmbDOo= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-306-57Xl6FtdMtiy8EYMFLhbpQ-1; Wed, 29 Nov 2023 21:42:17 -0500 X-MC-Unique: 57Xl6FtdMtiy8EYMFLhbpQ-1 Received: from smtp.corp.redhat.com (int-mx10.intmail.prod.int.rdu2.redhat.com [10.11.54.10]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 5A8722815E20; Thu, 30 Nov 2023 02:42:17 +0000 (UTC) Received: from localhost (unknown [10.72.113.121]) by smtp.corp.redhat.com (Postfix) with ESMTPS id A36F8492BFE; Thu, 30 Nov 2023 02:42:16 +0000 (UTC) Date: Thu, 30 Nov 2023 10:42:13 +0800 From: Baoquan He To: Michal Hocko Cc: Jiri Bohac , Pingfan Liu , Tao Liu , Vivek Goyal , Dave Young , kexec@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/4] kdump: crashkernel reservation from CMA Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.10 X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on groat.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (groat.vger.email [0.0.0.0]); Wed, 29 Nov 2023 18:43:12 -0800 (PST) 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.