From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailout1.w1.samsung.com (mailout1.w1.samsung.com [210.118.77.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id CFBC130FC03 for ; Tue, 13 Jan 2026 22:59:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=210.118.77.11 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768345160; cv=none; b=VVneFXT/qqQdLz+iUU7BTMaMviRa/NbWa5y7kkcRW+K7DX22qxuSEPkK/mKSQ5IroBpyVPulscHuuxmWVy/h4HK7B9M+XqaVVPw1+FeIUrGznYD6Q9GEHnRxtSEbXqoEZtBHdPEtSp8tV3EQ2e8vWX+vBbBY8xTm37qjMabFbhA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1768345160; c=relaxed/simple; bh=+ZBx7AySFXUeov09FnzcPw/BfBgDaijoh4oxr7Rt//U=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:From:In-Reply-To: Content-Type:References; b=LGZIZzhgw/b856IhErqoQK4tnwTMF8tuPsyybvzHj7m1MDjNuSBLAw9leNkZOOvCYbkZmHEs5WVDNLDhMfNEeHMUBzechVREUpVpsI2hLFqZbG9sP9Iqqr+zJ2NdUll52g8FWgU5YIneOOy3ILMBTcYnqoXaZPYO7c5DFuLPTA8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=samsung.com; spf=pass smtp.mailfrom=samsung.com; dkim=pass (1024-bit key) header.d=samsung.com header.i=@samsung.com header.b=IZBFjmUk; arc=none smtp.client-ip=210.118.77.11 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=samsung.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=samsung.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=samsung.com header.i=@samsung.com header.b="IZBFjmUk" Received: from eucas1p2.samsung.com (unknown [182.198.249.207]) by mailout1.w1.samsung.com (KnoxPortal) with ESMTP id 20260113225909euoutp01b221f7aa09b9d55270c014c18ae37d24~KbIt0GZ1t2471024710euoutp01C for ; Tue, 13 Jan 2026 22:59:09 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 mailout1.w1.samsung.com 20260113225909euoutp01b221f7aa09b9d55270c014c18ae37d24~KbIt0GZ1t2471024710euoutp01C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t=1768345149; bh=pKj8OFgIWZYaPjLOGY0Hru5SNu94TWYuwIW6GtEw+PU=; h=Date:Subject:To:Cc:From:In-Reply-To:References:From; b=IZBFjmUkin+XtXk9bQ9fIqYSTGm8Btqh+QIviHYKjDKoKYs57o3MoqaB+PEFgorjj eCm+dFMWXmVaT8evuSaB4/ca9D9jHtHw8/1mnYYoOQSifc8CLrF3ePufVr1/OvKo5A dH1gkUg1/DWWCaF9qsmP0zhfIrSIXG8YZ5nd9b3Y= Received: from eusmtip2.samsung.com (unknown [203.254.199.222]) by eucas1p2.samsung.com (KnoxPortal) with ESMTPA id 20260113225908eucas1p20120cc4c7ab2c17932dfb40d9f02c83a~KbIsqiN7i1638616386eucas1p2o; Tue, 13 Jan 2026 22:59:08 +0000 (GMT) Received: from [106.210.134.192] (unknown [106.210.134.192]) by eusmtip2.samsung.com (KnoxPortal) with ESMTPA id 20260113225906eusmtip2be65a6cf8cc51f597c2f777164fd7547~KbIq5jSm91614816148eusmtip2I; Tue, 13 Jan 2026 22:59:06 +0000 (GMT) Message-ID: <643b75da-d673-4106-888f-7fe232dccf7b@samsung.com> Date: Tue, 13 Jan 2026 23:59:05 +0100 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Betterbird (Windows) Subject: Re: [PATCH 0/3] dma-mapping: Improve atomic pool behaviour To: Robin Murphy , akpm@linux-foundation.org, vbabka@suse.cz, david@kernel.org Cc: bhe@redhat.com, iommu@lists.linux-foundation.org, linux-mm@kvack.org, vladimir.kondratiev@mobileye.com, s-adivi@ti.com, linux-kernel@vger.kernel.org, lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com, rppt@kernel.org, surenb@google.com, mhocko@suse.com, jackmanb@google.com, hannes@cmpxchg.org, ziy@nvidia.com Content-Language: en-US From: Marek Szyprowski In-Reply-To: Content-Transfer-Encoding: 7bit X-CMS-MailID: 20260113225908eucas1p20120cc4c7ab2c17932dfb40d9f02c83a X-Msg-Generator: CA Content-Type: text/plain; charset="utf-8" X-RootMTR: 20260112154649eucas1p265e59d616343bb4c2ce80128c393f56b X-EPHeader: CA X-CMS-RootMailID: 20260112154649eucas1p265e59d616343bb4c2ce80128c393f56b References: On 12.01.2026 16:46, Robin Murphy wrote: > These days we have somewhat of a matrix of mm zones that may or may not > exist and may or may not be empty, which the per-zone atomic pool logic > doesn't actually handle all that well. It's not all that difficult to > improve robustness and reduce redundancy, so that's what this series > aims for. > > I initially wrote this just because I happened to be looking through the > boot log of one of my boards and had one of those out-of-the-blue > realisations of "hang on, why *is* it allocating pools for zones it > doesn't even have memory in?", but coincidentally, it seems that others > happened to notice related aspects around the same time[1][2]. This is > my attempt to sort it all out properly. > > I guess this could go via either the dma-mapping or mm tree, whichever > maintainers prefer. I will take this patchset to dma-mapping-fixes branch, thanks! Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland