From owner-freebsd-current@FreeBSD.ORG Mon Jan 7 09:08:38 2008 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DEE6B16A417; Mon, 7 Jan 2008 09:08:38 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id 98AE713C442; Mon, 7 Jan 2008 09:08:38 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id BE39C17105; Mon, 7 Jan 2008 09:08:36 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m0798Z1D008681; Mon, 7 Jan 2008 09:08:35 GMT (envelope-from phk@critter.freebsd.dk) To: Kostik Belousov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Fri, 04 Jan 2008 15:48:29 +0200." <20080104134829.GA57756@deviant.kiev.zoral.com.ua> Date: Mon, 07 Jan 2008 09:08:35 +0000 Message-ID: <8680.1199696915@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Dag-Erling Sm??rgrav , freebsd-current@freebsd.org, Robert Watson , Jason Evans , Igor Mozolevsky Subject: Re: sbrk(2) broken X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2008 09:08:39 -0000 In message <20080104134829.GA57756@deviant.kiev.zoral.com.ua>, Kostik Belousov writes: >On Fri, Jan 04, 2008 at 02:12:50PM +0100, Dag-Erling Sm??rgrav wrote: >> "Igor Mozolevsky" writes: >> > This makes memory management in the userland hideously and >> > unnecessarily complicated. It's simpler to have SIGDANGER [...] >> >> You don't seem to understand what Poul-Henning was trying to point out, >> which is that broadcasting SIGDANGER can make a bad situation much, much >> worse by waking up and paging in every single process in the system, > >By making the default action for SIGDANGER to be SIG_IGN, this problem >would be mostly solved. Only processes that actually care about SIGDANGER >and installing the handler for it would require some non-trivial and >resource-hungry operation. This is a non-starter, if SIGDANGER is to have any effect, all processes that use malloc(3) should react to it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.