[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <a2776ec50808210818n74c09003s98ee8e7bd8e73951@mail.gmail.com>
Date: Thu, 21 Aug 2008 17:18:27 +0200
From: righi.andrea@...il.com
To: "KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>
Cc: balbir@...ux.vnet.ibm.com, "Dave Hansen" <dave@...ux.vnet.ibm.com>,
"Paul Menage" <menage@...gle.com>,
"Dave Hansen" <haveblue@...ibm.com>,
"Hugh Dickins" <hugh@...itas.com>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Linux Memory Management List" <linux-mm@...ck.org>,
"linux kernel mailing list" <linux-kernel@...r.kernel.org>
Subject: Re: [discuss] memrlimit - potential applications that can use
On 8/21/08, KAMEZAWA Hiroyuki <kamezawa.hiroyu@...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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists