From patchwork Fri Dec 17 09:08:25 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Baoquan He X-Patchwork-Id: 12683929 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id C03BEC433EF for ; Fri, 17 Dec 2021 09:08:58 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 216A66B0072; Fri, 17 Dec 2021 04:08:48 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 1A0316B0073; Fri, 17 Dec 2021 04:08:48 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 041156B0075; Fri, 17 Dec 2021 04:08:47 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0106.hostedemail.com [216.40.44.106]) by kanga.kvack.org (Postfix) with ESMTP id EA7DB6B0072 for ; Fri, 17 Dec 2021 04:08:47 -0500 (EST) Received: from smtpin25.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with ESMTP id A1E938249980 for ; Fri, 17 Dec 2021 09:08:37 +0000 (UTC) X-FDA: 78926710674.25.409C12E Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by imf23.hostedemail.com (Postfix) with ESMTP id 7B332140007 for ; Fri, 17 Dec 2021 09:08:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1639732116; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version: content-transfer-encoding:content-transfer-encoding; bh=MbKEnIMqozJmjIU2Viw6TRTg5VDB7tuZyWJ3ztwdV1w=; b=J4pfhRqNXtO45nR01y5zjdgZ1dOlQ075VY0HIctRjU0NuzMelGNp7TY/bDHlO72IbMaW7n mdrJUGu1aolyxw6kxVe24RoFueTOfgk7RW+Z/rPiqZpSgMtvD5a9lEgxNWcUDFrKACPOip VI8Ej/ZDBgnQyFxdoZsMxrgWOC7NXYw= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-563-xS8qT_EzPv6xrFQI-00Jsw-1; Fri, 17 Dec 2021 04:08:33 -0500 X-MC-Unique: xS8qT_EzPv6xrFQI-00Jsw-1 Received: from smtp.corp.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.14]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id E19BF1017968; Fri, 17 Dec 2021 09:08:31 +0000 (UTC) Received: from MiWiFi-R3L-srv.redhat.com (ovpn-12-164.pek2.redhat.com [10.72.12.164]) by smtp.corp.redhat.com (Postfix) with ESMTP id E3D297A498; Fri, 17 Dec 2021 09:08:28 +0000 (UTC) From: Baoquan He To: linux-kernel@vger.kernel.org Cc: linux-mm@kvack.org, akpm@linux-foundation.org, corbet@lwn.net, hch@lst.de, cl@linux.com, bhe@redhat.com Subject: [PATCH 0/2] Clean up document and small improvement of atomic pool Date: Fri, 17 Dec 2021 17:08:25 +0800 Message-Id: <20211217090827.101938-1-bhe@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.14 Authentication-Results: imf23.hostedemail.com; dkim=pass header.d=redhat.com header.s=mimecast20190719 header.b=J4pfhRqN; dmarc=pass (policy=none) header.from=redhat.com; spf=none (imf23.hostedemail.com: domain of bhe@redhat.com has no SPF policy when checking 170.10.129.124) smtp.mailfrom=bhe@redhat.com X-Rspamd-Server: rspam12 X-Rspamd-Queue-Id: 7B332140007 X-Stat-Signature: fgrh4x7rsufg7ebm1i9w5aornpaow5xg X-HE-Tag: 1639732112-473126 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: This patchset contains two small patches. Identified this when I tried to fix a kdump bug that page allocation failure is always warned out during kdump kernel on x86_64. Since dma atomic pool is initialized very early during bootup, that allocation failure is always triggered in dma_atomic_pool_init() firstly. I originally planned to add an kernel option to disable each of the three dma atomic pool. Finally I realized it's not only dma atomic pool getting the issue, any later requsting page from DMA zone will fail. So I changed solution to fix the kdump bug. While the document clean up and the small fix which allows user to disable atomic pool makes sense to improve. The small fix which makes 'coherent_pool=0' disable dma atomic pool like 'cma=0', looks more reasonable than the old behavioud which will take the default atomic size. [PATCH RESEND v2 0/5] Avoid requesting page from DMA zone when no managed pages https://lore.kernel.org/all/20211207030750.30824-1-bhe@redhat.com/T/#u Baoquan He (2): docs: kernel-parameters: Update to reflect the current default size of atomic pool dma-pool: allow user to disable atomic pool Documentation/admin-guide/kernel-parameters.txt | 5 ++++- kernel/dma/pool.c | 7 +++++-- 2 files changed, 9 insertions(+), 3 deletions(-)