linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Evgeniy Ivanov <lolkaantimat@gmail.com>
To: linux-mm@kvack.org
Subject: Re: Low priority writers make realtime processes thrashing
Date: Sun, 7 Nov 2010 13:20:01 +0300	[thread overview]
Message-ID: <AANLkTimb3aKzMUHOHMXfsFhjd23Ab=y3-1uB_zYJRKRN@mail.gmail.com> (raw)
In-Reply-To: <AANLkTino-GJTpmved=SjmN2O_dN=fhrS+vVfHAPoKQ6y@mail.gmail.com>

Hi again,

I played some more time with writebacks and discovered, that problem
is really not related to the writeback.
What I found is that cache size always changes (min -> + 10mb -> +
10mb -> + 10mb -> min), and it's caused by 3 dd processes, which copy
300 mb in a loop from /dev/zero. It looks like RT process thrashing
when we come to min. In the mailing list I found a presentation, which
points to the page reclaim slow path, which I will try to check
tomorrow. Also I think to try to profile kernel, to see the difference
between normal work and work when RT processes are thrashing.
Filesystem is ext3 with default mount options. But I doubt fs code is
related, since we always write to the same files (append) and hence
it's mostly about getting and dirtying pages.
Any thoughts?

On Tue, Nov 2, 2010 at 7:32 PM, Evgeniy Ivanov <lolkaantimat@gmail.com> wrote:
> 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
>



-- 
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>

      reply	other threads:[~2010-11-07 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-02 16:32 Evgeniy Ivanov
2010-11-07 10:20 ` Evgeniy Ivanov [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='AANLkTimb3aKzMUHOHMXfsFhjd23Ab=y3-1uB_zYJRKRN@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