From: yong w <yongw.pur@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: bsingharora@gmail.com,
"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 linux-next] delayacct: track delays from memory compact
Date: Sat, 4 Dec 2021 19:23:20 +0800 [thread overview]
Message-ID: <CAOH5QeDZH4vsjN_hHXfe48XYA02ekf4XvynOQ=GzbtgD9cVzgw@mail.gmail.com> (raw)
In-Reply-To: <20211203130210.f34079f175f28bd1c5c26541@linux-foundation.org>
Sorry, the patch has something wrong.
I'll resend the patch later.
Thanks!
Andrew Morton <akpm@linux-foundation.org> 于2021年12月4日周六 05:02写道:
>
> On Fri, 3 Dec 2021 06:37:52 -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 memory compact.
> >
> > To get the impact of tasks in direct memory compact, measure
> > the delay when allocating memory through memory compact.
> >
> > ...
> >
> > --- a/include/linux/delayacct.h
> > +++ b/include/linux/delayacct.h
> > @@ -42,8 +42,13 @@ struct task_delay_info {
> > u64 thrashing_start;
> > u64 thrashing_delay; /* wait for thrashing page */
> >
> > + u64 compact_start;
> > + u64 compact_delay; /* wait for memory compact */
> > +
> > + u64 freepages_start;
>
> task_delay_info already has a freepages_start, so it fails to compile.
>
> Did you send the correct version?
>
next prev parent reply other threads:[~2021-12-04 11:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 14:37 yongw.pur
2021-12-03 21:02 ` Andrew Morton
2021-12-04 11:23 ` yong w [this message]
2021-12-04 10:20 ` kernel test robot
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='CAOH5QeDZH4vsjN_hHXfe48XYA02ekf4XvynOQ=GzbtgD9cVzgw@mail.gmail.com' \
--to=yongw.pur@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--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 \
/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