linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: cl@linux-foundation.org, linux-mm@kvack.org, pavel@ucw.cz,
	dave@linux.vnet.ibm.com
Subject: Re: [PATCH] Warn if we run out of swap space
Date: Mon, 01 Jun 2009 22:44:20 +0300	[thread overview]
Message-ID: <4A242F94.9010704@redhat.com> (raw)
In-Reply-To: <20090601123503.2337a79b.akpm@linux-foundation.org>

Andrew Morton wrote:
>> We really should have a machine readable channel for this sort of 
>> information, so it can be plumbed to a userspace notification bubble the 
>> user can ignore.
>>     
>
> That could just be printk().  It's a question of a) how to tell
> userspace which bits to pay attention to and maybe b) adding some
> more structure to the text.
>
> Perhaps careful use of faciliy levels would suffice for a), but I
> expect that some new tagging scheme would be more practical.
>   

I thought dmesg was an unreliable channel which can overflow.  It's also 
prone to attacks by spell checkers.

I prefer reliable binary interfaces to shell explorable text interfaces 
as I think any feature worth having is much more useful controlled by an 
application rather than a bored sysadmin.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

--
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: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2009-06-03 14:52 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 18:58 Christoph Lameter
2009-05-22 20:47 ` Pavel Machek
2009-05-23  4:38 ` Andrew Morton
2009-05-25  0:53   ` KAMEZAWA Hiroyuki
2009-05-24 13:44 ` KOSAKI Motohiro
2009-05-25  2:42   ` Randy Dunlap
2009-05-26  0:40     ` KOSAKI Motohiro
2009-05-26  1:05       ` Randy Dunlap
2009-05-26  1:08         ` KOSAKI Motohiro
2009-05-26  3:29     ` Paul Mundt
2009-05-26 14:23       ` Christoph Lameter
2009-05-26 20:15         ` Andrew Morton
2009-05-26 20:45           ` Randy Dunlap
2009-05-26 20:55             ` Andrew Morton
2009-05-27  0:25               ` KAMEZAWA Hiroyuki
2009-05-26 20:54           ` Christoph Lameter
2009-05-26 21:01             ` Andrew Morton
2009-05-26 21:05               ` Christoph Lameter
2009-05-27  0:42         ` KAMEZAWA Hiroyuki
2009-05-27 13:54           ` Christoph Lameter
2009-06-04  6:02             ` KOSAKI Motohiro
2009-06-01 16:19 ` Avi Kivity
2009-06-01 17:29   ` Christoph Lameter
2009-06-01 17:38     ` Avi Kivity
2009-06-01 19:35   ` Andrew Morton
2009-06-01 19:44     ` Avi Kivity [this message]
2009-06-02  9:14       ` Pavel Machek
2009-06-02  9:19         ` Avi Kivity
2009-06-02  9:15       ` Pavel Machek
2009-06-02  9:21         ` Avi Kivity
2009-06-02  9:30           ` Pavel Machek
2009-06-02  9:50             ` Avi Kivity
2009-06-02  9:23         ` Avi Kivity
2009-06-02  9:26           ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A242F94.9010704@redhat.com \
    --to=avi@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=dave@linux.vnet.ibm.com \
    --cc=linux-mm@kvack.org \
    --cc=pavel@ucw.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox