From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail172.messagelabs.com (mail172.messagelabs.com [216.82.254.3]) by kanga.kvack.org (Postfix) with SMTP id A53B85F0019 for ; Wed, 3 Jun 2009 13:27:54 -0400 (EDT) Message-ID: <4A24EF07.6070708@redhat.com> Date: Tue, 02 Jun 2009 12:21:11 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [PATCH] Warn if we run out of swap space References: <4A23FF89.2060603@redhat.com> <20090601123503.2337a79b.akpm@linux-foundation.org> <4A242F94.9010704@redhat.com> <20090602091544.GC15756@elf.ucw.cz> In-Reply-To: <20090602091544.GC15756@elf.ucw.cz> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org To: Pavel Machek Cc: Andrew Morton , cl@linux-foundation.org, linux-mm@kvack.org, dave@linux.vnet.ibm.com List-ID: Pavel Machek wrote: > Ouch and please... don't stop useful printk() warnings just because > some 'pie-in-the-sky future binary protocol'. That's what happened in > ACPI land with battery critical, and it is also why I don't get > battery warnings on some of my machines. > I don't oppose printk() on significant events (such as this) in addition to a proper programmatic interface. > State-of-the art userspace should not be required for reasonable > operation... > Pavel > On the other hand, we shouldn't need to cobble userspace out of a bunch of shell scripts because the kernel tries to communicate with users directly. -- error compiling committee.c: too many arguments to function -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org