From owner-freebsd-advocacy Thu Dec 20 14:41: 5 2001 Delivered-To: freebsd-advocacy@freebsd.org Received: from freebie.atkielski.com (ASt-Lambert-101-2-1-14.abo.wanadoo.fr [193.251.59.14]) by hub.freebsd.org (Postfix) with ESMTP id D8E7537B417; Thu, 20 Dec 2001 14:40:55 -0800 (PST) Received: from contactdish ([10.0.0.10]) by freebie.atkielski.com (8.11.3/8.11.3) with SMTP id fBKMesR30110; Thu, 20 Dec 2001 23:40:54 +0100 (CET) (envelope-from anthony@freebie.atkielski.com) Message-ID: <027901c189a7$62a133c0$0a00000a@atkielski.com> From: "Anthony Atkielski" To: "John Baldwin" Cc: "Jeremiah Gowdy" , , "Gilbert Gong" References: Subject: Re: Microsoft Advocacy? Date: Thu, 20 Dec 2001 23:40:54 +0100 Organization: Anthony's Home Page (development site) MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-advocacy@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG John writes: > Yes, I have read them. I also note that the > ones I am willing to sign do not make restrictions > on the open source software I develop. Even if you are willing to stand your ground, can you be certain that all others do the same? > Uh, this is _specifically_ for UP machines. That occurred to me as I was pressing the send button. > Unmaskable interrupts are usually fatal > machine exceptions where we are about > to panic anyway, so they are not a concern. Usually? What are the exceptions, and how do you handle them? If you have locks that are set only within code that inhibits interrupts, you don't have to worry about the overhead of spinning on them, because they will always be unlocked. If you remove the locks, though, and for any reason the code is interrupted by an unmaskable interrupt, you may experience an unpredictable system failure. Leaving the lock in incurs very little overhead and offers a sanity check, just in case you overlooked something. > This only serves to display your ignorance. No, it simply proves that I've been there, done that, and learned from my mistakes. The longer you write system software, the more conservative and cautious you become. > You missed my point: this design goal came > from worrying about user needs (desktop) rather > than server needs. I don't see how that goal would be specific to a desktop environment. > It was when it was first done in BSD. Maybe it was for BSD, but algorithms like that have been around for as long as operating systems have (or at least since CPUs overtook I/O performance-wise). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-advocacy" in the body of the message