Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 13 Sep 2002 17:28:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 13 Sep 2002 17:28:30 -0400 Received: from 2-028.ctame701-1.telepar.net.br ([200.193.160.28]:42645 "EHLO 2-028.ctame701-1.telepar.net.br") by vger.kernel.org with ESMTP id ; Fri, 13 Sep 2002 17:28:29 -0400 Date: Fri, 13 Sep 2002 18:33:04 -0300 (BRT) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Pavel Machek cc: kernel list Subject: Re: Good way to free as much memory as possible under 2.5.34? In-Reply-To: <20020913212921.GA17627@atrey.karlin.mff.cuni.cz> 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 Content-Length: 943 Lines: 28 On Fri, 13 Sep 2002, Pavel Machek wrote: > Allocating memory is pain because I have to free it afterwards. Yep I > have such code, but it is ugly. try_to_free_pages() really seems like > cleaner solution to me... if you only tell me how to fix it :-). "Fixing" the VM just so it behaves the way swsuspend wants is out. If swsuspend relies on all other subsystems playing nicely, I think it should be removed from the kernel. I suspect only very few people will use swsuspend, so it should not be intrusive. regards, Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ Spamtraps of the month: september@surriel.com trac@trac.org - 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/