linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: yong w <yongw.pur@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"Peter Zijlstra (Intel)" <peterz@infradead.org>,
	mingo@kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>,
	yang.yang29@zte.com.cn, wang.yong12@zte.com.cn
Subject: Re: [PATCH v2 linux-next] delayacct: track delays from memory compact
Date: Tue, 14 Dec 2021 16:49:14 +1100	[thread overview]
Message-ID: <YbgwWir/Ymt/2gxE@balbir-desktop> (raw)
In-Reply-To: <CAOH5QeCO_EZzkU=B3L1=1OPiZa7XxnWZK87GbwXNOQXxZqYcoQ@mail.gmail.com>

On Mon, Dec 13, 2021 at 09:56:08PM +0800, yong w wrote:
> Hello,  is this patch OK?
> 
> Thanks.
> 
> yong w <yongw.pur@gmail.com> 于2021年12月8日周三 00:50写道:
> >
> > Balbir Singh <bsingharora@gmail.com> 于2021年12月7日周二 13:16写道:
> > >
> > > On Sun, Dec 05, 2021 at 07:08:02PM +0800, yong w wrote:
> > > > Balbir Singh <bsingharora@gmail.com> 于2021年12月5日周日 16:17写道:
> > > > >
> > > > > On Sat, Dec 04, 2021 at 04:09:55AM -0800, yongw.pur@gmail.com wrote:
> > > > > > From: wangyong <wang.yong12@zte.com.cn>
> > > > > >
> > > > > > Delay accounting does not track the delay of memory compact.
> > > > > > When there is not enough free memory, tasks can spend
> > > > > > a amount of their time waiting for compact.
> > > > > >
> > > > > > To get the impact of tasks in direct memory compact, measure
> > > > > > the delay when allocating memory through memory compact.
> > > > > >
> > > > >
> > > > > Should we call this DIRECT_COMPACT and through documentation
> > > > > or name change imply that this won't work for kcompactd the
> > > > > kernel thread - based on my reading of the patches.
> > > > >
> > > > Using DIRECT_COMPACT is a little redundant,because the
> > > > delayacct stats of delay accounting is specific to tasks, it has
> > > > nothing to do with kcompactd, which is similar to the RECLAIM field.
> > > >
> > >
> > > What would we expect when we call delayacct -p <pidof kcompactd>
> > > to be output?
> > If the slow path of memory allocation is invoked in the kcompacd process,
> > there may be delays being recorded.
> >
> > > Don't feel to strongly, but it can be confusing that kcompactd
> > > has spent no time in compact'ing? Not that delayacct is used for
> > > kernel threads, but I am not sure if that use case exists today.
> > Yes, delayacct does not restrict the process of obtaining information,
> > but kcompactd is used for  compaction,  the compact delay of
> > kcompatd is not actually a delay.Maybe it can be added to the
> > document later to make it clearer.
> >
> > Thanks for your reply!

Please avoid top posting, when you say added later, I presume more
patches for documentation are coming. I am OK with the patch in that
case.

Reviewed-by: Balbir Singh <bsingharora@gmail.com>

Balbir Singh


  reply	other threads:[~2021-12-14  5:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04 12:09 yongw.pur
2021-12-05  8:17 ` Balbir Singh
2021-12-05 11:08   ` yong w
2021-12-07  5:16     ` Balbir Singh
2021-12-07 16:50       ` yong w
2021-12-13 13:56         ` yong w
2021-12-14  5:49           ` Balbir Singh [this message]
2021-12-15 12:40             ` yong w

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=YbgwWir/Ymt/2gxE@balbir-desktop \
    --to=bsingharora@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=wang.yong12@zte.com.cn \
    --cc=yang.yang29@zte.com.cn \
    --cc=yongw.pur@gmail.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