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 4B4D6C77B6C for ; Wed, 12 Apr 2023 22:11:03 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id B3A5A900002; Wed, 12 Apr 2023 18:11:02 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id AEAE26B0075; Wed, 12 Apr 2023 18:11:02 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 98B78900002; Wed, 12 Apr 2023 18:11:02 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 83F3E6B0074 for ; Wed, 12 Apr 2023 18:11:02 -0400 (EDT) Received: from smtpin20.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay06.hostedemail.com (Postfix) with ESMTP id 3A890AB03F for ; Wed, 12 Apr 2023 22:11:02 +0000 (UTC) X-FDA: 80674135164.20.7541548 Received: from mail-ej1-f50.google.com (mail-ej1-f50.google.com [209.85.218.50]) by imf13.hostedemail.com (Postfix) with ESMTP id 6E60220011 for ; Wed, 12 Apr 2023 22:11:00 +0000 (UTC) Authentication-Results: imf13.hostedemail.com; dkim=pass header.d=gmail.com header.s=20221208 header.b=Ry1W4adv; spf=pass (imf13.hostedemail.com: domain of jaewon31.kim@gmail.com designates 209.85.218.50 as permitted sender) smtp.mailfrom=jaewon31.kim@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1681337460; 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=oufvjKKI2MUajaYKCTf5Z02edT7RtvxqCtYlGyFozHo=; b=uS8Kk8pd37VsCB7q0yT8F+yo6xTv4HoTMY1NeG2zpXy8+ydF2yi5p6PU7sPT3t1RXYqWRp bzW2nSYgsggL9DURTV4tdJTVKg9tLpLDES6G7xkqkTCBt0IwU6MlV9RHp1HR/TiESbI17C jh7qFIYRp22MME7iWsLQVP48akBHdFM= ARC-Authentication-Results: i=1; imf13.hostedemail.com; dkim=pass header.d=gmail.com header.s=20221208 header.b=Ry1W4adv; spf=pass (imf13.hostedemail.com: domain of jaewon31.kim@gmail.com designates 209.85.218.50 as permitted sender) smtp.mailfrom=jaewon31.kim@gmail.com; dmarc=pass (policy=none) header.from=gmail.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1681337460; a=rsa-sha256; cv=none; b=gFmwjRXG37rYPNltyqusb7j3dWAnKwSVHk0Ghf91p2SqIbX5zq6pvzuxP+iAUyl/H35H1s k5vCzminEMqCyzeCU74i64UFkMIBaPurB8M/IS/B1LAiImuw9omwvG+eZSPTPDuOo5W3zj djCjQKP+LjU814QqGxWJI/FOGAuWMDM= Received: by mail-ej1-f50.google.com with SMTP id os24so2897237ejb.12 for ; Wed, 12 Apr 2023 15:11:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1681337459; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=oufvjKKI2MUajaYKCTf5Z02edT7RtvxqCtYlGyFozHo=; b=Ry1W4advBq/dG8Sxmijig8UKnwgiTTMx6mhpqYYXJKozntBfzsN1FtZHGiqjGgjmYM 1RTOztJV4ZXTlGTWXbr5HHCQtkurkug7iB1i8KKPvy9helgVXOwIsuMaQNdpaVBHDGCf t6jPMeICmD1Ce71PAQys2EzctjZZ96qtHA0td4csGJECiLgHR5rcYG9EyjLkMTpvaMVf hNjZ7kO8lnd0TarWCiIPotTxR7fi9uu3af3tOgyMEYGmMTRrnaVjTDoZytql/NTVS4BB wEbMbTwjMLHusBAKK8nPBm4cqFZP53YAGzEhx2eoriCj1Ql0E4HqzkzTPcebhm0cgt0K BT3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681337459; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=oufvjKKI2MUajaYKCTf5Z02edT7RtvxqCtYlGyFozHo=; b=QwQGmFSA5cctUwsldywQHiSIVD/hXSqRGjb4LOoiP0OGC4Z9ypDAQGs1X2rp/6l/VW yIPVUCXu3mF29xqg5qYvXYiHP+tKLCy5xJ7sAsDE6LoSopsecHQkgl6bscYZt6zutqR6 0FHowuKyKc4YYXVRowv6U3Atn2sLIylvrtkmXoZ+ohbwMeYqSpAJ0OB0i4/AIo1udex2 /DXFqs23YYDDpP7cBDnjnpQZQBanOhCrx6ZJOfYOlLLnTDwUn4Pm9u3Mo1PL1Gqe2Onk xUwXWfAoRMOMjkiQA9ii9UcS3Oz9Fd46t3cenDA2mSxawmXQxO7TFDyw5T0BVTbgVKvy eRFg== X-Gm-Message-State: AAQBX9d24kxIPfiIHWrlEURZb2T/6li6P9O1cKOy/zNtuE2XFQki3WEy hEOZ7EpRac+il9kkoJYZlyIjgNsM/3ovbtL8SwM= X-Google-Smtp-Source: AKy350aKZmff9BGhBUKinW1sQgsBVQZiNP8dsWfuC6Mrwq5MTw5g0W17W5tgvDDkaHtedcdxNI/niXJCMoEOgkXoLWo= X-Received: by 2002:a17:906:8403:b0:931:fb3c:f88d with SMTP id n3-20020a170906840300b00931fb3cf88dmr221218ejx.5.1681337458688; Wed, 12 Apr 2023 15:10:58 -0700 (PDT) MIME-Version: 1.0 References: <20230410073228.23043-1-jaewon31.kim@samsung.com> <20230412085726epcms1p7d2bec2526e47bd10a3b6ea6a113c9cc3@epcms1p7> <20230412094440epcms1p445319579ead0d0576bb616ebb07501b4@epcms1p4> <20230412113759epcms1p8cb15b54e3a96c7616419cb030d16f804@epcms1p8> In-Reply-To: From: Jaewon Kim Date: Thu, 13 Apr 2023 07:10:49 +0900 Message-ID: Subject: Re: [PATCH v3] dma-buf/heaps: system_heap: avoid too much allocation To: "T.J. Mercier" Cc: Jaewon Kim , Michal Hocko , jstultz@google.com, Sumit Semwal , daniel.vetter@ffwll.ch, Andrew Morton , hannes@cmpxchg.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Content-Type: multipart/alternative; boundary="000000000000f905e305f92ae174" X-Rspamd-Server: rspam07 X-Rspamd-Queue-Id: 6E60220011 X-Rspam-User: X-Stat-Signature: duhtozgfsx3gj4phskp51jxrhp8y84zp X-HE-Tag: 1681337460-578122 X-HE-Meta: U2FsdGVkX1/TvIO8fKjRkEw+xEWx5FTywqxHcENrIkcEDmIvZRu+AjerNbY3TpA5xPIyWbgCvIpmofVF1Bgtn9MuaB7BD0GdlKpTxX7WtHykPn1li8986u7/MD+0gPXB3Ll4xHeycpqc75SW9bEUPr1CoQjsw+qtgHZ8QIiAR1hCRDWDGfJBV1y/0Wi9TjZImClkEJPLqqqZwAr8FpbhkdXChKRa1JGurFGC+7LJiYiln4Jkc98dCsdvlmI4Y9J/NvQpzcbwaOGiMc/2cnvdshQgqwhYP56h6OEKo0tC4YijlSmwugNGsFQrxgWpILFdCcc7czOIujfDN07FyBMRqdeoCdo/0qxh5I9T4RGYC0nm/yFa5Aj0sHhkVfMl1tyzDOTg/yxs0qQ9ilE4Jy4hy4h7dAdL/fQy/m1t79uLjoax9xOAW7DUObSd4xUjY6uGbP3VdA5h4qWteb3IFXrkcjWou2tBxy7val3vgnVX5jDxhDucm6LhsMpzvEp5jD7fcOrAg+sezEkLAGxPot2Cl+JRajd6OqcWxTemT2vaI57HcWJM4/GigMjg3BLa39pGY8z/42x0fr9TRA8KC36IihiCMNIMIqBcWISX5ghiGQxzc5S+b9rCB+pGkjTlhNFHlJrFHuU7JVy/l4sFNXcXSOvBmJ7F+TIBnIjiy7poGJ39sMILItkvfGxpri9xOgSxHW7U6g2MbW/Pyuhaj8gkgu02anxbPcGMjcnrbYEl4e4mxRjFEWkvT5sT+XCgZPbCX1FxKmvfPevF/qm3fsJsxMiUHk+UFJSpH8xaBP6kAydqB/LxQXCngnU/1SWUxW21R070znwKF6Z6bqwpOd68ZL+//bPf1srW5WcRht5SKYGcxu9pYGnSyTHn7oYTtvQmVgHwxLZIjLPHj6DhGO9oJHRf6m/nRqHtaDSn+kswcKy5VCH5KkulTIvg/66Mb3hZKkJD74wLhDLzTDis1aq q5d4Tc1g Y/qgOU1tJNHRG9LTYYe/5YpwHglOCIQNy9K1K0gRrgHzP/EuQAKlJTVxRHqrripltavykMWIAhsBCiU6IJPfdUXj6tOruGbsfi3eS/ZXv37+AcG7bjl5hO2Lm5z8O6F2If+eIpplKdTFbyAp1cB16E55FP0mxTPcxGNJJ/jFaIA1le7YiwSwGd3X8w75nJclH0EDIprF+2KaBj5yOH30mgPd0p0NEbnIWKkjBs6MvI7JT8k+/JH63XaT7cdbc425vv0K9IRecpA5ShxHMVvEQpkS+uldB8K9BI99HAd2LtjGMexU67rf2e+2yKDHlveGAsVpk0PrrSUXozNmoprlgBdoFLlrdX14oho0e0pC/r6wK0emVbKV79AiANnwih9800znfCoFpDjwaqMKaYGekfTn8L1hXCRjXMVANrO0MI7fWRb4YmRauiguetfCXUrsrWWf+HH0GYFi2G+NwnyXJlodrZArBwsBGgzM1TQnHhLiIBqm4+ft4GcKbeijKTlbVZ+vD7uu3vRfVXsLilWqa12ON6mxKEqR+OE9NHJ3czkXLagvFgyOmGv/2hUVOcwYUZ93WN100m6uUaOGgucjqpuIifg== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000129, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: --000000000000f905e305f92ae174 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It was one of camera scenarios. I internally asked and heard that was not a bug but normal. I think 2GB looks too big for one graphics buffer but it could be for other purposes like camera. I think the system heap should support that. 2023=EB=85=84 4=EC=9B=94 13=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 1:49, T= .J. Mercier =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1: > On Wed, Apr 12, 2023 at 4:38=E2=80=AFAM Jaewon Kim > wrote: > > > Yes I think you're right. As a allocator, dma-buf system heap looks to > be loose > > in memory allocation. Limiting dmabuf memory may be required. But I > think there > > is no nice and reasonable way so far. And the dma-buf system heap is > being > > widely used in Android mobile system. AFAIK the camera consumes huge > memory > > through this dma-buf system heap. I actually even looked a huge size > request > > over 2GB in one dma-buf request. > > > Hey can you point me to where you saw a request that big? That's a > non-buggy request?! > --000000000000f905e305f92ae174 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It was one of camera scenarios. I internally asked a= nd heard that was not a bug but normal. I think 2GB looks too big for one g= raphics buffer but it could be for other purposes like camera. I think the = system heap should support that.

2023=EB=85= =84 4=EC=9B=94 13=EC=9D=BC (=EB=AA=A9) =EC=98=A4=EC=A0=84 1:49, T.J. Mercie= r <tjmercier@google.com>= =EB=8B=98=EC=9D=B4 =EC=9E=91=EC=84=B1:
On Wed, Apr 12, 2023 at 4:38=E2=80=AFAM Jaewon Kim <jaewon31.k= im@samsung.com> wrote:

> Yes I think you're right. As a allocator, dma-buf system heap look= s to be loose
> in memory allocation. Limiting dmabuf memory may be required. But I th= ink there
> is no nice and reasonable way so far. And the dma-buf system heap is b= eing
> widely used in Android mobile system. AFAIK the camera consumes huge m= emory
> through this dma-buf system heap. I actually even looked a huge size r= equest
> over 2GB in one dma-buf request.
>
Hey can you point me to where you saw a request that big? That's a
non-buggy request?!
--000000000000f905e305f92ae174--