Date: Tue, 17 Nov 1998 14:08:57 -0800 (PST) From: Matthew Dillon <dillon@apollo.backplane.com> To: Terry Lambert <tlambert@primenet.com> Cc: Marius.Bendiksen@scancall.no (Marius Bendiksen), rnordier@nordier.com, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD on i386 memory model Message-ID: <199811172208.OAA29032@apollo.backplane.com> References: <199811171806.LAA03809@usr09.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The only differences between a normal call gate and an
interrupt is that an interrupt disables interrupts on call
(cli equivalent), while a call gate does not, and a
call gate has extra garbage to handle argument copying
(which we don't use), while an interrupt does not.
There are constructs that make call gates sound like a
walk in the park, though... a task gate, for example.
What a holy mess.
Interrupt gates are definitely faster.
-Matt
:> I've not looked upon interrupts beyond hardware handling, but I seem to
:> recall call gates being preferrable for isolation reasons, but I'm not
:> sure, so don't flame me if I'm wrong ;)
:
:Actually, you can swap the same stuff as a result of an interrupt;
:see:
:
: Protected Mode Software Architecture
: Tom Shanley
: MindShare, Inc.
: ISBN: 0-201-55447-X
:
: Terry Lambert
: terry@lambert.org
:---
:Any opinions in this posting are my own and not those of my present
:or previous employers.
:
:To Unsubscribe: send mail to majordomo@FreeBSD.org
:with "unsubscribe freebsd-hackers" in the body of the message
:
Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet
Communications & God knows what else.
<dillon@backplane.com> (Please include original email in any response)
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811172208.OAA29032>