From: Andrew Morton <akpm@linux-foundation.org>
To: "zhaowuyun@wingtech.com" <zhaowuyun@wingtech.com>
Cc: "Michal Hocko" <mhocko@kernel.org>,
mgorman <mgorman@techsingularity.net>,
minchan <minchan@kernel.org>, vinmenon <vinmenon@codeaurora.org>,
hannes <hannes@cmpxchg.org>,
"hillf.zj" <hillf.zj@alibaba-inc.com>,
linux-mm <linux-mm@kvack.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"Hugh Dickins" <hughd@google.com>
Subject: Re: [PATCH] [PATCH] mm: disable preemption before swapcache_free
Date: Thu, 26 Jul 2018 15:11:18 -0700 [thread overview]
Message-ID: <20180726151118.db0cf8016e79bed849e549f9@linux-foundation.org> (raw)
In-Reply-To: <20180726150323057627100@wingtech.com>
On Thu, 26 Jul 2018 15:03:23 +0800 "zhaowuyun@wingtech.com" <zhaowuyun@wingtech.com> wrote:
> >On Thu 26-07-18 10:21:40, zhaowuyun@wingtech.com wrote:
> >[...]
> >> Our project really needs a fix to this issue
> >
> >Could you be more specific why? My understanding is that RT tasks
> >usually have all the memory mlocked otherwise all the real time
> >expectations are gone already.
> >--
> >Michal Hocko
> >SUSE Labs
>
>
> The RT thread is created by a process with normal priority, and the process was sleep,
> then some task needs the RT thread to do something, so the process create this thread, and set it to RT policy.
> I think that is the reason why RT task would read the swap.
A simpler bandaid might be to replace the cond_resched() with msleep(1).
next prev parent reply other threads:[~2018-07-26 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2018072514375722198958@wingtech.com>
2018-07-25 7:40 ` Michal Hocko
[not found] ` <2018072515575576668668@wingtech.com>
2018-07-25 8:21 ` Michal Hocko
2018-07-25 10:32 ` Michal Hocko
[not found] ` <2018072517530727482074@wingtech.com>
2018-07-25 10:34 ` Michal Hocko
2018-07-25 21:16 ` Andrew Morton
[not found] ` <2018072610214038358990@wingtech.com>
2018-07-26 6:06 ` Michal Hocko
[not found] ` <20180726150323057627100@wingtech.com>
2018-07-26 7:44 ` Michal Hocko
2018-07-26 22:11 ` Andrew Morton [this message]
[not found] ` <20180727140749669129112@wingtech.com>
2018-08-04 23:07 ` Hugh Dickins
[not found] ` <20180807101540612373235@wingtech.com>
2018-08-07 3:23 ` Hugh Dickins
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=20180726151118.db0cf8016e79bed849e549f9@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hillf.zj@alibaba-inc.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=vinmenon@codeaurora.org \
--cc=zhaowuyun@wingtech.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
all inboxes | Powered by JetHome®