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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8706CC54EBC for ; Thu, 12 Jan 2023 08:13:43 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 239F48E0003; Thu, 12 Jan 2023 03:13:43 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 1E99D8E0001; Thu, 12 Jan 2023 03:13:43 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 08AD08E0003; Thu, 12 Jan 2023 03:13:43 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id EAD7B8E0001 for ; Thu, 12 Jan 2023 03:13:42 -0500 (EST) Received: from smtpin05.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay05.hostedemail.com (Postfix) with ESMTP id B42324074D for ; Thu, 12 Jan 2023 08:13:42 +0000 (UTC) X-FDA: 80345433084.05.AC73ADA Received: from mail-pj1-f74.google.com (mail-pj1-f74.google.com [209.85.216.74]) by imf15.hostedemail.com (Postfix) with ESMTP id 27E01A0011 for ; Thu, 12 Jan 2023 08:13:40 +0000 (UTC) Authentication-Results: imf15.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=RGhd7Gam; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf15.hostedemail.com: domain of 3M8G_YwgKCNgMB4E88F5AIIAF8.6IGFCHOR-GGEP46E.ILA@flex--shakeelb.bounces.google.com designates 209.85.216.74 as permitted sender) smtp.mailfrom=3M8G_YwgKCNgMB4E88F5AIIAF8.6IGFCHOR-GGEP46E.ILA@flex--shakeelb.bounces.google.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1673511221; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=VWdRXf2+F3B6naWulQRoVncCtgT+T33N/C9h1MKyUek=; b=v0+SaUm+4JMInf+0ZzkFTOBxkfJLPP+pFhvH6eNz1LVt89saVA0I/y9L9qaIOX8xkZmeFb cV06lrHxrVxFl2llR3tKE6a5gPiIjAOe9NhKnuo1BueInTfKkSPL2uly84bTjGru6+eH8u 0zBgWHdetdWhELcVP3em1P5aVL2WLFI= ARC-Authentication-Results: i=1; imf15.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=RGhd7Gam; dmarc=pass (policy=reject) header.from=google.com; spf=pass (imf15.hostedemail.com: domain of 3M8G_YwgKCNgMB4E88F5AIIAF8.6IGFCHOR-GGEP46E.ILA@flex--shakeelb.bounces.google.com designates 209.85.216.74 as permitted sender) smtp.mailfrom=3M8G_YwgKCNgMB4E88F5AIIAF8.6IGFCHOR-GGEP46E.ILA@flex--shakeelb.bounces.google.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1673511221; a=rsa-sha256; cv=none; b=j45t5e4wgjvY1R+SEabU1OvMNwJ7MCJ/QAZGXnRg/yUl9/ukbhcif+Ny5ON8ZyTS+B2CV2 hD19KRVUbBq9w8gde4oIMiUEaBmyMQtVCt1Ixt83FLcuepYvP8R4QT5cidpkQUtvDltAc3 YvDwpywQ7+vt9Q/pf6b5NNnlcdDg0MQ= Received: by mail-pj1-f74.google.com with SMTP id r17-20020a17090aa09100b0021903e75f14so7677187pjp.9 for ; Thu, 12 Jan 2023 00:13:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=VWdRXf2+F3B6naWulQRoVncCtgT+T33N/C9h1MKyUek=; b=RGhd7Gam36sQbHlynE0qAtHIsyX4aCLddPEY2Ot/Dgnedc14Puqc+N15BF4HB1+p/F EyiFI8PkNHaolrVoe7QK5BM3CZp8vk6W4pTXG5t695yYCvf//btA1VGQaXM5Z9EWJrrS xLHhPHGK7LgyKGGfWBnGBtXkZ8Wr4/C7eaUCkaE01oIFkojxBDOH6PCPZu8BNx5Djp6V IfwRrmeF7rOuyASGIPSCTwqUXba95DqJIXmf+I/r32QKtPTm9Z4todzk318w55UFVqKx +j/E0vEN9DOhznh8mKC4jQPd/KfjI32B1A83D6ZGmdcx152TXiUUGw3Pro8wO5zpPEJ8 n0bQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=VWdRXf2+F3B6naWulQRoVncCtgT+T33N/C9h1MKyUek=; b=fpHNJ0SAc+41WFknv3Lgz4UoCfMKF8LZ6rFI2eIfL1xo8KqofOjO5g8muB+kwcx55Q 8VjExLVsV+jMvYdqqZ57Bkg1GADvrqoKzapCM9s2dSSGIps1e03cxo4Ib3dy+WHB6b0o 79X572Lqlb3dIRtqkLSfiYAmgL3Go3/PS9uex3m56umssO8op3nCmijMAWxQc9hVc6j/ OK18Xi/HEnHC/abi0OufGlbGixdzicLtCKJgtGVO9xDlSSAwX4BWVad4DrAgvLem2ic3 xPwe8y991xsDSd8Jfq05b4DakTBb91KuKrXgfq1DLvmj8jM+jbXB9AA9/IdTZoKYIINy LS4Q== X-Gm-Message-State: AFqh2kpKzpHOUKylAKd1jA74Ep6h5mRIWlC5aBTfY2vPF6n9pnQmDvPi ZW7EneIxI4V7CDPnqsgSxrddDH8Zw7Hnag== X-Google-Smtp-Source: AMrXdXsnUERgCx1wBY/PUV43pyxeJkOgHSEhh4R8ej3lO942bcK1tz6HE+NyNfEUpzC5WGguaBo2zTGHvm8JZA== X-Received: from shakeelb.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:262e]) (user=shakeelb job=sendgmr) by 2002:a05:6a00:1244:b0:56b:8181:fe3e with SMTP id u4-20020a056a00124400b0056b8181fe3emr5060573pfi.57.1673511219777; Thu, 12 Jan 2023 00:13:39 -0800 (PST) Date: Thu, 12 Jan 2023 08:13:37 +0000 In-Reply-To: Mime-Version: 1.0 References: <20230109213809.418135-1-tjmercier@google.com> Message-ID: <20230112081337.fxgnhdk44mxu26et@google.com> Subject: Re: [PATCH 0/4] Track exported dma-buffers with memcg From: Shakeel Butt To: "T.J. Mercier" Cc: Tejun Heo , Zefan Li , Johannes Weiner , Jonathan Corbet , Greg Kroah-Hartman , "Arve =?utf-8?B?SGrDuG5uZXbDpWc=?=" , Todd Kjos , Martijn Coenen , Joel Fernandes , Christian Brauner , Carlos Llamas , Suren Baghdasaryan , Sumit Semwal , "Christian =?utf-8?B?S8O2bmln?=" , Michal Hocko , Roman Gushchin , Muchun Song , Andrew Morton , Paul Moore , James Morris , "Serge E. Hallyn" , Stephen Smalley , Eric Paris , android-mm@google.com, jstultz@google.com, cgroups@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org, linux-mm@kvack.org, linux-security-module@vger.kernel.org, selinux@vger.kernel.org, daniel.vetter@ffwll.ch Content-Type: text/plain; charset="us-ascii" X-Rspamd-Queue-Id: 27E01A0011 X-Rspamd-Server: rspam09 X-Rspam-User: X-Stat-Signature: j6ut8qp6ojjmnnczbrqfrje1ab88scfi X-HE-Tag: 1673511220-844366 X-HE-Meta: U2FsdGVkX184mHNhI86aUlAw8ksEpQlmhnd4YwcJh3A+L36Y2G940Ew3Bhk6NEUppSAq9enUlZ/ZNQ/1TOblLAdr5vv0UID6KGbS9web+u4QRi1jRg3ffIR5+GyPIBeLE7nT9wro2B1qjUVw1inwmNSyTSnS4UliJ3OxbQr2xH/biTQR5cN4OMMmMS80uDK44c5Xe05XFF9uKq0nRwl7HDOs/V1DfKWA4pu/4CTiWVgz0+RVGhv3ko2/YVCOUiPHzZed6g92Cohlw6sgKhkWSYS2gJsaSS/T18W+5L6Hqn2eGkx0B6Jyame1lKmzHDLw8poKavwWy36GpYqJzgxpWVOHttjWXGhHTpPN5X62TurJfcYX5i36oK20eaC2M002tD8qNBqvzVetX7u5hlcDoOmKe1dzjl2w3zEj9STdn0lvzx//c61WCdafklCYOjiG4whS651eTH1Xaw9Jpbu+aCb7k3gkRMbL9rqkm9ohd6DqEU2wHOWghu/xJ7BjGXvVk3S6BF4M6CWeG2xdSqLSb5sV1WtmEBnZFIyLi6QRVVlheq2xbNG3di09am07lILi+znqKud4nSeN2jyvmZTNImHogx1QKdu5dAkMbzZ/y2Uixl5+/W62aTdtVM0Y8j6S913e4ocYhX5XYSDrbXFtb7ssvo1++cqaE1EMZqUdNsQo7Z1j5Tp233cpkVk79yraW7rc9hCKMy1t5hAOz3AUjJdyyzxmob1+cnv0LmrkL8+cZTc593WfwqPn8UH8mwdgx7JhGgAXvolFT9fagKv1Bzz9fssK3VlWt86B7+TzRjWaZTiN4pEVR7dTzWTix85I17PEjPIQx15TaF8s0l8MdHJqpZJ2aE8Xkz0q9/nrGAWy1HfhuWR2z0EkEkxVlLUcHEtx1qTOT9n/nRjkO08pISFC+TtL1kzPh+7qicURkPojxyeyf243q4T/5DhVmRjguLB2QcvwxLQ1QJvAnO+ Leix3yiP MPixYe8fC76uRj9KuyKQ8JNACMk3jTNDW9NufwHTLcOekdq3/8rhAGGiht6biYFByDRXkI1YkTydWoqBA/HhOvrR47Rq+j4hINVN156oGuAfULtcYv133s6gYEt7M8/QtuidkfWfxqpLOx+RHnIIJrYa6NYAsKXSrJPuGTUX/sasNy7nscHmENj5T3LWy8yv+5HTFlHQifJkiwIiytjmcisKbda7hRLohC19SROOigaMWpKstkwHBnvcoxoKZ0UYXjVB1vHXsXZwrLAbD8Ad2mn3Mg+xN/gnJTnQX4ugaO96q/Q6lPgWG5u5ePp7svDb67aLaPTZtOy14XDpBiycFb0c+s3gZGuuHSIlsDHWrYQ00CGUhAF9MeunapQB9Fuf9PLtXVJzOdR1HZw7z7NKiHGoSOcQeGpww1yXuC7VAMqohnPzOO0AZxLAVG1sfjJ3PxHpfSwffNRM58I8= 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: On Wed, Jan 11, 2023 at 04:49:36PM -0800, T.J. Mercier wrote: > [...] > > The problem is a bit that with gpu allocations reclaim is essentially "we > > pass the error to userspace and they get to sort the mess out". There are > > some exceptions (some gpu drivers to have shrinkers) would we need to make > > sure these shrinkers are tied into the cgroup stuff before we could enable > > charging for them? > > > I'm also not sure that we can depend on the dmabuf being backed at > export time 100% of the time? (They are for dmabuf heaps.) If not, > that'd make calling the existing memcg folio based functions a bit > difficult. > Where does the actual memory get allocated? I see the first patch is updating the stat in dma_buf_export() and dma_buf_release(). Does the memory get allocated and freed in those code paths?