From: Andrew Morton <akpm@linux-foundation.org>
To: 高翔 <gaoxiang17@xiaomi.com>
Cc: Frank van der Linden <fvdl@google.com>,
David Hildenbrand <david@redhat.com>,
Xiang Gao <gxxa03070307@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: 回复: [External Mail]Re: [PATCH v2] mm/cma: print total and used count in cma_alloc()
Date: Fri, 4 Oct 2024 15:39:47 -0700 [thread overview]
Message-ID: <20241004153947.43c5b16b7f75b0f60e918019@linux-foundation.org> (raw)
In-Reply-To: <2a7b7fc3a48d4bb9a6394e51af074017@xiaomi.com>
On Fri, 4 Oct 2024 12:23:30 +0000 高翔 <gaoxiang17@xiaomi.com> wrote:
> > > +static unsigned long cma_get_used_pages(struct cma *cma) {
> > > + unsigned long used;
> > > +
> > > + spin_lock_irq(&cma->lock);
> > > + used = bitmap_weight(cma->bitmap, (int)cma_bitmap_maxno(cma));
> > > + spin_unlock_irq(&cma->lock);
> >
> > This adds overhead to each allocation, even if debug outputs are
> > ignored I assume?
> >
> > I wonder if we'd want to print these details only when our allocation
> > failed?
> >
> > Alternatively, we could actually track how many pages are allocated in
> > the cma, so we don't have to traverse the complete bitmap on every
> > allocation.
> >
>
> Yep, that's what I did as part of
> https://lore.kernel.org/all/20240724124845.614c03ad39f8af3729cebee6@linux-foundation.org/T/
>
> That patch didn't make it in (yet). I'm happy for it to be combined with this one if that's easier.
That patch has been forgotten about. As I asked in July,
"I suggest a resend, and add some Cc:s for likely reviewers."
next prev parent reply other threads:[~2024-10-04 22:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-29 3:27 Xiang Gao
2024-09-30 9:34 ` David Hildenbrand
2024-10-02 19:50 ` Frank van der Linden
2024-10-04 12:23 ` 回复: [External Mail]Re: " 高翔
2024-10-04 22:39 ` Andrew Morton [this message]
2024-10-04 22:55 ` Frank van der Linden
2024-10-10 8:48 ` 答复: " 高翔
2024-10-10 21:17 ` Andrew Morton
2024-10-11 2:25 ` 答复: " 高翔
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=20241004153947.43c5b16b7f75b0f60e918019@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=fvdl@google.com \
--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