From mboxrd@z Thu Jan  1 00:00:00 1970
From: Dan Smith <danms@us.ibm.com>
Subject: [RFC] Xend configuration option for console memory limit
Date: Tue, 11 Oct 2005 12:15:35 -0700
Message-ID: <87ek6rj25k.fsf@us.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Xen Developers <xen-devel@lists.xensource.com>
Cc: Ian.Pratt@cl.cam.ac.uk
List-Id: xen-devel@lists.xenproject.org

Bug #296 describes the possible Out-Of-Memory outcome of a console
flood.  Currently, xenconsoled has the ability to obey a limit, but
Xend does not set it, to prevent console message loss.

I propose that a configuration option be added to xend-config.sxp that
sets the limit.  That way, a user with a large console buffer
requirement can easily set it, and OOM situations can be avoided.

I'll be happy to knock up a patch if this sounds reasonable.

Thoughts?

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@us.ibm.com