linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>, rppt@kernel.org
Cc: akiyks@gmail.com, akpm@linux-foundation.org, corbet@lwn.net,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	skhan@linuxfoundation.org, yejiajian2018@email.szu.edu.cn,
	zhangyinan2019@email.szu.edu.cn
Subject: Re: [PATCH v2] Documentation/mm/page_owner.rst: delete frequently changing experimental data
Date: Wed, 5 Oct 2022 16:32:23 +0700	[thread overview]
Message-ID: <89aed08f-1e0b-258c-516d-97a30fd02840@gmail.com> (raw)
In-Reply-To: <20221005091052.6631-1-caoyixuan2019@email.szu.edu.cn>

On 10/5/22 16:10, Yixuan Cao wrote:
> Thanks for Jonathan Corbet, Bagas Sanjaya and Mike Rapoport's
> constructive suggestions. Notice that the size(1) output is
> changing frequently, I remove the two tables and describe them
> in a general way. Doing so avoids having to repeatedly maintain
> the two tables due to kernel changes.
> 

For the patch description, better write:

"The kernel size changes due to many factors, such as compiler
 version, configuration, and the build environment. This makes
 size comparison figures irrelevant to reader's setup.

 Remove these figures and describe the effects of page owner
 to the kernel size in general instead."

> Signed-off-by: Yixuan Cao <caoyixuan2019@email.szu.edu.cn>
> ---
>  Documentation/mm/page_owner.rst | 20 ++++----------------
>  1 file changed, 4 insertions(+), 16 deletions(-)
> 
> diff --git a/Documentation/mm/page_owner.rst b/Documentation/mm/page_owner.rst
> index f18fd8907049..1b661ad85647 100644
> --- a/Documentation/mm/page_owner.rst
> +++ b/Documentation/mm/page_owner.rst
> @@ -38,22 +38,10 @@ not affect to allocation performance, especially if the static keys jump
>  label patching functionality is available. Following is the kernel's code
>  size change due to this facility.
>  
> -- Without page owner::
> -
> -   text    data     bss     dec     hex filename
> -   48392   2333     644   51369    c8a9 mm/page_alloc.o
> -
> -- With page owner::
> -
> -   text    data     bss     dec     hex filename
> -   48800   2445     644   51889    cab1 mm/page_alloc.o
> -   6662     108      29    6799    1a8f mm/page_owner.o
> -   1025       8       8    1041     411 mm/page_ext.o
> -
> -Although, roughly, 8 KB code is added in total, page_alloc.o increase by
> -520 bytes and less than half of it is in hotpath. Building the kernel with
> -page owner and turning it on if needed would be great option to debug
> -kernel memory problem.
> +Although, enabling page owner increases kernel size by several kilobytes,
> +most of this code is outside page allocator and its hot path. Building 
> +the kernel with page owner and turning it on if needed would be great
> +option to debug kernel memory problem.
>  

s/Although,/Although/

Thanks for reviewing.

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2022-10-05  9:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25 17:29 [PATCH] Documentation/mm/page_owner.rst: update experimental data Yixuan Cao
2022-08-25 18:09 ` Jonathan Corbet
2022-08-26  2:30   ` Bagas Sanjaya
2022-08-26  4:16     ` Mike Rapoport
2022-10-05  9:10       ` [PATCH v2] Documentation/mm/page_owner.rst: delete frequently changing " Yixuan Cao
2022-10-05  9:32         ` Bagas Sanjaya [this message]
2022-10-05 11:38           ` [PATCH v3] " Yixuan Cao
2022-10-05 14:55           ` [PATCH v4] " Yixuan Cao
2022-10-06  1:46             ` Bagas Sanjaya
2022-10-06  4:05               ` [PATCH v5] " Yixuan Cao
2022-10-10 18:54             ` [PATCH v4] " Jonathan Corbet

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=89aed08f-1e0b-258c-516d-97a30fd02840@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=akiyks@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=caoyixuan2019@email.szu.edu.cn \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rppt@kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=yejiajian2018@email.szu.edu.cn \
    --cc=zhangyinan2019@email.szu.edu.cn \
    /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).