From mboxrd@z Thu Jan 1 00:00:00 1970 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 gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id BF5BFCD4F24 for ; Wed, 13 May 2026 14:53:28 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 8089D10E326; Wed, 13 May 2026 14:53:28 +0000 (UTC) Authentication-Results: gabe.freedesktop.org; dkim=pass (2048-bit key; unprotected) header.d=intel.com header.i=@intel.com header.b="e4ZZFKl5"; dkim-atps=neutral Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.10]) by gabe.freedesktop.org (Postfix) with ESMTPS id D240110E326; Wed, 13 May 2026 14:53:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1778684008; x=1810220008; h=message-id:subject:from:to:cc:date:in-reply-to: references:content-transfer-encoding:mime-version; bh=+nkd0hIANHMErNoW+36L2RFIXXYiPCP2hqzvZ335Z8U=; b=e4ZZFKl57ZHxPqBfUH3439t2YDbD8StUptzutsZ7kYcr2m6ww8EFhbEi N8sepPt6auciLvY3j2aDOGvhGTJ7QD7AtVzuvfFnd9NP6VBvq6JkTNsjk 4Q/AnSGkn6FrtqOd1W3oBhvXZSzTf8b6wyyQApl8WcVZZSq+ZfO/TDwHs lplaGr4df+15AMaNGvh/7izsrOpyb7/GZ5KMzyHkLV/ud9mWFF8UXBpzZ C6lrczYFzzz1yBLZM4kWjw4t1fXiay6LZx6Szh2Qg0ayF0hecuWNRTmwD tHEGUmdlOe2Xz/kdUI8jDPNOuFEUPCeCviFxbibK/UYUdXGuO9Y0upKlj Q==; X-CSE-ConnectionGUID: 56Ia8NgaTiSlIoi4dz0GDg== X-CSE-MsgGUID: lOyhsEO9QxCZ2/dw9rBpFA== X-IronPort-AV: E=McAfee;i="6800,10657,11785"; a="97039256" X-IronPort-AV: E=Sophos;i="6.23,232,1770624000"; d="scan'208";a="97039256" Received: from orviesa003.jf.intel.com ([10.64.159.143]) by orvoesa102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 May 2026 07:53:21 -0700 X-CSE-ConnectionGUID: vjFABCX/SsuPcYOxQxbOUg== X-CSE-MsgGUID: X8kOSuBQQWCEnb4zi4I8dw== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.23,232,1770624000"; d="scan'208";a="242112986" Received: from ijarvine-mobl1.ger.corp.intel.com (HELO [10.245.244.49]) ([10.245.244.49]) by ORVIESA003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 May 2026 07:53:14 -0700 Message-ID: Subject: Re: [PATCH 1/2] mm/shmem: add shmem_insert_folio() From: Thomas =?ISO-8859-1?Q?Hellstr=F6m?= To: "David Hildenbrand (Arm)" , Christian =?ISO-8859-1?Q?K=F6nig?= , intel-xe@lists.freedesktop.org Cc: Andrew Morton , Lorenzo Stoakes , "Liam R. Howlett" , Vlastimil Babka , Mike Rapoport , Suren Baghdasaryan , Michal Hocko , Hugh Dickins , Baolin Wang , Brendan Jackman , Johannes Weiner , Zi Yan , Huang Rui , Matthew Auld , Matthew Brost , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , David Airlie , Simona Vetter , dri-devel@lists.freedesktop.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Date: Wed, 13 May 2026 16:53:11 +0200 In-Reply-To: References: <20260512110339.6244-1-thomas.hellstrom@linux.intel.com> <20260512110339.6244-2-thomas.hellstrom@linux.intel.com> <26479389-459b-4cc4-914d-e7d29d5e5cc9@kernel.org> <1ce447ceea88bbe56c7d28654a51fc2856a7f986.camel@linux.intel.com> <65596f86-e6a3-48b0-aa3d-2e608964e29d@kernel.org> Organization: Intel Sweden AB, Registration Number: 556189-6027 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.58.3 (3.58.3-1.fc43) MIME-Version: 1.0 X-BeenThere: intel-xe@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel Xe graphics driver List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-xe-bounces@lists.freedesktop.org Sender: "Intel-xe" On Wed, 2026-05-13 at 13:36 +0200, David Hildenbrand (Arm) wrote: > On 5/13/26 12:37, Thomas Hellstr=C3=B6m wrote: >=20 >=20 > >=20 [...] > > One alternative would be a single large sparse shmem object common > > for > > all DRM objects, with a range allocator, but that also got pretty > > ugly > > when I tried to implement that. >=20 > Does not sound too crazy, though. >=20 > >=20 Yeah, I stumbled on finding a reasonable idea to connect a shmem folio to the pool LRUs and the range allocator metadata. Assuming a shmem folio is pinned using the memfd pinning interface, would folio->private be temporarily available? Thanks, Thomas