From owner-freebsd-current Sat Mar 25 12:38:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 573B537B5FA for ; Sat, 25 Mar 2000 12:38:28 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA46330; Sat, 25 Mar 2000 13:38:24 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA73468; Sat, 25 Mar 2000 13:38:13 -0700 (MST) Message-Id: <200003252038.NAA73468@harmony.village.org> To: Matthew Dillon Subject: Re: Anyone know why the syscall interface is using the doreti mechanism? Cc: Bruce Evans , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sat, 25 Mar 2000 02:12:07 PST." <200003251012.CAA19991@apollo.backplane.com> References: <200003251012.CAA19991@apollo.backplane.com> Date: Sat, 25 Mar 2000 13:38:13 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200003251012.CAA19991@apollo.backplane.com> Matthew Dillon writes: : It's getting clean enough that you can almost understand the interrupt : code :-) Cool. That's one part of the kernel that I've not quite fully understood. I always figured there was something I was missing about the code and why it needed to be as complex as it was... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message