From owner-freebsd-smp Mon Apr 9 22:40:45 2001 Delivered-To: freebsd-smp@freebsd.org Received: from d902.iki.rssi.ru (d902.iki.rssi.ru [193.232.9.10]) by hub.freebsd.org (Postfix) with ESMTP id 4C96237B423 for ; Mon, 9 Apr 2001 22:40:40 -0700 (PDT) (envelope-from degay@d902.iki.rssi.ru) Received: from fishpc.iki.rssi.ru (fishpc.iki.rssi.ru [193.232.9.87]) by d902.iki.rssi.ru (8.11.1/8.11.1) with SMTP id f3A5edp66239 for ; Tue, 10 Apr 2001 09:40:39 +0400 (MSD) (envelope-from degay@d902.iki.rssi.ru) From: Alexander Degay To: freebsd-smp@FreeBSD.ORG Subject: unsub Date: Tue, 10 Apr 2001 09:40:39 +0400 Organization: SMISLAB Reply-To: degay@d902.iki.rssi.ru Message-ID: X-Mailer: Forte Agent 1.8/32.548 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth 6aab658f unsubscribe freebsd-smp degay@d902.iki.rssi.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Apr 11 14:40:15 2001 Delivered-To: freebsd-smp@freebsd.org Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by hub.freebsd.org (Postfix) with SMTP id 4F13F37B423 for ; Wed, 11 Apr 2001 14:40:13 -0700 (PDT) (envelope-from jkf@aura.research.bell-labs.com) Received: from grubby.research.bell-labs.com ([135.104.2.9]) by crufty; Wed Apr 11 17:37:58 EDT 2001 Received: from aura.research.bell-labs.com ([135.104.46.10]) by grubby; Wed Apr 11 17:40:10 EDT 2001 Received: (from jkf@localhost) by aura.research.bell-labs.com (8.9.1/8.9.1) id RAA14852; Wed, 11 Apr 2001 17:40:07 -0400 (EDT) Date: Wed, 11 Apr 2001 17:40:07 -0400 (EDT) From: Jeff Fellin Message-Id: <200104112140.RAA14852@aura.research.bell-labs.com> To: freebsd-arch@FreeBSD.org, freebsd-smp@FreeBSD.org Subject: Making a driver SMP-safe Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm not sure this belongs here or in bsd-smp, so I'm dual posting it. I have a question on what the actual interfaces, and if there are any guidelines on how to convert a device driver that runs in a UniProcessor environement to one that can run on concurrent CPU's in a MultiProcessor environment. Many of the archives talk about mutexes in general, but I haven't seen a concise description of how a driver needs to deal with SMP issues. I have written several SMP drivers using the POSIX and other SMP mutex schemes, so I need to know the API's. I have built my driver on an SMP kernel (STABLE) and it works, at least to funky lock panics. So, I assume something was done to prevent concurrent access to my driver in STABLE. I would like to know what was done to protect the driver from executing concurrently. Any pointers to documents or mail archive entries I may have missed in my searches is appreciated. Jeff Fellin Bell Labs, Murray Hill NJ (908) 582-7673 fellin@lucent.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Apr 11 15: 5:37 2001 Delivered-To: freebsd-smp@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id F34BB37B422; Wed, 11 Apr 2001 15:05:31 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.2/8.11.2) with ESMTP id f3BM5GG10418; Wed, 11 Apr 2001 15:05:16 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200104112140.RAA14852@aura.research.bell-labs.com> Date: Wed, 11 Apr 2001 15:04:46 -0700 (PDT) From: John Baldwin To: Jeff Fellin Subject: RE: Making a driver SMP-safe Cc: freebsd-smp@FreeBSD.org, freebsd-arch@FreeBSD.org Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 11-Apr-01 Jeff Fellin wrote: > > I'm not sure this belongs here or in bsd-smp, so I'm dual posting it. > > I have a question on what the actual interfaces, and if there are > any guidelines on how to convert a device driver that runs in a > UniProcessor environement to one that can run on concurrent CPU's > in a MultiProcessor environment. > > Many of the archives talk about mutexes in general, but I haven't > seen a concise description of how a driver needs to deal with SMP > issues. I have written several SMP drivers using the POSIX and other > SMP mutex schemes, so I need to know the API's. > > > I have built my driver on an SMP kernel (STABLE) and it works, > at least to funky lock panics. So, I assume something was done to > prevent concurrent access to my driver in STABLE. I would like to > know what was done to protect the driver from executing concurrently. In stable there is a giant spin lock around the entire kernel, which protects your driver. In -current it's a bit different, but at this point in time it all looks the same to the drivers as there is a Giant mutex that protects 99% of the kernel still. Later on when Giant is split up driver's will start needing to use locks to protect their data as well as to access shared data. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Wed Apr 11 15:13:29 2001 Delivered-To: freebsd-smp@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E2F9237B423; Wed, 11 Apr 2001 15:13:24 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA04999; Wed, 11 Apr 2001 15:13:27 -0700 Date: Wed, 11 Apr 2001 15:13:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jeff Fellin Cc: freebsd-smp@FreeBSD.ORG, freebsd-arch@FreeBSD.ORG Subject: RE: Making a driver SMP-safe In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jeff- from what I know of your project, you'll have to wait until CAM is SMP-ized anyway. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message From owner-freebsd-smp Fri Apr 13 13: 9: 9 2001 Delivered-To: freebsd-smp@freebsd.org Received: from smtp03.mrf.mail.rcn.net (smtp03.mrf.mail.rcn.net [207.172.4.62]) by hub.freebsd.org (Postfix) with ESMTP id C14D137B50B for ; Fri, 13 Apr 2001 13:09:07 -0700 (PDT) (envelope-from gwadkins@erols.com) Received: from 66-44-13-12.s774.apx2.lnh.md.dialup.rcn.com ([66.44.13.12] helo=george) by smtp03.mrf.mail.rcn.net with smtp (Exim 3.16 #5) id 14o9sQ-0005dD-00 for freebsd-smp@FreeBSD.ORG; Fri, 13 Apr 2001 16:09:07 -0400 Date: Fri, 13 Apr 2001 16:14:43 -0400 To: freebsd-smp@FreeBSD.ORG From: G.W.Adkins Subject: 4-way SMP on a Proliant 6500 under 4.2 X-Mailer: Opera 5.02 build 856a X-Priority: 3 (Normal) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Message-Id: Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I seem to be having trouble compiling a kernel under 4.2 which will boot on a 4 way PPro 200/1024K cache machine, it hangs early in the boot, while programming APIC #2. Is this a common thing? I've compiled dual SMP kernels with this release before, and they gave me no trouble at all... George Adkins To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message