[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABdmKX2fA2nXaSb8k+LE1yeso=ZnboDtxhzmjzrS35GSKv73hQ@mail.gmail.com>
Date: Wed, 12 Apr 2023 09:49:19 -0700
From: "T.J. Mercier" <tjmercier@...gle.com>
To: jaewon31.kim@...sung.com
Cc: Michal Hocko <mhocko@...e.com>,
"jstultz@...gle.com" <jstultz@...gle.com>,
"sumit.semwal@...aro.org" <sumit.semwal@...aro.org>,
"daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"hannes@...xchg.org" <hannes@...xchg.org>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"jaewon31.kim@...il.com" <jaewon31.kim@...il.com>
Subject: Re: [PATCH v3] dma-buf/heaps: system_heap: avoid too much allocation
On Wed, Apr 12, 2023 at 4:38 AM Jaewon Kim <jaewon31.kim@...sung.com> 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?!
Powered by blists - more mailing lists