Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 12 Apr 2001 16:19:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 12 Apr 2001 16:19:24 -0400 Received: from garrincha.netbank.com.br ([200.203.199.88]:56335 "HELO netbank.com.br") by vger.kernel.org with SMTP id ; Thu, 12 Apr 2001 16:19:14 -0400 Date: Thu, 12 Apr 2001 17:18:55 -0300 (BRST) From: Rik van Riel To: Szabolcs Szakacsits Cc: Marcelo Tosatti , Alan Cox , Hugh Dickins , Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org Subject: Re: scheduler went mad? In-Reply-To: Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 12 Apr 2001, Szabolcs Szakacsits wrote: > You mean without dropping out_of_memory() test in kswapd and calling > oom_kill() in page fault [i.e. without additional patch]? No. I think it's ok for __alloc_pages() to call oom_kill() IF we turn out to be out of memory, but that should not even be needed. Also, when a task in __alloc_pages() is OOM-killed, it will have PF_MEMALLOC set and will immediately break out of the loop. The rest of the system will spin around in the loop until the victim has exited and then their allocations will succeed. regards, Rik -- Virtual memory is like a game you can't win; However, without VM there's truly nothing to lose... http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com.br/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/