From owner-freebsd-questions  Tue Jun 30 12:01:18 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id MAA13832
          for freebsd-questions-outgoing; Tue, 30 Jun 1998 12:01:18 -0700 (PDT)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from europe.std.com (europe.std.com [199.172.62.20])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13814
          for <freebsd-questions@FreeBSD.ORG>; Tue, 30 Jun 1998 12:00:59 -0700 (PDT)
          (envelope-from sja@world.std.com)
Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0)
	id PAA04242; Tue, 30 Jun 1998 15:00:57 -0400 (EDT)
Received: by world.std.com (TheWorld/Spike-2.0)
	id AA29089; Tue, 30 Jun 1998 15:00:56 -0400
From: sja@world.std.com (Stuart J Adams)
Message-Id: <199806301900.AA29089@world.std.com>
Subject: splnet, splx and tsleep
To: freebsd-questions@FreeBSD.ORG
Date: Tue, 30 Jun 1998 15:00:56 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL25]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


I am trying to understand the exact effects
of splnet and splimp in the kernel. 

When running at splnet/splimp a process
cannot be preempted out due to time slicing
right ???

what happens when tsleep is called while
at splnet ??? This happens in the accept
system call, the system can't be left at
the splnet priority level until a connection
is made. How does tsleep effect the current
spl ???

Is there a good explanation on the net or in
book about these kernel architectural issues ??? 

Thanks,
  Stuart


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message