All of lore.kernel.org
 help / color / mirror / Atom feed
From: SJ Park <sj@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: SJ Park <sj@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Asier Gutierrez <gutierrez.asier@huawei-partners.com>,
	"Liam R. Howlett" <liam@infradead.org>,
	David Hildenbrand <david@kernel.org>,
	Jonathan Corbet <corbet@lwn.net>,
	Lorenzo Stoakes <ljs@kernel.org>, Michal Hocko <mhocko@suse.com>,
	Mike Rapoport <rppt@kernel.org>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Vlastimil Babka <vbabka@kernel.org>,
	damon@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v4 3/3] Docs/mm/damon/design: Document hugepage_mem_bp target metric
Date: Mon, 31 Aug 2026 17:47:11 -0700	[thread overview]
Message-ID: <20260901004712.89669-1-sj@kernel.org> (raw)
In-Reply-To: <107dc6ba-697e-4b25-ba3e-8ce2499cac9a@infradead.org>

On Mon, 31 Aug 2026 13:00:26 -0700 Randy Dunlap <rdunlap@infradead.org> wrote:

> 
> 
> On 8/31/26 8:45 AM, Randy Dunlap wrote:
> > Hi,
> > 
> > On 8/31/26 7:47 AM, SJ Park wrote:
> >> From: Asier Gutierrez <gutierrez.asier@huawei-partners.com>
> >>
> >> Document hugepage_mem_bp metric exposed by sysfs.
> >>
> >> Signed-off-by: Asier Gutierrez <gutierrez.asier@huawei-partners.com>
> >> Reviewed-by: SJ Park <sj@kernel.org>
> >> Signed-off-by: SJ Park <sj@kernel.org>
> >> ---
> >>  Documentation/mm/damon/design.rst | 2 ++
> >>  1 file changed, 2 insertions(+)
> >>
> >> diff --git a/Documentation/mm/damon/design.rst b/Documentation/mm/damon/design.rst
> >> index aed6cb1cf4831..a8c163475ef2b 100644
> >> --- a/Documentation/mm/damon/design.rst
> >> +++ b/Documentation/mm/damon/design.rst
> >> @@ -713,6 +713,8 @@ mechanism tries to make ``current_value`` of ``target_metric`` be same to
> >>    bp (1/10,000).
> >>  - ``node_eligible_mem_bp``: Scheme target access pattern-eligible memory ratio
> >>    of a node in bp (1/10,000).
> >> +- ``hugepage_mem_bp``: Total huge page to total used memory ratio in bp
> >> +  (1/10,000).
> >>  
> >>  ``nid`` is optionally required for ``node_mem_used_bp``, ``node_mem_free_bp``,
> >>  ``node_memcg_used_bp``, ``node_memcg_free_bp`` and ``node_eligible_mem_bp`` to
> > 
> > I've looked thru the entire design.rst file and cannot find anything telling
> > me (or anyone) what "bp" means.  Explain??
> 
> OK, I found it on the internet. I still think that it would be a
> good idea to say "basis point" one time (the first time that it is used).

You are right, and I agree.  I will add that clarification before the next
merge window.

> 
> 
> -- 
> ~Randy


Thanks,
SJ

  reply	other threads:[~2026-09-01  0:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-31 14:47 [PATCH v4 0/3] mm/damon: Introduce a huge page collapsing mechanism using auto tuning SJ Park
2026-08-31 14:47 ` [PATCH v4 1/3] mm/damon: Introduce DAMOS_QUOTA_HUGEPAGE " SJ Park
2026-08-31 18:16   ` sashiko-bot
2026-09-01  0:45     ` SJ Park
2026-09-01  6:58   ` Lian Wang
2026-09-01 14:23     ` SJ Park
2026-09-02  1:56       ` Lian Wang
2026-09-02  4:23         ` SJ Park
2026-09-02  5:12           ` wang lian
2026-09-02 15:03       ` Gutierrez Asier
2026-09-02 15:15         ` SJ Park
2026-08-31 14:47 ` [PATCH v4 2/3] mm/damon/sysfs: support hugepage_mem_bp quota goal metric SJ Park
2026-08-31 18:22   ` sashiko-bot
2026-09-01  0:46     ` SJ Park
2026-08-31 14:47 ` [PATCH v4 3/3] Docs/mm/damon/design: Document hugepage_mem_bp target metric SJ Park
2026-08-31 15:45   ` Randy Dunlap
2026-08-31 20:00     ` Randy Dunlap
2026-09-01  0:47       ` SJ Park [this message]
2026-09-01  5:20         ` Gutierrez Asier
2026-09-01  5:31           ` SJ Park
2026-08-31 18:35   ` sashiko-bot
2026-09-01  0:48     ` SJ Park
2026-09-01  0:49 ` [PATCH v4 0/3] mm/damon: Introduce a huge page collapsing mechanism using auto tuning SJ Park

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=20260901004712.89669-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=damon@lists.linux.dev \
    --cc=david@kernel.org \
    --cc=gutierrez.asier@huawei-partners.com \
    --cc=liam@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=rdunlap@infradead.org \
    --cc=rppt@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.