From: Vivek Goyal <vgoyal@redhat.com>
To: Petr Tesarik <ptesarik@suse.cz>
Cc: Atsushi Kumagai <kumagai-atsushi@mxc.nes.nec.co.jp>,
"d.hatayama@jp.fujitsu.com" <d.hatayama@jp.fujitsu.com>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>,
"zzou@redhat.com" <zzou@redhat.com>,
"bhe@redhat.com" <bhe@redhat.com>
Subject: Re: [PATCH] makedumpfile: change the wrong code to calculate bufsize_cyclic for elf dump
Date: Mon, 21 Apr 2014 11:51:56 -0400 [thread overview]
Message-ID: <20140421155156.GE4367@redhat.com> (raw)
In-Reply-To: <20140421174630.78565d63@hananiah.suse.cz>
On Mon, Apr 21, 2014 at 05:46:30PM +0200, Petr Tesarik wrote:
> On Mon, 21 Apr 2014 11:19:14 -0400
> Vivek Goyal <vgoyal@redhat.com> wrote:
>
> > On Fri, Apr 18, 2014 at 09:41:33PM +0200, Petr Tesarik wrote:
> > > On Fri, 18 Apr 2014 22:29:12 +0800
> > > "bhe@redhat.com" <bhe@redhat.com> wrote:
> >[...]
> > > > Instead, I am wondering how the 80% comes from, and why 20% of free
> > > > memory must be safe.
> > >
> > > I believe these 80% come from the default value of vm.dirty_ratio,
> >
> > Actually I had suggested this 80% number when --cyclic feature was
> > implemented. And I did not base it on dirty_ratio. Just a random
> > suggestion.
>
> Hm. OK, you seem to have very good suggestions, even if they are
> random. ;-)
>
> > > which is 20%. In other words, the kernel won't block further writes
> > > until 20% of available RAM is used up by dirty cache. But if you
> > > fill up all free memory with dirty pages and then touch another (though
> > > allocated) page, the kernel will go into direct reclaim, and if nothing
> > > can be written out ATM, it will invoke the OOM Killer.
> >
> > We can start playig with reducing dirty_raio too and see how does it go.
>
> Or use direct I/O... Is it still broken?
May be if that turns out to be an issue. Or just reduce dirty_ratio to say
5 instead of default 20. Different things can be tried once we know what's
the root cause of the issue.
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2014-04-21 15:52 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-10 21:44 makedumpfile memmory usage seems high with option -E Vivek Goyal
2014-04-11 9:22 ` Atsushi Kumagai
2014-04-11 10:19 ` Arthur Zou
2014-04-14 8:02 ` [PATCH] makedumpfile: change the wrong code to calculate bufsize_cyclic for elf dump Baoquan He
2014-04-14 8:11 ` Baoquan He
2014-04-16 6:44 ` Baoquan He
2014-04-17 4:01 ` Atsushi Kumagai
2014-04-17 4:52 ` bhe
2014-04-17 5:02 ` bhe
2014-04-18 9:22 ` Atsushi Kumagai
2014-04-18 14:29 ` bhe
2014-04-18 19:41 ` Petr Tesarik
2014-04-21 15:19 ` Vivek Goyal
2014-04-21 15:46 ` Petr Tesarik
2014-04-21 15:51 ` Vivek Goyal [this message]
2014-04-21 15:14 ` Vivek Goyal
2014-04-23 11:09 ` bhe
2014-04-21 15:12 ` Vivek Goyal
2014-04-23 7:55 ` Atsushi Kumagai
2014-04-23 11:55 ` bhe
2014-04-23 17:08 ` Vivek Goyal
2014-04-23 23:50 ` bhe
2014-04-24 2:05 ` bhe
2014-04-25 13:22 ` Vivek Goyal
2014-04-28 5:05 ` Atsushi Kumagai
2014-04-28 12:50 ` Vivek Goyal
2014-05-09 5:36 ` Atsushi Kumagai
2014-05-09 20:49 ` Vivek Goyal
2014-05-15 7:22 ` bhe
2014-05-15 9:10 ` Atsushi Kumagai
2014-05-19 11:15 ` bhe
2014-05-19 15:11 ` Vivek Goyal
2014-05-27 5:34 ` Atsushi Kumagai
2014-05-27 14:49 ` Vivek Goyal
2014-05-23 7:18 ` Atsushi Kumagai
2014-05-14 5:44 ` bhe
2014-04-28 5:04 ` Atsushi Kumagai
2014-05-09 5:35 ` Atsushi Kumagai
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=20140421155156.GE4367@redhat.com \
--to=vgoyal@redhat.com \
--cc=bhe@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=kumagai-atsushi@mxc.nes.nec.co.jp \
--cc=ptesarik@suse.cz \
--cc=zzou@redhat.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 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.