From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (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 D63CF1465A5 for ; Thu, 31 Oct 2024 16:45:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=170.10.129.124 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730393132; cv=none; b=kl5ka7cS4Y9OD1Oh4aJsbcpeAG+NeR6PMpSGV4xkWKba5OYnXwX4X0UBW3Xdhzto+NZlEXe1KJsmGs3g+2KR8LCpy/vofNhutPSNqZGDO/aGrs+RyfoJw81r/Blh8IEwrfhE+ZiZSdWVILol8tIveh2zuTR/R6VIFbWIMvqUSgI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1730393132; c=relaxed/simple; bh=182pqmxJKzOagD+mCIwZct3+5F1kCCVclBMGYB3B2rI=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=o8qu1vn0KujAVsLeMhRLjB6OAVLXjI0Y38/6amp/kZUQxDInfXYshdhpg+ipcRdCvvOvRBwBCnryRfRirZWQu1hukKGFZ1NvvLcYEsgPZ91LiRIk6RzqGk+7tZiDcCJwOjNGqsyBd2ftwSfoyzgZQ5uiTRGw3j9c5YSsqsXAxK0= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com; spf=pass smtp.mailfrom=redhat.com; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b=aBswaGvq; arc=none smtp.client-ip=170.10.129.124 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=redhat.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="aBswaGvq" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1730393128; 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=182pqmxJKzOagD+mCIwZct3+5F1kCCVclBMGYB3B2rI=; b=aBswaGvqANU5ZUKMAoBLsi86BtGX+Tz6OC0eZc9pKXrZ7WPt03Eqpb4DluQsGOD6z2ENb9 TU0pR7h32nxULGXUyYmViY0cB3Ht1O16J38+hF6fMtF+QDP2VE+PXuynqWVFvVylbECaPB GsvUOsqf/zmXhb7TaeZO5KPrIqkkKKg= Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-435-hgweYrBWOBaMpp6ff-izDQ-1; Thu, 31 Oct 2024 12:45:26 -0400 X-MC-Unique: hgweYrBWOBaMpp6ff-izDQ-1 Received: by mail-lj1-f200.google.com with SMTP id 38308e7fff4ca-2fb652f40f1so7039241fa.2 for ; Thu, 31 Oct 2024 09:45:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1730393125; x=1730997925; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=182pqmxJKzOagD+mCIwZct3+5F1kCCVclBMGYB3B2rI=; b=A0t1xRAfPA52krtlgwLNnKjlBahWu11i5HryXZJ0qIQK0KTP+Pn4UhLqSzyCsdjzSt r+aakEOr6Q21PsLB3wsCa7mBlhFeO+AD44o3oREqR1vRuUtCIvBxmRAGJC6hAjS7XSEl VFfPb90DD3QiZ8UHIBe/Vw6cNvr7kR1bWJwOut/1b/vv1moXUEei5Ez8fywd4P++qoMS pfOpDZoWHIfIyIA74pUFxewL3P2I4uXbvX/PP2UYJ3Wv2UL863XuTpqf14vWh04RDmaH VqDciFl+4LGmd3Weu1W26aWF6VJEoiz9j8QBTJZXe8sit3IDPsLe3xvCRH8e2bDa5kQ0 hhFQ== X-Forwarded-Encrypted: i=1; AJvYcCUAEI/9mty2pGWYnewfa4CyVT6cO+OPq0OAvMzTuKcblGtws3HjhSg740+QLOahzQMojUHtEfUCOJyCwQ==@vger.kernel.org X-Gm-Message-State: AOJu0YyhMS6CHACnN35pjhhm2InEWYfCA87HsEWBdrd8BM0FLOH6jq4i uX5k/FIa7er5WGXdm/LDx1fjANCPtl+yQu6/HzQZT1o5tqOufTvo17H29DUvxFuHJXTQ/v7XUsT NWnYHEPQcUhyyLGR3+POOlRNwwJSelSSLnBHdHPiDFXexKdBJVZFQn+hdJWeQ X-Received: by 2002:a05:6512:32c8:b0:535:82eb:21d1 with SMTP id 2adb3069b0e04-53d65e1781fmr431494e87.57.1730393125213; Thu, 31 Oct 2024 09:45:25 -0700 (PDT) X-Google-Smtp-Source: AGHT+IHouLo3TF+7LJo+6trZy9gzmL/37JvOLD2BMFURyxuRnX3R17ZHSmy2W/qUwbYYI/LTZymFXg== X-Received: by 2002:a05:6512:32c8:b0:535:82eb:21d1 with SMTP id 2adb3069b0e04-53d65e1781fmr431467e87.57.1730393124704; Thu, 31 Oct 2024 09:45:24 -0700 (PDT) Received: from localhost ([2a01:e0a:b25:f902::ff]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-381c10d4342sm2618972f8f.32.2024.10.31.09.45.24 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 31 Oct 2024 09:45:24 -0700 (PDT) Date: Thu, 31 Oct 2024 17:45:23 +0100 From: Maxime Ripard To: metux Cc: Sumit Semwal , Benjamin Gaignard , Brian Starkey , John Stultz , "T.J. Mercier" , Christian =?utf-8?B?S8O2bmln?= , linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org Subject: Re: Requirements to merge new heaps in the kernel Message-ID: <20241031-bouncy-cute-shrimp-cd2530@houat> References: <20241022-macaw-of-spectacular-joy-8dcefa@houat> <35deac48-4220-4889-833d-1b57b417e968@gmx.de> Precedence: bulk X-Mailing-List: linux-media@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha384; protocol="application/pgp-signature"; boundary="e7ghtd5lwxlkxgfh" Content-Disposition: inline In-Reply-To: <35deac48-4220-4889-833d-1b57b417e968@gmx.de> --e7ghtd5lwxlkxgfh Content-Type: text/plain; protected-headers=v1; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Subject: Re: Requirements to merge new heaps in the kernel MIME-Version: 1.0 On Wed, Oct 30, 2024 at 12:16:22PM +0100, metux wrote: > On 22.10.24 10:38, Maxime Ripard wrote: > > I'm still interested in merging a carve-out driver[1], since it seems t= o be > > in every vendor BSP and got asked again last week. > >=20 > > I remember from our discussion that for new heap types to be merged, we > > needed a kernel use-case. Looking back, I'm not entirely sure how one > > can provide that given that heaps are essentially facilities for > > user-space. >=20 > For those who didn't follow your work, could you please give a short > intro what's that all about ? >=20 > If I understand you correctly, you'd like the infrastructure of > kmalloc() et al for things / memory regions that aren't the usual heap, > right ? No, not really. The discussion is about dma-buf heaps. They allow to allocate buffers suitable for DMA from userspace. It might or might not =66rom the system memory, at the heap driver discretion. > What's the practical use case ? GPU memory ? Shared memory between > nodes in a multi-CPU / cluster machine ? >=20 > Is it related to NUMA ? And since it's about DMA, it doesn't have much to do with CPUs either. Maxime --e7ghtd5lwxlkxgfh Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iJUEABMJAB0WIQTkHFbLp4ejekA/qfgnX84Zoj2+dgUCZyO0HQAKCRAnX84Zoj2+ dsaIAYDSLs4vqC2W23GWmQw+nLt61ihhhwXON5VrB1bS7hVzaX7P2Gu1Vl0ygras mpk+w40Bf2OSx3W0bmcLT2VATGEiKE8QZJt+N49J3WfSZwJOPvQjXudAGBe5XxGj WjSuaDPXug== =PFmP -----END PGP SIGNATURE----- --e7ghtd5lwxlkxgfh--