From owner-freebsd-arch@FreeBSD.ORG  Mon May 22 15:55:11 2006
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
X-Original-To: arch@FreeBSD.org
Delivered-To: freebsd-arch@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2B29016A625;
	Mon, 22 May 2006 15:55:11 +0000 (UTC) (envelope-from mj@feral.com)
Received: from ns1.feral.com (ns1.feral.com [192.67.166.1])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B073243D45;
	Mon, 22 May 2006 15:55:10 +0000 (GMT) (envelope-from mj@feral.com)
Received: from ns1.feral.com (localhost [127.0.0.1])
	by ns1.feral.com (8.13.6/8.13.6) with ESMTP id k4MFtAMv034561;
	Mon, 22 May 2006 08:55:10 -0700 (PDT) (envelope-from mj@feral.com)
Received: from localhost (mjacob@localhost)
	by ns1.feral.com (8.13.6/8.13.6/Submit) with ESMTP id k4MFtAB3034558;
	Mon, 22 May 2006 08:55:10 -0700 (PDT) (envelope-from mj@feral.com)
X-Authentication-Warning: ns1.feral.com: mjacob owned process doing -bs
Date: Mon, 22 May 2006 08:55:10 -0700 (PDT)
From: Matthew Jacob <mj@feral.com>
X-X-Sender: mjacob@ns1.feral.com
To: Robert Watson <rwatson@FreeBSD.org>
In-Reply-To: <20060522143521.J21787@fledge.watson.org>
Message-ID: <20060522085405.Y34519@ns1.feral.com>
References: <20060522143521.J21787@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: arch@FreeBSD.org
Subject: Re: your mail
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Matthew Jacob <mj@feral.com>
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 22 May 2006 15:55:11 -0000

>
> Non-MPSAFE network device driver compatibility adds significant overhead to

I agree. I'm appalled at mixing the two. I had several years of that at 
Sun, thank you very much.

CAM and all assocated drives should be MPSAFE. Period. Scott is working 
on this how.