[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2f11576a0910271102g60dcdd1dj8f3df213bc64a51d@mail.gmail.com>
Date: Wed, 28 Oct 2009 03:02:39 +0900
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: vedran.furac@...il.com
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
hugh.dickins@...cali.co.uk, akpm@...ux-foundation.org,
rientjes@...gle.com
Subject: Re: Memory overcommit
>> I attached a scirpt for checking oom_score of all exisiting process.
>> (oom_score is a value used for selecting "bad" processs.")
>> please run if you have time.
>
> 96890 21463 VirtualBox // OK
> 118615 11144 kded4 // WRONG
> 127455 11158 knotify4 // WRONG
> 132198 1 init // WRONG
> 133940 11151 ksmserver // WRONG
> 134109 11224 audacious2 // Audio player, maybe
> 145476 21503 VirtualBox // OK
> 174939 11322 icedove-bin // thunderbird, maybe
> 178015 11223 akregator // rss reader, maybe
> 201043 22672 krusader // WRONG
> 212609 11187 krunner // WRONG
> 256911 24252 test // culprit, malloced 1GB
> 1750371 11318 run-mozilla.sh // tiny, parent of firefox threads
> 2044902 11141 kdeinit4 // tiny, parent of most KDE apps
Verdran, I made alternative improvement idea. Can you please mesure
badness score
on your system?
Maybe your culprit process take biggest badness value.
Note: this patch change time related thing. So, please drink a cup of
coffee before mesurement.
small rest time makes correct test result.
Download attachment "0001-oom-oom-score-bonus-by-run_time-use-proportional-va.patch" of type "application/octet-stream" (3025 bytes)
Powered by blists - more mailing lists