From: Mel Gorman <mgorman@techsingularity.net>
To: zhong jiang <zhongjiang@huawei.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz, linux-mm@kvack.org
Subject: Re: [PATCH] mm, page_alloc: fix the duplicate save/ressave irq
Date: Tue, 14 Mar 2017 13:51:32 +0000 [thread overview]
Message-ID: <20170314135132.6nfsr7f5xevpss6n@techsingularity.net> (raw)
In-Reply-To: <58C7DCCA.6080603@huawei.com>
On Tue, Mar 14, 2017 at 08:06:34PM +0800, zhong jiang wrote:
> >> you mean the removing cpu maybe handle the IRQ, it will result in the incorrect pcpu->count ?
> >>
> > Yes, if it hasn't had interrupts disabled yet at the time of the drain.
> > I didn't check, it probably is called from a context that disables
> > interrupts but the fact you're not sure makes me automatically wary of
> > the patch particularly given how little difference it makes for the common
> > case where direct reclaim failed triggering a drain.
> >
> >> but I don't sure that dying cpu remain handle the IRQ.
> >>
> > You'd need to be certain to justify the patch.
> >
> Hi, Mel
>
> by code review, I see the cpu hotplug will only register the notfier to callback the function without
> interrupt come. is it right ??
>
That sentence is impossible to parse meaningfully. The patch was
posted without verifying it made any performance difference (it almost
certainly won't) and without checking all the callers are actually safe
(which you're still not sure of).
Consider the patch NAK'd on both grounds (marginal, if any improvement
with no checking that the patch is safe).
--
Mel Gorman
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-03-14 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 8:02 zhongjiang
2017-03-13 8:31 ` Vlastimil Babka
2017-03-13 10:08 ` Vlastimil Babka
2017-03-13 10:53 ` zhong jiang
2017-03-13 11:19 ` Mel Gorman
2017-03-13 13:59 ` zhong jiang
2017-03-13 14:26 ` Mel Gorman
2017-03-13 14:51 ` zhong jiang
2017-03-14 12:06 ` zhong jiang
2017-03-14 13:51 ` Mel Gorman [this message]
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=20170314135132.6nfsr7f5xevpss6n@techsingularity.net \
--to=mgorman@techsingularity.net \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=vbabka@suse.cz \
--cc=zhongjiang@huawei.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