Messages in this thread |  | | | Date | Wed, 20 Feb 2008 11:48:41 +0900 | | From | KOSAKI Motohiro <> | | Subject | Re: [PATCH 0/8][for -mm] mem_notify v6 | |
Hi Rik
> > Sounds like a job for memory limits (ulimit?), not for OOM
> > notification, right?
>
> I suspect one problem could be that an HPC job scheduling program
> does not know exactly how much memory each job can take, so it can
> sometimes end up making a mistake and overcommitting the memory on
> one HPC node.
>
> In that case the user is better off having that job killed and
> restarted elsewhere, than having all of the jobs on that node
> crawl to a halt due to swapping.
>
> Paul, is this guess correct? :)
Yes.
Fujitsu HPC middleware watching sum of memory consumption of the job
and, if over-consumption happened, kill process and remove job schedule.
I think that is common hpc requirement.
but we watching to user defined memory limit, not swap.
Thanks.
|  |