From: Andrew Morton <akpm@linux-foundation.org>
To: Xiang Gao <gxxa03070307@gmail.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
gaoxiang17 <gaoxiang17@xiaomi.com>
Subject: Re: [PATCH] mm/cma: print total and used count in cma_alloc()
Date: Thu, 26 Sep 2024 13:25:34 -0700 [thread overview]
Message-ID: <20240926132534.8bd3acaf379ab592770e0d1b@linux-foundation.org> (raw)
In-Reply-To: <20240926120049.321514-1-gxxa03070307@gmail.com>
On Thu, 26 Sep 2024 20:00:49 +0800 Xiang Gao <gxxa03070307@gmail.com> wrote:
> before:
> [ 24.407814] cma: cma_alloc(cma (____ptrval____), name: reserved, count 1, align 0)
> [ 24.413397] cma: cma_alloc(cma (____ptrval____), name: reserved, count 1, align 0)
> [ 24.415886] cma: cma_alloc(cma (____ptrval____), name: reserved, count 1, align 0)
>
> after:
> [ 24.097989] cma: cma_alloc(cma (____ptrval____), name: reserved, total count 16384, used count: 64, request count 1, align 0)
> [ 24.104260] cma: cma_alloc(cma (____ptrval____), name: reserved, total count 16384, used count: 65, request count 1, align 0)
> [ 24.107504] cma: cma_alloc(cma (____ptrval____), name: reserved, total count 16384, used count: 66, request count 1, align 0)
OK, thanks. We should explain why we're making this change! The
previous version of the patch had "To better understand cma area during
debugging", but that isn't very specific.
Please tell us the use case - why is this information helpful? How is
it used?
next prev parent reply other threads:[~2024-09-26 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 12:00 Xiang Gao
2024-09-26 20:25 ` Andrew Morton [this message]
2024-09-27 12:30 ` David Hildenbrand
2024-09-28 1:04 ` 答复: [External Mail]Re: " 高翔
2024-09-28 8:30 ` David Hildenbrand
2024-09-29 2:52 ` 答复: " 高翔
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=20240926132534.8bd3acaf379ab592770e0d1b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gaoxiang17@xiaomi.com \
--cc=gxxa03070307@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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