Messages in this thread |  | | | Date | Thu, 21 Aug 2008 17:18:27 +0200 | | From | righi.andrea@gmail ... | | Subject | Re: [discuss] memrlimit - potential applications that can use | |
On 8/21/08, KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> I'm sorry I miss the point. My concern on memrlimit (for overcommiting) is
> that
> it's not fair because an application which get -ENOMEM at mmap() is just
> someone
> unlucky. I think it's better to trigger some notifier to application or
> daemon
> rather than return -ENOMEM at mmap(). Notification like "Oh, it seems the
> VSZ
> of total application exceeds the limit you set. Although you can continue
> your
> operation, it's recommended that you should fix up the situation".
> will be good.
-ENOMEM should be considered by applications like "try again" (maybe
-EAGAIN would be more appropriate). When the notification of the
out-of-virtual-memory event occurs the dedicated userspace daemon can
do ehm... something... to resolve the situation. Just like the OOM
handling in userspace. Similar issues, but a common solution could
resolve both problems.
-Andrea
|  |