Date: Fri, 04 Jan 2008 14:12:50 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: "Igor Mozolevsky" <igor@hybrid-lab.co.uk> Cc: Poul-Henning Kamp <phk@phk.freebsd.dk>, freebsd-current@freebsd.org, Robert Watson <rwatson@freebsd.org>, Jason Evans <jasone@freebsd.org> Subject: Re: sbrk(2) broken Message-ID: <86abnlag4t.fsf@ds4.des.no> In-Reply-To: <a2b6592c0801040503j650046f5k73895b5b0c84025d@mail.gmail.com> (Igor Mozolevsky's message of "Fri\, 4 Jan 2008 13\:03\:01 %2B0000") References: <86myrlahee.fsf@ds4.des.no> <5647.1199451237@critter.freebsd.dk> <a2b6592c0801040503j650046f5k73895b5b0c84025d@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
"Igor Mozolevsky" <igor@hybrid-lab.co.uk> 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, 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) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86abnlag4t.fsf>