Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <ZDZ4j7UdBt32j28J@dhcp22.suse.cz> <ZDZqYTSHBNGLq0zI@dhcp22.suse.cz>
 <20230410073228.23043-1-jaewon31.kim@samsung.com> <20230412085726epcms1p7d2bec2526e47bd10a3b6ea6a113c9cc3@epcms1p7>
 <20230412094440epcms1p445319579ead0d0576bb616ebb07501b4@epcms1p4>
 <CGME20230410073304epcas1p4cf3079b096994d69472b7801bd530bc7@epcms1p8>
 <ZDaP4/PYyb9tKGQi@dhcp22.suse.cz> <20230412113759epcms1p8cb15b54e3a96c7616419cb030d16f804@epcms1p8>
In-Reply-To: <20230412113759epcms1p8cb15b54e3a96c7616419cb030d16f804@epcms1p8>
From:   "T.J. Mercier" <tjmercier@google.com>
Date:   Wed, 12 Apr 2023 09:49:19 -0700
Message-ID: <CABdmKX2fA2nXaSb8k+LE1yeso=ZnboDtxhzmjzrS35GSKv73hQ@mail.gmail.com>
Subject: Re: [PATCH v3] dma-buf/heaps: system_heap: avoid too much allocation
To:     jaewon31.kim@samsung.com
Cc:     Michal Hocko <mhocko@suse.com>,
        "jstultz@google.com" <jstultz@google.com>,
        "sumit.semwal@linaro.org" <sumit.semwal@linaro.org>,
        "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
        "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
        "hannes@cmpxchg.org" <hannes@cmpxchg.org>,
        "linux-mm@kvack.org" <linux-mm@kvack.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "jaewon31.kim@gmail.com" <jaewon31.kim@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Wed, Apr 12, 2023 at 4:38=E2=80=AFAM Jaewon Kim <jaewon31.kim@samsung.co=
m> 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 bein=
g
> widely used in Android mobile system. AFAIK the camera consumes huge memo=
ry
> through this dma-buf system heap. I actually even looked a huge size requ=
est
> 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?!