From: Aili Yao <yaoaili@kingsoft.com>
To: Oscar Salvador <osalvador@suse.de>
Cc: <naoya.horiguchi@nec.com>, <linux-mm@kvack.org>,
<yangfeng1@kingsoft.com>
Subject: Re: [PATCH] mm,hwpoison: non-current task should be checked early_kill for force_early
Date: Fri, 15 Jan 2021 17:53:08 +0800 [thread overview]
Message-ID: <20210115175308.42e212ce.yaoaili@kingsoft.com> (raw)
In-Reply-To: <20210115094037.GD4092@linux>
On Fri, 15 Jan 2021 10:40:37 +0100
Oscar Salvador <osalvador@suse.de> wrote:
> On Fri, Jan 15, 2021 at 05:31:25PM +0800, Aili Yao wrote:
> > On Fri, 15 Jan 2021 17:26:22 +0800
> > Aili Yao <yaoaili@kingsoft.com> wrote:
> >
> > > > So, back to your change, if force_early was set, but the main task does not
> > > > match, you still want to check whether any thread belonging to the main task
> > > > has the policy set?
> > > >
> > > Yes.
> > >
> > Sorry, the code only loop processes, not thread.
>
> The loop in task_early_kill goes through processes, while the one in
> find_early_kill_thread goes through threads, right?
>
I think you are right, to early_kill, the code wants pick the right thread of one process.
--
Best Regards!
Aili Yao
next prev parent reply other threads:[~2021-01-15 10:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 7:55 Aili Yao
2021-01-15 8:49 ` Oscar Salvador
2021-01-15 9:26 ` Aili Yao
2021-01-15 9:31 ` Aili Yao
2021-01-15 9:40 ` Oscar Salvador
2021-01-15 9:53 ` Aili Yao [this message]
2021-01-15 10:31 ` Oscar Salvador
2021-01-18 5:15 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 5:57 ` Aili Yao
2021-01-18 6:50 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 7:16 ` Aili Yao
2021-01-18 8:15 ` Aili Yao
2021-01-18 8:57 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 9:09 ` Aili Yao
2021-01-19 5:25 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-19 6:04 ` Aili Yao
2021-01-19 7:33 ` HORIGUCHI NAOYA(堀口 直也)
2021-01-18 9:24 ` Oscar Salvador
2021-01-18 9:38 ` Aili Yao
2021-01-18 10:09 ` Oscar Salvador
2021-01-19 4:21 ` Aili Yao
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=20210115175308.42e212ce.yaoaili@kingsoft.com \
--to=yaoaili@kingsoft.com \
--cc=linux-mm@kvack.org \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=yangfeng1@kingsoft.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