From owner-freebsd-smp  Sat Apr  5 08:17:32 1997
Return-Path: <owner-smp>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id IAA15121
          for smp-outgoing; Sat, 5 Apr 1997 08:17:32 -0800 (PST)
Received: from corona.jcmax.com (corona.jcmax.com [204.69.248.2])
          by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA15115
          for <smp@freebsd.org>; Sat, 5 Apr 1997 08:17:28 -0800 (PST)
Received: by corona.jcmax.com (5.65/2.49G/4.1.3_U1)
	id AA05092; Sat, 5 Apr 97 11:17:25 -0500
Date: Sat, 5 Apr 97 11:17:25 -0500
From: cr@jcmax.com (Cyrus Rahman)
Message-Id: <9704051617.AA05092@corona.jcmax.com>
To: smp@freebsd.org
Subject: Questions about mp_lock
Sender: owner-smp@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Could someone who had a hand in implementing the SMP kernel give me a hint
about why the mp_lock count gets stored in the proc/user structure and
switched out in cpu_switch()?

Seems kind of weird, since I would expect that a process getting switched in
or out would always posses exactly one lock, and that any others would be
the result of interrupts.  But it does appear that something more complicated
is going on, and I can't exactly figure out what it is.

Cyrus