From: Mel Gorman <mgorman@suse.de>
To: Bertil Engelholm <bertil.engelholm@ericsson.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: zone_reclaim is hanging high priority real time user pthreads
Date: Thu, 2 Jun 2011 12:02:16 +0100 [thread overview]
Message-ID: <20110602110216.GF7306@suse.de> (raw)
In-Reply-To: <980E20D8E719A84BBF593FDE6AEC23DA0AEB42A245@ESESSCMS0351.eemea.ericsson.se>
On Fri, May 27, 2011 at 01:22:42PM +0200, Bertil Engelholm wrote:
> Thanx for the response. Since a few days back we have tried disabling the
> zone reclaim and the system behaves much better so that seems to be the
> short term solution we'll go for.
Good news.
> I also assume that if you have real time pthreads that are sensitive to
> stalls you might have to disable zone reclaim also in later kernels
> even though the zone reclaim implementation have been radically improved.
>
It'd be one possibility. However, I understand that at least one person
is considering adding an additional level of watermarks that is
dependant on the number of real-time threads in the system and their
expected usage. The idea would be that latency sensitive applications
would be allowed to use a number of pages between two watermarks were
other users would wake kswapd or enter direct reclaim. I don't know
where that currently stands though.
Thanks.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2011-06-02 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 13:34 PROBLEM: zone_reclaim is hanging high priority real time user pthreads Bertil Engelholm
2011-05-27 10:48 ` Mel Gorman
2011-05-27 11:22 ` Bertil Engelholm
2011-06-02 11:02 ` Mel Gorman [this message]
2011-06-08 6:53 ` Bertil Engelholm
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=20110602110216.GF7306@suse.de \
--to=mgorman@suse.de \
--cc=bertil.engelholm@ericsson.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.