From owner-freebsd-current@FreeBSD.ORG Fri Jan 4 13:48:40 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 4BD1B16A417; Fri, 4 Jan 2008 13:48:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from relay02.kiev.sovam.com (relay02.kiev.sovam.com [62.64.120.197]) by mx1.freebsd.org (Postfix) with ESMTP id E473213C50D; Fri, 4 Jan 2008 13:48:39 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from [212.82.216.226] (helo=deviant.kiev.zoral.com.ua) by relay02.kiev.sovam.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from ) id 1JAmuU-000PGi-2Y; Fri, 04 Jan 2008 15:48:38 +0200 Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2) with ESMTP id m04DmTeu067071; Fri, 4 Jan 2008 15:48:29 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.2/8.14.2/Submit) id m04DmTTd067070; Fri, 4 Jan 2008 15:48:29 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 4 Jan 2008 15:48:29 +0200 From: Kostik Belousov To: Dag-Erling Sm??rgrav Message-ID: <20080104134829.GA57756@deviant.kiev.zoral.com.ua> References: <86myrlahee.fsf@ds4.des.no> <5647.1199451237@critter.freebsd.dk> <86abnlag4t.fsf@ds4.des.no> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="28KEV0d44fEAywNn" Content-Disposition: inline In-Reply-To: <86abnlag4t.fsf@ds4.des.no> User-Agent: Mutt/1.4.2.3i X-Scanner-Signature: a8c813420754d5015e2a5a3aeed75c84 X-DrWeb-checked: yes X-SpamTest-Envelope-From: kostikbel@gmail.com X-SpamTest-Group-ID: 00000000 X-SpamTest-Info: Profiles 1976 [Dec 29 2007] X-SpamTest-Info: helo_type=3 X-SpamTest-Info: {received from trusted relay: not dialup} X-SpamTest-Method: none X-SpamTest-Method: Local Lists X-SpamTest-Rate: 0 X-SpamTest-Status: Not detected X-SpamTest-Status-Extended: not_detected X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0255], KAS30/Release Cc: Poul-Henning Kamp , 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: Fri, 04 Jan 2008 13:48:40 -0000 --28KEV0d44fEAywNn Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 [...] >=20 > 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, > including processes that are blocked and wouldn't otherwise run for > several minutes, hours or even days (getty, inetd, sshd, mountd, even > nfsd / nfsiod in some cases can sleep for days at a time waiting for > I/O) 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. --28KEV0d44fEAywNn Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFHfjksC3+MBN1Mb4gRAmJjAKDta4Mk4AjCW2d0m5X/14Nkpo944QCgs4WC vcLoV3Fz6xWAXkmkPWhOFbc= =R3Hf -----END PGP SIGNATURE----- --28KEV0d44fEAywNn--