From: Norbert Preining <preining@logic.at>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: David Rientjes <rientjes@google.com>, linux-kernel@vger.kernel.org
Subject: Re: khugepaged / firefox going wild in 3.18-rc
Date: Fri, 7 Nov 2014 22:07:17 +0900 [thread overview]
Message-ID: <20141107130717.GF11838@auth.logic.tuwien.ac.at> (raw)
In-Reply-To: <545B71A8.6030209@suse.cz>
Hi Vlastimil,
On Thu, 06 Nov 2014, Vlastimil Babka wrote:
> OK, one possibility is to do (it should apply cleanly)
> git revert e14c720efdd73c6d69cd8d07fa894bcd11fe1973
I am running with this reverted now, and I cannot reproduce the
khugepage going overboard anymore.
I tried hard since 2 days now, no chance to reproduce.
Before firefox or shotwell went into boom mode, but not now.
(For now!)
> > Again, as I mentioned, I don't have /proc/pid/stack for any "pid", is
> > this depending on some specific kerenl option?
>
> Ah I missed that. Should be CONFIG_STACKTRACE to enable that.
If you want, I can compile a "default" kernel without the above commit
reverted, and turn on STACKTRACE (I have turned it one for *all* future
kernels I compile ;-)
I also didn't try the patch you send me, just the revert from above.
Please let me know which other experiments you want to see.
Thanks
Norbert
------------------------------------------------------------------------
PREINING, Norbert http://www.preining.info
JAIST, Japan TeX Live & Debian Developer
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
------------------------------------------------------------------------
next prev parent reply other threads:[~2014-11-07 13:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 23:20 Norbert Preining
2014-11-05 0:00 ` David Rientjes
2014-11-05 0:10 ` Norbert Preining
2014-11-05 0:12 ` Norbert Preining
2014-11-05 0:20 ` David Rientjes
2014-11-06 12:25 ` Vlastimil Babka
2014-11-06 12:39 ` Norbert Preining
2014-11-06 13:03 ` Vlastimil Babka
2014-11-07 13:07 ` Norbert Preining [this message]
2014-11-07 13:38 ` Vlastimil Babka
2014-11-07 13:57 ` Norbert Preining
2014-11-07 15:44 ` Vlastimil Babka
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=20141107130717.GF11838@auth.logic.tuwien.ac.at \
--to=preining@logic.at \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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
all inboxes | Powered by JetHome®