From: Jaewon Kim <jaewon31.kim@gmail.com>
To: "T.J. Mercier" <tjmercier@google.com>
Cc: Jaewon Kim <jaewon31.kim@samsung.com>,
Michal Hocko <mhocko@suse.com>,
jstultz@google.com, Sumit Semwal <sumit.semwal@linaro.org>,
daniel.vetter@ffwll.ch,
Andrew Morton <akpm@linux-foundation.org>,
hannes@cmpxchg.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] dma-buf/heaps: system_heap: avoid too much allocation
Date: Thu, 13 Apr 2023 07:10:49 +0900 [thread overview]
Message-ID: <CAJrd-Uuj7b7JhGK+3HW5aEc9HiTs0JMKGiQJuJ_Z6Z8za0j4Cw@mail.gmail.com> (raw)
In-Reply-To: <CABdmKX2fA2nXaSb8k+LE1yeso=ZnboDtxhzmjzrS35GSKv73hQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
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년 4월 13일 (목) 오전 1:49, T.J. Mercier <tjmercier@google.com>님이 작성:
> On Wed, Apr 12, 2023 at 4:38 AM Jaewon Kim <jaewon31.kim@samsung.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?!
>
[-- Attachment #2: Type: text/html, Size: 1402 bytes --]
next prev parent reply other threads:[~2023-04-12 22:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230410073304epcas1p4cf3079b096994d69472b7801bd530bc7@epcas1p4.samsung.com>
2023-04-10 7:32 ` [PATCH v3] dma-buf/heaps: system_heap: avoid too much allocation Jaewon Kim
2023-04-12 8:22 ` Michal Hocko
[not found] ` <CGME20230410073304epcas1p4cf3079b096994d69472b7801bd530bc7@epcms1p7>
2023-04-12 8:57 ` Jaewon Kim
2023-04-12 9:23 ` Michal Hocko
[not found] ` <CGME20230410073304epcas1p4cf3079b096994d69472b7801bd530bc7@epcms1p4>
2023-04-12 9:44 ` Jaewon Kim
2023-04-12 11:02 ` Michal Hocko
[not found] ` <CGME20230410073304epcas1p4cf3079b096994d69472b7801bd530bc7@epcms1p8>
2023-04-12 11:37 ` Jaewon Kim
2023-04-12 11:51 ` Michal Hocko
[not found] ` <CGME20230410073304epcas1p4cf3079b096994d69472b7801bd530bc7@epcms1p2>
2023-04-12 12:35 ` Jaewon Kim
2023-04-12 13:01 ` Michal Hocko
2023-04-12 16:49 ` T.J. Mercier
2023-04-12 22:10 ` Jaewon Kim [this message]
[not found] ` <CGME20230410073304epcas1p4cf3079b096994d69472b7801bd530bc7@epcms1p6>
2023-04-13 0:16 ` Jaewon Kim
2023-04-13 6:55 ` Michal Hocko
[not found] ` <CGME20230410073304epcas1p4cf3079b096994d69472b7801bd530bc7@epcms1p1>
2023-04-13 7:01 ` Jaewon Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJrd-Uuj7b7JhGK+3HW5aEc9HiTs0JMKGiQJuJ_Z6Z8za0j4Cw@mail.gmail.com \
--to=jaewon31.kim@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=daniel.vetter@ffwll.ch \
--cc=hannes@cmpxchg.org \
--cc=jaewon31.kim@samsung.com \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=sumit.semwal@linaro.org \
--cc=tjmercier@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).