From: Evgeniy Ivanov <lolkaantimat@gmail.com>
To: linux-mm@kvack.org
Subject: Low priority writers make realtime processes thrashing
Date: Tue, 2 Nov 2010 19:32:40 +0300 [thread overview]
Message-ID: <AANLkTino-GJTpmved=SjmN2O_dN=fhrS+vVfHAPoKQ6y@mail.gmail.com> (raw)
Hi,
When I run few "hard-writers" I get problems with my 15 realtime
processes (do some very small writes, just 2 pages per-time): they
start thrashing. I thought it's caused by write-back and was waiting
for Greg Tellen's per-cgroup dirty page accounting patch. Before
testing it I tried to change threshold in
page-writeback.c:get_dirty_limits(), I set dirty_ratio for RT process
80% (instead of just extra dirty / 4), but it didn't help me. What
else can cause problems?
I'm linux kernel newbie and will appreciate any addvices.
--
Evgeniy Ivanov
--
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/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2010-11-02 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 16:32 Evgeniy Ivanov [this message]
2010-11-07 10:20 ` Evgeniy Ivanov
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='AANLkTino-GJTpmved=SjmN2O_dN=fhrS+vVfHAPoKQ6y@mail.gmail.com' \
--to=lolkaantimat@gmail.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox