From owner-freebsd-hackers Thu Feb 21 0:28:54 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.prod.itd.earthlink.net (harrier.mail.pas.earthlink.net [207.217.120.12]) by hub.freebsd.org (Postfix) with ESMTP id 7D04637B400 for ; Thu, 21 Feb 2002 00:28:52 -0800 (PST) Received: from pool0063.cvx40-bradley.dialup.earthlink.net ([216.244.42.63] helo=mindspring.com) by harrier.prod.itd.earthlink.net with esmtp (Exim 3.33 #1) id 16doav-0003f1-00; Thu, 21 Feb 2002 00:28:49 -0800 Message-ID: <3C74AFB7.FCDEE8A2@mindspring.com> Date: Thu, 21 Feb 2002 00:28:39 -0800 From: Terry Lambert X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: sridharv@ufl.edu Cc: hackers@freebsd.org Subject: Re: interrupt priority question References: <1014272387.3c74918386be5@webmail.health.ufl.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG sridharv@ufl.edu wrote: > While i understand the mechanism of hardware interrupt priority, > I am curious to know how the priority levels are achieved/implemented > for software ( in particular the various layers of the TCP/IP stack.. > splxxx() ). Stevens Volume 2 is the canonical reference. Basically, the code runs at NETISR, which is a software interrupt which is ran at splx() time. Look at the source code for splx() to get a better idea. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message