From: Dave Jones <davej@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: oomkillers gone wild.
Date: Sun, 10 Jun 2012 20:46:02 -0400 [thread overview]
Message-ID: <20120611004602.GA29713@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206101652180.18114@chino.kir.corp.google.com>
On Sun, Jun 10, 2012 at 04:52:50PM -0700, David Rientjes wrote:
> On Sun, 10 Jun 2012, Dave Jones wrote:
>
> > To double check, here it is in rc2 (which has that patch)..
> >
> > $ uname -r
> > 3.5.0-rc2+
> > $ cat /proc/$(pidof dbus-daemon)/oom_score{_adj,}
> > -900
> > 7441500919753
> > $ grep RSS /proc/$(pidof dbus-daemon)/status
> > VmRSS: 1604 kB
>
> Eek, yes, that's definitely wrong. The following should fix it.
now prints..
-900
0
which I assume is much better ;-)
Dave
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: oomkillers gone wild.
Date: Sun, 10 Jun 2012 20:46:02 -0400 [thread overview]
Message-ID: <20120611004602.GA29713@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1206101652180.18114@chino.kir.corp.google.com>
On Sun, Jun 10, 2012 at 04:52:50PM -0700, David Rientjes wrote:
> On Sun, 10 Jun 2012, Dave Jones wrote:
>
> > To double check, here it is in rc2 (which has that patch)..
> >
> > $ uname -r
> > 3.5.0-rc2+
> > $ cat /proc/$(pidof dbus-daemon)/oom_score{_adj,}
> > -900
> > 7441500919753
> > $ grep RSS /proc/$(pidof dbus-daemon)/status
> > VmRSS: 1604 kB
>
> Eek, yes, that's definitely wrong. The following should fix it.
now prints..
-900
0
which I assume is much better ;-)
Dave
next prev parent reply other threads:[~2012-06-11 0:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 15:27 oomkillers gone wild Dave Jones
2012-06-04 15:27 ` Dave Jones
2012-06-04 23:30 ` David Rientjes
2012-06-04 23:30 ` David Rientjes
2012-06-05 17:44 ` Dave Jones
2012-06-05 17:44 ` Dave Jones
2012-06-05 18:52 ` Dave Jones
2012-06-05 18:52 ` Dave Jones
2012-06-08 19:57 ` David Rientjes
2012-06-08 19:57 ` David Rientjes
2012-06-08 20:03 ` Dave Jones
2012-06-08 20:03 ` Dave Jones
2012-06-08 20:37 ` Thomas Gleixner
2012-06-08 20:37 ` Thomas Gleixner
2012-06-10 2:15 ` David Rientjes
2012-06-10 2:15 ` David Rientjes
2012-06-08 20:15 ` David Rientjes
2012-06-08 20:15 ` David Rientjes
2012-06-08 21:03 ` Dave Jones
2012-06-08 21:03 ` Dave Jones
2012-06-10 2:21 ` David Rientjes
2012-06-10 2:21 ` David Rientjes
2012-06-10 3:21 ` KOSAKI Motohiro
2012-06-10 3:21 ` KOSAKI Motohiro
2012-06-10 20:10 ` Dave Jones
2012-06-10 20:10 ` Dave Jones
2012-06-10 23:52 ` David Rientjes
2012-06-10 23:52 ` David Rientjes
2012-06-11 0:46 ` Dave Jones [this message]
2012-06-11 0:46 ` Dave Jones
2012-06-11 9:11 ` [patch 3.5-rc2] mm, oom: fix and cleanup oom score calculations David Rientjes
2012-06-11 9:11 ` David Rientjes
2012-06-11 19:13 ` Dave Jones
2012-06-11 19:13 ` Dave Jones
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=20120611004602.GA29713@redhat.com \
--to=davej@redhat.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.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.