From: Serge Hallyn <serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org>
To: Aaron Staley <aaron-ZNH+RosXeVlBDgjK7y7TUQ@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Li Zefan <lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>,
Paul Menage <menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.org>
Subject: Re: PROBLEM: Processes writing large files in memory-limited LXC container are killed by OOM
Date: Tue, 25 Jun 2013 08:24:32 -0500 [thread overview]
Message-ID: <20130625132432.GA4098@sergelap> (raw)
In-Reply-To: <CAMcjixYa-mjo5TrxmtBkr0MOf+8r_iSeW5MF4c8nJKdp5m+RPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Quoting Aaron Staley (aaron-ZNH+RosXeVlBDgjK7y7TUQ@public.gmane.org):
> This is better explained here:
> http://serverfault.com/questions/516074/why-are-applications-in-a-memory-limited-lxc-container-writing-large-files-to-di
> (The
> highest-voted answer believes this to be a kernel bug.)
Yeah, sorry I haven't had time to look more into it, but I'm pretty
that's the case. When you sent the previous email I looked quickly at
the dd source. I had always assumed that dd looked at available memory
and malloced as much as it thought it could - but looking at the source,
it does not in fact do that. So yes, I think the kernel is simply
leaving it all in page cache and accounting that to the process which
then gets OOMed.
Instead, the kernel should be throttling the task while it waits for
the page cache to be written to disk (since blkio might also be
slowed down).
-serge
next prev parent reply other threads:[~2013-06-25 13:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 5:45 PROBLEM: Processes writing large files in memory-limited LXC container are killed by OOM Aaron Staley
[not found] ` <CAMcjixYa-mjo5TrxmtBkr0MOf+8r_iSeW5MF4c8nJKdp5m+RPA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-25 13:24 ` Serge Hallyn [this message]
2013-06-25 20:54 ` Aaron Staley
[not found] ` <CAMcjixZtW0KdAmLXyDoGFqL2qh4aEgdGjBYJWrPESFMz0dvELw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27 5:12 ` Zhu Yanhai
[not found] ` <CAC8teKXNof5PdU2dMz4iZ8tM=Dx=aZ0efxotDhdc-xopeK-+Xg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27 5:19 ` Aaron Staley
[not found] ` <CAMcjixZdXWGezcVQPPo3M0yNBx4TtbiOoqYJQWvNbTyqULifUA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-06-27 20:51 ` Aristeu Rozanski
2013-07-01 15:21 ` Serge Hallyn
2013-07-01 15:27 ` Aaron Staley
2013-06-28 18:52 ` Serge E. Hallyn
2013-07-01 18:01 ` Serge Hallyn
2013-07-01 18:01 ` Serge Hallyn
2013-07-01 18:01 ` Serge Hallyn
2013-07-01 18:45 ` Johannes Weiner
2013-07-01 18:45 ` Johannes Weiner
2013-07-01 18:45 ` Johannes Weiner
2013-07-01 18:51 ` Aaron Staley
[not found] ` <20130701184503.GG17812-druUgvl0LCNAfugRpC6u6w@public.gmane.org>
2013-07-01 18:51 ` Aaron Staley
2013-07-01 19:02 ` Serge Hallyn
2013-07-01 19:02 ` Serge Hallyn
2013-07-01 19:02 ` Serge Hallyn
2013-07-02 12:42 ` Michal Hocko
2013-07-02 12:42 ` Michal Hocko
2013-07-02 12:42 ` Michal Hocko
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=20130625132432.GA4098@sergelap \
--to=serge.hallyn-gewih/nmzzlqt0dzr+alfa@public.gmane.org \
--cc=aaron-ZNH+RosXeVlBDgjK7y7TUQ@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=lizf-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org \
--cc=menage-hpIqsD4AKlfQT0dZR+AlfA@public.gmane.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.