From: Branimir Maksimovic <branimir.maksimovic@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: vm commit in atop utility steadilly grows (latest mainline kernel from git)
Date: Sat, 18 Jan 2014 09:21:08 +0100 [thread overview]
Message-ID: <52DA3974.2080800@gmail.com> (raw)
In-Reply-To: <52D97F2D.1020500@gmail.com>
Hm, I don't know what happened, perhaps I miscompiled but after
todays git updates and recompile problem is no more.
On 01/17/2014 08:06 PM, Branimir Maksimovic wrote:
> Yesterday, I have noticed that vmcom steadilly grows (it was 7TB before
> I noticed). I compile kernel every day or two after git pull.
> Rebooted and then watched atop, vmcom constantly grows.
> Didn't notice any of running processes to allocate.
> Booted in 3.12.8 kernel and everything is back to normal.
> Since this is pretty noticable, I guess that this is caused by commit
> between rc8 release and now, not sure.
> Machine is i5 3570k, motherboard asus maximus gene v.
>
>
next prev parent reply other threads:[~2014-01-18 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 19:06 vm commit in atop utility steadilly grows (latest mainline kernel from git) Branimir Maksimovic
2014-01-18 8:21 ` Branimir Maksimovic [this message]
2014-01-18 8:34 ` Andrew Morton
2014-01-18 8:44 ` Branimir Maksimovic
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=52DA3974.2080800@gmail.com \
--to=branimir.maksimovic@gmail.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).