From owner-freebsd-arch@FreeBSD.ORG Mon May 22 13:35:21 2006 Return-Path: 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 155BC16A5C6 for ; Mon, 22 May 2006 13:35:21 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id C55D043D4C for ; Mon, 22 May 2006 13:35:20 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id E5EB346BE6 for ; Mon, 22 May 2006 09:35:19 -0400 (EDT) Date: Mon, 22 May 2006 14:35:19 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: arch@FreeBSD.org Message-ID: <20060522142619.X21787@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Reminder: intent to remove NET_NEEDS_GIANT() in 7.0 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 13:35:24 -0000 As part of preparing for the FreeBSD Developer Summit at BSDCan a couple of weeks ago, I reviewed remaining components of the network stack relying on NET_NEEDS_GIANT() to operate. The list was essentially this: - i4b - netatm - ng_h4 - KAME IPSEC - IP encapsulation in IPX The intent remains to remove compatibility support for non-MPSAFE network stack protocols for 7.0; the compatibility mode adds significant run-time overhead to the operation of the entire network stack when in operation. We cannot continue to operate supported network protocol features with Giant compatibility going forward. If you are a maintainer of one of the above subsystems, be warned that, effective August 1, 2006, you will no longer be able to rely on the socket and network driver layers acquiring Giant to synchronize data structures in your subsystem in the CVS HEAD. Please do whatever work is necessary to allow your network subsystem to operate under the current kernel synchronization architecture if you wish it to remain in the tree, as consumers of NET_NEEDS_GIANT() will start producing compile errors in the CVS HEAD as of August 1. As previously announced on this list, netatm is reaching thee end of its mortal life span in absence of a maintainer (it is already known not to work as a result of several years of decay), and unless it suddenly becomes MPSAFE and functional, will be removed from the CVS HEAD on June 30. I'm happy to help provide advice and information on migrating to a Giant-free synchronization model, but having already adopted several network protocols for this purpose (netatalk, netnatm, netipx, ...), I don't have time to maintain any additional ones, so need to rely on other maintainers to update these components. Thanks, Robert N M Watson From owner-freebsd-arch@FreeBSD.ORG Mon May 22 13:46:23 2006 Return-Path: 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 7348A16AB91; Mon, 22 May 2006 13:46:23 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0197E43D5E; Mon, 22 May 2006 13:46:22 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 440D146B0A; Mon, 22 May 2006 09:46:18 -0400 (EDT) Date: Mon, 22 May 2006 14:46:18 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: arch@FreeBSD.org Message-ID: <20060522144542.T21787@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Resend with subject: No more non-MPSAFE network device drivers, please! X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 13:46:27 -0000 This e-mail is just to remind device driver authors of something that I hope they were already aware of: as FreeBSD has been shipping with a network stack largely capable of running without Giant since the 5.x series, we will no longer be accepting new network device drivers that require Giant compatibility to function. This is true both for UP and SMP systems. Non-MPSAFE network device driver compatibility adds significant overhead to the operation of the network stack, and non-MPSAFE network device drivers pay a very high overhead to operate in the current environment. The compatibility code also complicates calling components which do not hold Giant, especially with regard to management ioctls. We have also discussed requiring that all network device drivers in the system for 7.0 be able to operate MPSAFE. This runs into some issues due to non-MPSAFEty of some key device driver subsystems, including Firewire, USB, and the TTY subsystem. Poul-Henning is in the process of working on MPSAFE tty support, and I hope that people will step up to the plate to work on the remaining subsystems in the near future. That way we will be able to remove the compatibility code, and continue cleanup and optimization work. Thanks, Robert N M Watson From owner-freebsd-arch@FreeBSD.ORG Mon May 22 13:56:00 2006 Return-Path: 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 3D89D16ABE8; Mon, 22 May 2006 13:56:00 +0000 (UTC) (envelope-from sem@FreeBSD.org) Received: from relay-er5.mbrd.ru (relay-er5.mbrd.ru [194.117.71.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id B13A243D48; Mon, 22 May 2006 13:55:59 +0000 (GMT) (envelope-from sem@FreeBSD.org) Received: from msd.mbrd.ru ([172.16.33.193]) by relay-er5.mbrd.ru with esmtpa (Exim 4.x) id 1FiAt2-000ClT-EO; Mon, 22 May 2006 17:55:56 +0400 Message-ID: <4471C2ED.3080703@FreeBSD.org> Date: Mon, 22 May 2006 17:55:57 +0400 From: Sergey Matveychuk User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Robert Watson References: <20060522144542.T21787@fledge.watson.org> In-Reply-To: <20060522144542.T21787@fledge.watson.org> X-Enigmail-Version: 0.93.2.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: arch@FreeBSD.org, freebsd-usb@freebsd.org Subject: Re: Resend with subject: No more non-MPSAFE network device drivers, please! X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 13:56:04 -0000 Robert Watson wrote: > This e-mail is just to remind device driver authors of something that I hope they were already aware of: as FreeBSD has been shipping with a network stack largely capable of running without Giant since the 5.x series, we will no longer be accepting new network device drivers that require Giant compatibility to function. This is true both for UP and SMP systems. > > Non-MPSAFE network device driver compatibility adds significant overhead to the operation of the network stack, and non-MPSAFE network device drivers pay a very high overhead to operate in the current environment. The compatibility code also complicates calling components which do not hold Giant, especially with regard to management ioctls. > > We have also discussed requiring that all network device drivers in the system for 7.0 be able to operate MPSAFE. This runs into some issues due to non-MPSAFEty of some key device driver subsystems, including Firewire, USB, and the TTY subsystem. Poul-Henning is in the process of working on MPSAFE tty support, and I hope that people will step up to the plate to work on the remaining subsystems in the near future. That way we will be able to remove the compatibility code, and continue cleanup and optimization work. > > Thanks, > > Robert N M Watson Looks like there are no developers right now who could rewrite USB stack to be MPSAFE. So all USB-Ethernet are broken. I gald if I mistake. -- Dixi. Sem. From owner-freebsd-arch@FreeBSD.ORG Mon May 22 14:02:05 2006 Return-Path: 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 3C30916ABAD; Mon, 22 May 2006 14:02:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id EAAFF43D45; Mon, 22 May 2006 14:02:00 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id AF84446BEB; Mon, 22 May 2006 10:01:59 -0400 (EDT) Date: Mon, 22 May 2006 15:01:59 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Sergey Matveychuk In-Reply-To: <4471C2ED.3080703@FreeBSD.org> Message-ID: <20060522145953.I21787@fledge.watson.org> References: <20060522144542.T21787@fledge.watson.org> <4471C2ED.3080703@FreeBSD.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@FreeBSD.org, freebsd-usb@freebsd.org Subject: Re: Resend with subject: No more non-MPSAFE network device drivers, please! X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 14:02:15 -0000 On Mon, 22 May 2006, Sergey Matveychuk wrote: >> We have also discussed requiring that all network device drivers in the >> system for 7.0 be able to operate MPSAFE. This runs into some issues due >> to non-MPSAFEty of some key device driver subsystems, including Firewire, >> USB, and the TTY subsystem. Poul-Henning is in the process of working on >> MPSAFE tty support, and I hope that people will step up to the plate to >> work on the remaining subsystems in the near future. That way we will be >> able to remove the compatibility code, and continue cleanup and >> optimization work. > > Looks like there are no developers right now who could rewrite USB stack to > be MPSAFE. So all USB-Ethernet are broken. Yes, hence this being something we are discussing, as opposed to implementing. In order for us to get to a world entirely without Giant-compatibility for network device drivers, we need to address the MPSAFEty of those major subsystems. The goal of this message was to make sure we don't start growing new major subsystems and network device drivers -- i.e., that we're into the realm of monotonically decreasing numbers of non-MPSAFE network device drivers. Specifically, I don't want to see any more PCI network device drivers that require Giant! Per discussion at the developer summit, a significant rewrite of the USB code is needed to make it MPSAFE. Volunteers welcome. Robert N M Watson From owner-freebsd-arch@FreeBSD.ORG Mon May 22 14:11:19 2006 Return-Path: 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 BB5BB16A6A9; Mon, 22 May 2006 14:11:19 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.FreeBSD.org (Postfix) with ESMTP id 07D9443D60; Mon, 22 May 2006 14:11:07 +0000 (GMT) (envelope-from des@des.no) Received: from tim.des.no (localhost [127.0.0.1]) by spam.des.no (Postfix) with ESMTP id BDD632086; Mon, 22 May 2006 16:10:56 +0200 (CEST) X-Spam-Tests: none X-Spam-Learn: disabled X-Spam-Score: 0.0/3.0 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on tim.des.no Received: from xps.des.no (des.no [80.203.243.180]) by tim.des.no (Postfix) with ESMTP id AF9822085; Mon, 22 May 2006 16:10:56 +0200 (CEST) Received: by xps.des.no (Postfix, from userid 1001) id 8D50733CAD; Mon, 22 May 2006 16:10:56 +0200 (CEST) From: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?=) To: Robert Watson References: <20060522144542.T21787@fledge.watson.org> <4471C2ED.3080703@FreeBSD.org> <20060522145953.I21787@fledge.watson.org> Date: Mon, 22 May 2006 16:10:55 +0200 In-Reply-To: <20060522145953.I21787@fledge.watson.org> (Robert Watson's message of "Mon, 22 May 2006 15:01:59 +0100 (BST)") Message-ID: <86y7wum9ow.fsf@xps.des.no> User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: arch@FreeBSD.org, freebsd-usb@freebsd.org, Sergey Matveychuk Subject: Re: Resend with subject: No more non-MPSAFE network device drivers, please! X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 14:11:20 -0000 Robert Watson writes: > Per discussion at the developer summit, a significant rewrite of the > USB code is needed to make it MPSAFE. Volunteers welcome. HP Selasky claims to have a working Giant-free USB stack: http://www.turbocat.net/~hselasky/usb4bsd/index.html No idea how well it works, though. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no From owner-freebsd-arch@FreeBSD.ORG Mon May 22 13:40:05 2006 Return-Path: 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 54C8F16A610; Mon, 22 May 2006 13:40:05 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id BFDBE43D4C; Mon, 22 May 2006 13:40:04 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 5E92E46CF3; Mon, 22 May 2006 09:40:04 -0400 (EDT) Date: Mon, 22 May 2006 14:40:04 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: arch@FreeBSD.org Message-ID: <20060522143521.J21787@fledge.watson.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Mailman-Approved-At: Mon, 22 May 2006 14:28:30 +0000 Cc: Subject: (no subject) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 13:40:06 -0000 This e-mail is just to remind device driver authors of something that I hope they were already aware of: as FreeBSD has been shipping with a network stack largely capable of running without Giant since the 5.x series, we will no longer be accepting new network device drivers that require Giant compatibility to function. This is true both for UP and SMP systems. Non-MPSAFE network device driver compatibility adds significant overhead to the operation of the network stack, and non-MPSAFE network device drivers pay a very high overhead to operate in the current environment. The compatibility code also complicates calling components which do not hold Giant, especially with regard to management ioctls. We have also discussed requiring that all network device drivers in the system for 7.0 be able to operate MPSAFE. This runs into some issues due to non-MPSAFEty of some key device driver subsystems, including Firewire, USB, and the TTY subsystem. Poul-Henning is in the process of working on MPSAFE tty support, and I hope that people will step up to the plate to work on the remaining subsystems in the near future. That way we will be able to remove the compatibility code, and continue cleanup and optimization work. Thanks, Robert N M Watson From owner-freebsd-arch@FreeBSD.ORG Mon May 22 15:55:11 2006 Return-Path: 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 X-X-Sender: mjacob@ns1.feral.com To: Robert Watson 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 List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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. From owner-freebsd-arch@FreeBSD.ORG Mon May 22 16:28:28 2006 Return-Path: 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 14DB616B871 for ; Mon, 22 May 2006 16:28:28 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id BDF1E43D4C for ; Mon, 22 May 2006 16:28:27 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 29EF446CCD; Mon, 22 May 2006 12:28:27 -0400 (EDT) Date: Mon, 22 May 2006 17:28:27 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Matthew Jacob In-Reply-To: <20060522085405.Y34519@ns1.feral.com> Message-ID: <20060522172636.Y21787@fledge.watson.org> References: <20060522143521.J21787@fledge.watson.org> <20060522085405.Y34519@ns1.feral.com> 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 List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 16:28:30 -0000 On Mon, 22 May 2006, Matthew Jacob wrote: >> 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. Yes -- we're beginning to reach the point where we can start issuing ultimatums on device drivers, but need USB and Firewire dealt with before we can begin to push out stragglers. For better or worse, those two hardware categories can't be ignored. Being at a point where we can universally make assumptions about MPSAFEty is a very good place to be, and we're very close with the network stack. I've been following Scott's CAM work in P4 with great interest, albeit little or no insight, since I know almost nothing about the SCSI layer. My brain is simply too small... Robert N M Watson From owner-freebsd-arch@FreeBSD.ORG Mon May 22 18:37:34 2006 Return-Path: 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 C40B916A893; Mon, 22 May 2006 18:37:34 +0000 (UTC) (envelope-from Danovitsch@vitsch.net) Received: from amsfep13-int.chello.nl (amsfep17-int.chello.nl [213.46.243.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54EF643D46; Mon, 22 May 2006 18:37:22 +0000 (GMT) (envelope-from Danovitsch@vitsch.net) Received: from Tuinhuisje.Vitsch.net ([62.195.87.223]) by amsfep13-int.chello.nl (InterMail vM.6.01.04.04 201-2131-118-104-20050224) with ESMTP id <20060522183720.KYJW21819.amsfep13-int.chello.nl@Tuinhuisje.Vitsch.net>; Mon, 22 May 2006 20:37:20 +0200 Received: from [192.168.87.6] (f23025.upc-f.chello.nl [80.56.23.25]) (authenticated bits=0) by Tuinhuisje.Vitsch.net (8.13.1/8.13.1) with ESMTP id k4MIb9ki033372; Mon, 22 May 2006 20:37:10 +0200 (CEST) (envelope-from Danovitsch@vitsch.net) From: "Daan Vreeken [PA4DAN]" Organization: Vitsch Electronics To: "Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=" Date: Mon, 22 May 2006 20:37:13 +0200 User-Agent: KMail/1.8.2 References: <20060522144542.T21787@fledge.watson.org> <20060522145953.I21787@fledge.watson.org> <86y7wum9ow.fsf@xps.des.no> In-Reply-To: <86y7wum9ow.fsf@xps.des.no> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200605222037.14030.Danovitsch@vitsch.net> Cc: Arch@freebsd.org, Sergey Matveychuk , Robert Watson , Freebsd-USB@freebsd.org, Hans Petter Selasky Subject: Re: Resend with subject: No more non-MPSAFE network device drivers, please! X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 18:37:37 -0000 On Monday 22 May 2006 16:10, Dag-Erling Sm=F8rgrav wrote: > Robert Watson writes: > > Per discussion at the developer summit, a significant rewrite of the > > USB code is needed to make it MPSAFE. Volunteers welcome. > > HP Selasky claims to have a working Giant-free USB stack: (added him to the 'cc' list) > http://www.turbocat.net/~hselasky/usb4bsd/index.html > > No idea how well it works, though. I have been running his USB driver on a production server for months here=20 without a single problem. I use his ugen implementation to communicate with= a=20 custom made USB device. On FreeBSD's USB driver a stress test would fail=20 after max 40,000 requests. With his USB driver I have successfully made ove= r=20 30,000,000 requests before stopping the test manually. There is a problem with his code though. (At least, there was back when I l= ast=20 looked at it, correct me if I'm wrong.) He has completely rewritten the OHC= I,=20 UHCI and EHCI parts, but kept the original (network, storage, etc) drivers.= =20 =46or the original drivers to work he has added some wrapper functions. Bac= k=20 when I looked these wrappers didn't work out of the box for the devices I=20 have tried. All "old" drivers need to be converter to "new world order" for them to wor= k=20 properly. That's the only problem I have been having with his driver : You get a bett= er=20 USB stack, but with less working drivers. I think it would be great to get his code into -current, but some developer= s=20 would have to help out to convert the existing drivers. =2D- Daan From owner-freebsd-arch@FreeBSD.ORG Mon May 22 19:17:43 2006 Return-Path: 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 BBDED16A772; Mon, 22 May 2006 19:17:43 +0000 (UTC) (envelope-from mistry.7@osu.edu) Received: from mail.united-ware.com (am-productions.biz [69.61.164.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id B435C43D6D; Mon, 22 May 2006 19:17:40 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.1.100] (mail.united-ware.com [69.61.164.22] (may be forged)) (authenticated bits=0) by mail.united-ware.com (8.13.4/8.13.6) with ESMTP id k4MJIhgq017021 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 22 May 2006 15:18:49 -0400 (EDT) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: freebsd-usb@freebsd.org, Hans Petter Selasky Date: Mon, 22 May 2006 15:17:29 -0400 User-Agent: KMail/1.9.1 References: <20060522144542.T21787@fledge.watson.org> <86y7wum9ow.fsf@xps.des.no> <200605222037.14030.Danovitsch@vitsch.net> In-Reply-To: <200605222037.14030.Danovitsch@vitsch.net> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart67549360.mrISMqu43M"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200605221518.03687.mistry.7@osu.edu> X-Spam-Status: No, score=-8.5 required=5.0 tests=ALL_TRUSTED,BAYES_50, MYFREEBSD2,MYFREEBSD3 autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on mail.united-ware.com X-Virus-Scanned: ClamAV 0.88.2/1475/Mon May 22 01:09:26 2006 on mail.united-ware.com X-Virus-Status: Clean Cc: "Daan Vreeken \[PA4DAN\]" , Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?= , Robert Watson , Arch@freebsd.org Subject: Re: Resend with subject: No more non-MPSAFE network device drivers, please! X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 19:17:44 -0000 --nextPart67549360.mrISMqu43M Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 22 May 2006 14:37, Daan Vreeken [PA4DAN] wrote: > On Monday 22 May 2006 16:10, Dag-Erling Sm=F8rgrav wrote: > > Robert Watson writes: > > > Per discussion at the developer summit, a significant rewrite > > > of the USB code is needed to make it MPSAFE. Volunteers > > > welcome. > > > > HP Selasky claims to have a working Giant-free USB stack: > > (added him to the 'cc' list) > > > http://www.turbocat.net/~hselasky/usb4bsd/index.html > > > > No idea how well it works, though. > > I have been running his USB driver on a production server for > months here without a single problem. I use his ugen implementation > to communicate with a custom made USB device. On FreeBSD's USB > driver a stress test would fail after max 40,000 requests. I've got a patch in a PR that fixes several ugen issues. > With his=20 > USB driver I have successfully made over 30,000,000 requests before > stopping the test manually. > > There is a problem with his code though. (At least, there was back > when I last looked at it, correct me if I'm wrong.) He has > completely rewritten the OHCI, UHCI and EHCI parts, but kept the > original (network, storage, etc) drivers. For the original drivers > to work he has added some wrapper functions. Back when I looked > these wrappers didn't work out of the box for the devices I have > tried. > All "old" drivers need to be converter to "new world order" for > them to work properly. > > That's the only problem I have been having with his driver : You > get a better USB stack, but with less working drivers. > I think it would be great to get his code into -current, but some > developers would have to help out to convert the existing drivers. I'd be willing to help convert drivers if we can get the code into the=20 tree (maybe as usb-ng?). Setting up a bounty for this stuff may be=20 worthwhile since having a solid USB stack would be a boon for=20 everyone. I'm not sure if it's possible with the HPS driver, but it would be=20 nice if every USB device could expose ugen endpoints along with their=20 device specific nodes. =2D-=20 Anish Mistry --nextPart67549360.mrISMqu43M Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQBEcg5rxqA5ziudZT0RAkFEAJ9p0HaaD9uecdAg1HZCRcWP5ntcVACgpyG2 jaEyQZPvohSIxl215FYKYy8= =pFvQ -----END PGP SIGNATURE----- --nextPart67549360.mrISMqu43M-- From owner-freebsd-arch@FreeBSD.ORG Mon May 22 20:39:02 2006 Return-Path: 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 AF40216AFBD; Mon, 22 May 2006 20:39:02 +0000 (UTC) (envelope-from ab@astralblue.net) Received: from purple.the-7.net (purple.the-7.net [207.158.28.23]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D63F43D4C; Mon, 22 May 2006 20:39:01 +0000 (GMT) (envelope-from ab@astralblue.net) Received: from [216.69.70.43] (bbq.nttmcl.com [216.69.70.43]) by purple.the-7.net (8.13.6/8.13.6) with ESMTP id k4MKcuYx032967; Mon, 22 May 2006 13:38:56 -0700 (PDT) (envelope-from ab@astralblue.net) Authentication-Results: purple.the-7.net from=ab@astralblue.net; sender-id=softfail; spf=softfail Message-ID: <447220E5.8080604@astralblue.net> Date: Mon, 22 May 2006 13:36:53 -0700 From: "Eugene M. Kim" User-Agent: Thunderbird 1.5.0.2 (Windows/20060308) MIME-Version: 1.0 To: Robert Watson References: <20060522143521.J21787@fledge.watson.org> <20060522085405.Y34519@ns1.feral.com> <20060522172636.Y21787@fledge.watson.org> In-Reply-To: <20060522172636.Y21787@fledge.watson.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org, Matthew Jacob Subject: Willing to adopt Firewire (was Re: your mail) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 20:39:09 -0000 Robert Watson wrote: > Yes -- we're beginning to reach the point where we can start issuing > ultimatums on device drivers, but need USB and Firewire dealt with > before we can begin to push out stragglers. For better or worse, > those two hardware categories can't be ignored. Being at a point > where we can universally make assumptions about MPSAFEty is a very > good place to be, and we're very close with the network stack. Quick question: Has anyone stepped up for MP-guarding Firewire and boys? I plan to begin hacking Firewire code soon (mainly to add support for 1394 audio devices), so I probably can adopt them if they've been orphaned. Eugene From owner-freebsd-arch@FreeBSD.ORG Mon May 22 20:47:03 2006 Return-Path: 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 1B88316A5B4 for ; Mon, 22 May 2006 20:47:03 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9003643D45 for ; Mon, 22 May 2006 20:47:02 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id DBEA746D01; Mon, 22 May 2006 16:46:56 -0400 (EDT) Date: Mon, 22 May 2006 21:46:56 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Eugene M. Kim" In-Reply-To: <447220E5.8080604@astralblue.net> Message-ID: <20060522214429.X246@fledge.watson.org> References: <20060522143521.J21787@fledge.watson.org> <20060522085405.Y34519@ns1.feral.com> <20060522172636.Y21787@fledge.watson.org> <447220E5.8080604@astralblue.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: arch@freebsd.org, Matthew Jacob Subject: Re: Willing to adopt Firewire (was Re: your mail) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 20:47:03 -0000 On Mon, 22 May 2006, Eugene M. Kim wrote: > Robert Watson wrote: >> Yes -- we're beginning to reach the point where we can start issuing >> ultimatums on device drivers, but need USB and Firewire dealt with before >> we can begin to push out stragglers. For better or worse, those two >> hardware categories can't be ignored. Being at a point where we can >> universally make assumptions about MPSAFEty is a very good place to be, and >> we're very close with the network stack. > > Quick question: Has anyone stepped up for MP-guarding Firewire and boys? I > plan to begin hacking Firewire code soon (mainly to add support for 1394 > audio devices), so I probably can adopt them if they've been orphaned. Not as far as I know -- I've not seen any real activity in the Firewire code in some time, and certainly no movement in the direction of making it MPSAFE. Your contribution here would be much appreciated! Robert N M Watson From owner-freebsd-arch@FreeBSD.ORG Mon May 22 20:49:07 2006 Return-Path: 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 6DEB116A4EE; Mon, 22 May 2006 20:49:07 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id 986CC43D46; Mon, 22 May 2006 20:49:06 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (r1rpegd7tz2f6pys@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k4MKmwji018199; Mon, 22 May 2006 13:48:58 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k4MKmrK3018198; Mon, 22 May 2006 13:48:53 -0700 (PDT) (envelope-from jmg) Date: Mon, 22 May 2006 13:48:53 -0700 From: John-Mark Gurney To: "Eugene M. Kim" Message-ID: <20060522204852.GL770@funkthat.com> Mail-Followup-To: "Eugene M. Kim" , Robert Watson , arch@freebsd.org, Matthew Jacob References: <20060522143521.J21787@fledge.watson.org> <20060522085405.Y34519@ns1.feral.com> <20060522172636.Y21787@fledge.watson.org> <447220E5.8080604@astralblue.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <447220E5.8080604@astralblue.net> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: Matthew Jacob , arch@freebsd.org, Robert Watson Subject: Re: Willing to adopt Firewire (was Re: your mail) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 20:49:10 -0000 Eugene M. Kim wrote this message on Mon, May 22, 2006 at 13:36 -0700: > Robert Watson wrote: > >Yes -- we're beginning to reach the point where we can start issuing > >ultimatums on device drivers, but need USB and Firewire dealt with > >before we can begin to push out stragglers. For better or worse, > >those two hardware categories can't be ignored. Being at a point > >where we can universally make assumptions about MPSAFEty is a very > >good place to be, and we're very close with the network stack. > > Quick question: Has anyone stepped up for MP-guarding Firewire and > boys? I plan to begin hacking Firewire code soon (mainly to add support > for 1394 audio devices), so I probably can adopt them if they've been > orphaned. Nope, not that I've heard... I regularly use firewire on my -current box, so I can help review/commit changes to firewire, or you can talk w/ simokawa about it too... We'll need to cordinate w/ simokawa anyways... /me wonders if simokawa goes to CBUG meetings. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arch@FreeBSD.ORG Mon May 22 21:00:11 2006 Return-Path: X-Original-To: freebsd-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 27DF216A46D for ; Mon, 22 May 2006 21:00:10 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.195]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A1CD43D49 for ; Mon, 22 May 2006 21:00:09 +0000 (GMT) (envelope-from asmrookie@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so961926wxd for ; Mon, 22 May 2006 14:00:09 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=LBk+M4Tz1MdFOPK89puvVnA1WP1Uiey/UCr2EHhDIfaoFLsEw1BBri511b9DMxVUpo6V0IuWZtw+mQk2FtDVOgGB3PyMs9fiim+INC+Mtv4nk4OzY6mUwqmUDGgFGjAewo34x0sSoZTly2a2+NPWKaqofHYO8+Svj9/3Jndqjow= Received: by 10.70.60.19 with SMTP id i19mr5610237wxa; Mon, 22 May 2006 14:00:09 -0700 (PDT) Received: by 10.70.38.10 with HTTP; Mon, 22 May 2006 14:00:09 -0700 (PDT) Message-ID: <3bbf2fe10605221400h16819083ja11d43574efd4f46@mail.gmail.com> Date: Mon, 22 May 2006 23:00:09 +0200 From: "Attilio Rao" To: freebsd-arch@freebsd.org In-Reply-To: <3bbf2fe10605221359y26176ffxaf3e1d41dc9af2ac@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 Content-Disposition: inline References: <20060522143521.J21787@fledge.watson.org> <20060522085405.Y34519@ns1.feral.com> <20060522172636.Y21787@fledge.watson.org> <447220E5.8080604@astralblue.net> <20060522214429.X246@fledge.watson.org> <3bbf2fe10605221359y26176ffxaf3e1d41dc9af2ac@mail.gmail.com> Subject: Re: Willing to adopt Firewire (was Re: your mail) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: rookie@gufi.org List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 21:00:11 -0000 MjAwNi81LzIyLCBSb2JlcnQgV2F0c29uIDxyd2F0c29uQGZyZWVic2Qub3JnPjoKPgo+IE9uIE1v biwgMjIgTWF5IDIwMDYsIEV1Z2VuZSBNLiBLaW0gd3JvdGU6Cj4KPiA+IFJvYmVydCBXYXRzb24g d3JvdGU6Cj4gPj4gWWVzIC0tIHdlJ3JlIGJlZ2lubmluZyB0byByZWFjaCB0aGUgcG9pbnQgd2hl cmUgd2UgY2FuIHN0YXJ0IGlzc3VpbmcKPiA+PiB1bHRpbWF0dW1zIG9uIGRldmljZSBkcml2ZXJz LCBidXQgbmVlZCBVU0IgYW5kIEZpcmV3aXJlIGRlYWx0IHdpdGggYmVmb3JlCj4gPj4gd2UgY2Fu IGJlZ2luIHRvIHB1c2ggb3V0IHN0cmFnZ2xlcnMuICBGb3IgYmV0dGVyIG9yIHdvcnNlLCB0aG9z ZSB0d28KPiA+PiBoYXJkd2FyZSBjYXRlZ29yaWVzIGNhbid0IGJlIGlnbm9yZWQuICBCZWluZyBh dCBhIHBvaW50IHdoZXJlIHdlIGNhbgo+ID4+IHVuaXZlcnNhbGx5IG1ha2UgYXNzdW1wdGlvbnMg YWJvdXQgTVBTQUZFdHkgaXMgYSB2ZXJ5IGdvb2QgcGxhY2UgdG8gYmUsIGFuZAo+ID4+IHdlJ3Jl IHZlcnkgY2xvc2Ugd2l0aCB0aGUgbmV0d29yayBzdGFjay4KPiA+Cj4gPiBRdWljayBxdWVzdGlv bjogSGFzIGFueW9uZSBzdGVwcGVkIHVwIGZvciBNUC1ndWFyZGluZyBGaXJld2lyZSBhbmQgYm95 cz8gIEkKPiA+IHBsYW4gdG8gYmVnaW4gaGFja2luZyBGaXJld2lyZSBjb2RlIHNvb24gKG1haW5s eSB0byBhZGQgc3VwcG9ydCBmb3IgMTM5NAo+ID4gYXVkaW8gZGV2aWNlcyksIHNvIEkgcHJvYmFi bHkgY2FuIGFkb3B0IHRoZW0gaWYgdGhleSd2ZSBiZWVuIG9ycGhhbmVkLgo+Cj4gTm90IGFzIGZh ciBhcyBJIGtub3cgLS0gSSd2ZSBub3Qgc2VlbiBhbnkgcmVhbCBhY3Rpdml0eSBpbiB0aGUgRmly ZXdpcmUgY29kZQo+IGluIHNvbWUgdGltZSwgYW5kIGNlcnRhaW5seSBubyBtb3ZlbWVudCBpbiB0 aGUgZGlyZWN0aW9uIG9mIG1ha2luZyBpdCBNUFNBRkUuCj4gWW91ciBjb250cmlidXRpb24gaGVy ZSB3b3VsZCBiZSBtdWNoIGFwcHJlY2lhdGVkIQoKQXMgSSBwb2ludGVkIG91dCBwcml2YXRlbHkg dG8gUm9iZXJ0LCBJIHdvdWxkIGxpa2UgdG8gd29yayBvbiBVU0IKc3RhY2sgaW4gb3JkZXIgdG8g bWFrZSBpdCBNUC1TQUZFLgpJIGRvbid0IGtub3cgaWYgSSBoYXZlIHRvIGNvb3JkaW5hdGUgd2l0 aCBzb21lYm9keSwgc2luY2UgdGhlIG9ubHkKcmVmZXJlbmNlIHdoaWNoIGxpdmVzIGluIHRoZSBj b2RlIGlzIGFib3V0IExlbm5hcnQgQXVndXN0c3NvbiBmcm9tCk5ldEJTRC4uLiB3aG8gaXMgcmVz cG9uc2libGUgZm9yIHRoaXMgcGFydCBvZiB0aGUgdHJlZT8KCkF0dGlsaW8KCi0tClBlYWNlIGNh biBvbmx5IGJlIGFjaGlldmVkIGJ5IHVuZGVyc3RhbmRpbmcgLSBBLiBFaW5zdGVpbgoKCi0tIApQ ZWFjZSBjYW4gb25seSBiZSBhY2hpZXZlZCBieSB1bmRlcnN0YW5kaW5nIC0gQS4gRWluc3RlaW4K From owner-freebsd-arch@FreeBSD.ORG Mon May 22 22:49:41 2006 Return-Path: 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 6154F16A798; Mon, 22 May 2006 22:49:41 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id D6E0B43D72; Mon, 22 May 2006 22:49:36 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [IPv6:::1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k4MMkgN9075129; Mon, 22 May 2006 16:46:42 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 May 2006 16:46:41 -0600 (MDT) Message-Id: <20060522.164641.74674575.imp@bsdimp.com> To: mistry.7@osu.edu From: Warner Losh In-Reply-To: <200605221518.03687.mistry.7@osu.edu> References: <86y7wum9ow.fsf@xps.des.no> <200605222037.14030.Danovitsch@vitsch.net> <200605221518.03687.mistry.7@osu.edu> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: des@des.no, Arch@freebsd.org, rwatson@freebsd.org, freebsd-usb@freebsd.org, hselasky@c2i.net Subject: Re: Resend with subject: No more non-MPSAFE network device drivers, please! X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 22:49:41 -0000 > I'd be willing to help convert drivers if we can get the code into the > tree (maybe as usb-ng?). Setting up a bounty for this stuff may be > worthwhile since having a solid USB stack would be a boon for > everyone. > I'm not sure if it's possible with the HPS driver, but it would be > nice if every USB device could expose ugen endpoints along with their > device specific nodes. Since I've been reviewing the HPS usb stack for a while now, I'd be happy to act as coordinator for efforts in this area. Warner From owner-freebsd-arch@FreeBSD.ORG Mon May 22 23:52:23 2006 Return-Path: X-Original-To: freebsd-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 8D1D216A901 for ; Mon, 22 May 2006 23:52:23 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout3.yahoo.com (mrout3.yahoo.com [216.145.54.173]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0C7D543D46 for ; Mon, 22 May 2006 23:52:23 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from minion.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout3.yahoo.com (8.13.6/8.13.4/y.out) with ESMTP id k4MNoEvY051254; Mon, 22 May 2006 16:50:14 -0700 (PDT) Date: Mon, 22 May 2006 16:50:11 -0700 Message-ID: From: gnn@freebsd.org To: Alexander Leidinger In-Reply-To: <20060522101825.adfzv59y1eogwocs@netchild.homeip.net> References: <200605181516.15541.hm@kts.org> <39318.1147960050@critter.freebsd.dk> <20060519143116.9iuvd81es0g0owkc@netchild.homeip.net> <20060522101825.adfzv59y1eogwocs@netchild.homeip.net> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Poul-Henning Kamp , hellmuth.michaelis@t-online.de, Julian Elischer , freebsd-arch@freebsd.org Subject: Re: doxygen target (was: Re: cvs commit: src Makefile.inc1 ObsoleteFiles.inc src/etc/defaults rc.conf src/etc/mtree BSD.usr.dist src/etc/rc.d Makefile isdnd pcvt syscons src/release/picobsd/build picobsd src/share/man/man4 Makefile atkbd.4 kbdmux.4 pcvt.4 splash.4 vkbd.4 ...) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 May 2006 23:52:24 -0000 At Mon, 22 May 2006 10:18:25 +0200, Alexander Leidinger wrote: > > Quoting gnn@neville-neil.com (from Sun, 21 May 2006 14:48:37 -0700): > > > At Fri, 19 May 2006 14:31:16 +0200, > > Alexander Leidinger wrote: > >> > >> Quoting "George V. Neville-Neil" (from Thu, 18 > >> May 2006 10:14:26 -0700): > >> > >> > I so hate to chime in on this thread, but I really think we need to > >> > start putting things into the code and using Doxygen, or a moral > >> > equivalent, to at least have a chance of keeping such things up to > >> > date. Someone a while back set up a proper Doxygen file for use with > >> > FreeBSD and we might simply pursue that tack. > >> > >> http://www.leidinger.net/FreeBSD/src_docs/ > >> http://www.leidinger.net/FreeBSD/FreeBSD-Dox.tar.bz2 > >> > >> Feel free to send/suggest further subsystems/improvements. > > > > The one thing I'd like to suggest is that this be made part of the > > tree with an optional make target. How should we go about doing that? > > We already have a doxygen config file in the tree, it covers the > entire kernel. But I think my approach of generating docs for > subsystems instead of the entire kernel may be more easy to understand > for people which want to understand a part of the kernel. > BTW I have move this to arch@ since I think it makes more sense there. > Regarding the make target, do you think about "cd /usr/src; make > doxygen" or about "cd /usr/src/; make doxygen"? Yes :-) It hsould be possible to be as specific or non-specific as possible. There can then be nightly builds of the docs, much like running global nightly to get cross references like I put up on codespelunking.org > The targets in the .tar.bz2 generate a HTML version too. Currently > the HTML version is around 300 MB, and it only covers a small part > of the kernel. Shall the HTML version also be generated (not > available online)? What about the destination, where do you want the > HTML version and/or the PDF version (needs pdflatex as a build tool) > to be placed (I can't come up with a good destination)? The HTML > version is generated by doxygen directly, the PDF needs to be > generated from the latex version, so in case of the PDF version it > would make sense to have a "doxygen" and "doxygeninstall" target, > but not for the HTML version (except you want to generate everything > in OBJDIR and then do a copy to the destination). > > Yes, I'm asking bikeshed questions... but only because I can't think > of a good answer myself ATM. My preference, and I'm not a Doxygen guru, is that we generate HTML from /usr/src into a /usr/doc directory, which is like /usr/obj, then some folks can serve /usr/doc on the net. Sub directory builds should make sub-directory doc directories. I.e. /usr/src/sys/netinet/doc. I think that /usr/src/sys is already a special root which gets a doc directory, and I think that's fine. For now I want to emphasize simplicity. THe other thing we need guidance on is, if people want to, how to most easily add clear annotations to soiurce that make Doxygen happy. A one page cheat sheet would go a long way towards making this usable by people who don't like to write documentation :-) Thanks, George From owner-freebsd-arch@FreeBSD.ORG Tue May 23 01:16:30 2006 Return-Path: X-Original-To: freebsd-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 9838316A421 for ; Tue, 23 May 2006 01:16:30 +0000 (UTC) (envelope-from fierykylin@gmail.com) Received: from wx-out-0102.google.com (wx-out-0102.google.com [66.249.82.200]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4DA943D49 for ; Tue, 23 May 2006 01:16:29 +0000 (GMT) (envelope-from fierykylin@gmail.com) Received: by wx-out-0102.google.com with SMTP id i31so991347wxd for ; Mon, 22 May 2006 18:16:29 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=QEpFA6lVc4gwaEx73BqcjoMmEDEovcYwDzHP0hV0fcmBR2SBJNnQwP3rSLaExwegcGLR8m5akIJM28HlzIfQHXVXTr3aciXHknACWBwS1aGiUnqpkWOEvavgWI1J5nihWtpMbRaZ4TSKFz1WjrrKOyGliubcZjLmpmEPyNAjXD0= Received: by 10.70.109.19 with SMTP id h19mr5334949wxc; Mon, 22 May 2006 18:16:29 -0700 (PDT) Received: by 10.70.43.11 with HTTP; Mon, 22 May 2006 18:16:29 -0700 (PDT) Message-ID: <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> Date: Tue, 23 May 2006 09:16:29 +0800 From: "william wallace" Sender: fierykylin@gmail.com To: "Warner Losh" In-Reply-To: <20060522.005010.104089663.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> X-Google-Sender-Auth: 748306afa86e69c9 Cc: "freebsd-hackers@freebsd.org" , freebsd-arch@freebsd.org Subject: Re: misc questions about the device&driver arch X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 01:16:30 -0000 I just have fossicked some idea from scottl@samsco.org "PCI-Express support= " PCI-Express support All, I've emailed before about supporting various aspects of PCI-Express and especially MSI, but haven't really gotten too far with it due to lack of resources. I now how access to a system that can do PCI-Express (PCI-E) so I'd like to revisit it and see what can be added for 5-STABLE. There are three general areas that need to be addressed in some form or another: Enhanced Configuration Space: PCI-E introduces an enhanced PCI Configuration space that allows for each function to have 4096 bytes of space instead of just 256. The Intel Lindenhurst chipset exposes this space via a memory-mapped window instead of the old slow type 1/2 ioport configuration methods. It appears that if the northbridge supports the enhanced config space then all PCI, PCI-X, and PCI-E devices will show up in it as well as in the legacy space. Proper support likely entails splitting up the pci host-bridge drivers so that a given ACPI or legacy front-end can plug into a given enhanced or legacy configuration layer. This definitely is not going to happen in time for 5.3, though. A hack that could work for 5-STABLE would be to provide pcie_[read|write]_config() methods that would compliment the existing pci methods and be available for drivers that want to access the >255 configuration addresses. Devices are already showing up that want to use these registers, btw. The mechanics of doing this would involve using pmap_mapdev() to map in the range that is specific to each function, and then hang this information off of the pcicfg structure. It's a bit hackish, yes, but it does seem to work in tests that a colleague of mine has done. MSI: I've bantered around different suggestions for an API that will support this. The basic thing that a driver needs from this is to know exactly how many message interrupt vectors are available to it. It can't just register vectors and handlers blindly since the purpose of MSI is to assign special meanings to each vector and allow the driver to handle each one in specifically. In order to keep the API as consistent as possible between classic interrupt sources and MSI sources, I'd like to add a new bus method: int bus_reserve_resource(device_t, int *start, int *end, int *count, int flags)= ; start, end, and count would be passed is as the desired range and would map to the per-function interrupt index in MSI. On return, the range supported and negotiated by the OS, bus, and function would be filled into these values. flags would be something like SYS_RES_MESSAGE. Internal failure of the function would be given in the return value. Whether failure to support MSI should be given as an error code return value can be debated. This function will also program the MSI configuration registers on the device to use the correct message cookie and number of messages. Interrupt registration would then proceed as normal with paired calls to bus_alloc_resource() and bus_setup_intr() for each desired interrupt index. The individual function interrupt index would be used as the start and end parameters to bus_alloc_resource(), and the type parameter would be SYS_RES_MESSAGE instead of SYS_RES_IRQ. bus_setup_intr() would unmask the source in the MSI APIC just like normal. Adding this for 5.3 is feasible, I think, and doesn't add a whole lot of risk. PCI-E provides a legacy mde for interrupts that simulates PCI interrupt lines, so drivers can choose whether to use MSI or the legacy interrupt methods. Hot-Plug, lane status, lane bonding: We don't have the infrastructure to support PCI or PCI-E hot-plug. It's also debatable whether this information will actually be available in a standard form. The PCI-E spec defines a new extended capabilities structure in the config space that can provide some of this information, but these kinds of things have a history of the vendors choosing their own proprietary methods and ignoring the standard. In short, we can't deal with this in the short term at all, and likely not in the long term without significant work to the bus and device infrastructure. On 5/22/06, Warner Losh wrote: > > > That happens at attach time. Cardbus right now has a private protoco= l > > > between the card bus bridge (cbb) and the bus to know when there's a > > > new card in a slot and to enumerate that bus. > > i think that 's because in cardbus protocol ,one bus only have one > > device ,so does pci express port (port :device =3D1:1) > > Cool. I just bought a new laptop yesterday. It has an expresscard > slot, which I think is handled as a PCI Express port (or USB 2.0 port, > depending on the card that's inserted). > > > so there will be a long list of methods in the future hotplug pci > > driver and pcib driver > > SHPC interface .. > > ....... > > PCIE interface > > ....... > > compaq interface > > ....... > > IBM interface .... > > ....... > > poer interface > > ....... > > Yes. If ExpressCard isn't handled by the PCIe interface, then we'd > want to add it to the list as well. > > Warner > --=20 we who r about to die,salute u! From owner-freebsd-arch@FreeBSD.ORG Tue May 23 02:07:32 2006 Return-Path: X-Original-To: freebsd-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 4533516A426; Tue, 23 May 2006 02:07:32 +0000 (UTC) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (gate.funkthat.com [69.17.45.168]) by mx1.FreeBSD.org (Postfix) with ESMTP id B20E343D48; Tue, 23 May 2006 02:07:31 +0000 (GMT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (yuojqcq06jdeuipr@localhost.funkthat.com [127.0.0.1]) by hydrogen.funkthat.com (8.13.4/8.13.3) with ESMTP id k4N27RRp027040; Mon, 22 May 2006 19:07:27 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: (from jmg@localhost) by hydrogen.funkthat.com (8.13.4/8.13.3/Submit) id k4N27QqC027039; Mon, 22 May 2006 19:07:26 -0700 (PDT) (envelope-from jmg) Date: Mon, 22 May 2006 19:07:26 -0700 From: John-Mark Gurney To: william wallace Message-ID: <20060523020726.GP770@funkthat.com> Mail-Followup-To: william wallace , Warner Losh , "freebsd-hackers@freebsd.org" , freebsd-arch@freebsd.org References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> User-Agent: Mutt/1.4.2.1i X-Operating-System: FreeBSD 5.4-RELEASE-p6 i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html Cc: "freebsd-hackers@freebsd.org" , freebsd-arch@freebsd.org Subject: Re: misc questions about the device&driver arch X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: John-Mark Gurney List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 02:07:32 -0000 william wallace wrote this message on Tue, May 23, 2006 at 09:16 +0800: > In order to keep the API as consistent as possible between classic > interrupt sources and MSI sources, I'd like to add a new bus method: > > int > bus_reserve_resource(device_t, int *start, int *end, int *count, int flags); > > start, end, and count would be passed is as the desired range and would > map to the per-function interrupt index in MSI. On return, the range > supported and negotiated by the OS, bus, and function would be filled > into these values. flags would be something like SYS_RES_MESSAGE. > Internal failure of the function would be given in the return value. > Whether failure to support MSI should be given as an error code return > value can be debated. This function will also program the MSI > configuration registers on the device to use the correct message cookie > and number of messages. Why not create a wrapper, and start at the highest requested, and slowly work your way down as the requests are rejected.. since the number of messages must be a power of two, it isn't than many rounds.. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-arch@FreeBSD.ORG Tue May 23 04:01:10 2006 Return-Path: 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 6886E16A421; Tue, 23 May 2006 04:01:10 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8E5A43D48; Tue, 23 May 2006 04:01:09 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [IPv6:::1] (may be forged)) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id k4N3xjEj078858; Mon, 22 May 2006 21:59:45 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Mon, 22 May 2006 21:59:45 -0600 (MDT) Message-Id: <20060522.215945.74674757.imp@bsdimp.com> To: rwatson@freebsd.org From: Warner Losh In-Reply-To: <20060522172636.Y21787@fledge.watson.org> References: <20060522143521.J21787@fledge.watson.org> <20060522085405.Y34519@ns1.feral.com> <20060522172636.Y21787@fledge.watson.org> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: arch@freebsd.org Subject: Re: your mail X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 04:01:10 -0000 > I've been following Scott's CAM work in P4 with great interest, > albeit little or no insight, since I know almost nothing about the > SCSI layer. My brain is simply too small... Well, the good news here is that we don't have any SCSI Ethernet support. Warner From owner-freebsd-arch@FreeBSD.ORG Tue May 23 05:20:34 2006 Return-Path: X-Original-To: freebsd-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 65E9C16A420; Tue, 23 May 2006 05:20:34 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8E41C43D46; Tue, 23 May 2006 05:20:31 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k4N5K1c8004598; Mon, 22 May 2006 23:20:06 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <44729B81.8010909@samsco.org> Date: Mon, 22 May 2006 23:20:01 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: william wallace References: <87ab37ab0605210108w127a235bue281428f52bbc784@mail.gmail.com> <20060521.114807.74702188.imp@bsdimp.com> <87ab37ab0605212328ue7c70fcu49c5fec8921ae229@mail.gmail.com> <20060522.005010.104089663.imp@bsdimp.com> <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> In-Reply-To: <87ab37ab0605221816y6cca5387sc43fa1e1116f55cc@mail.gmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org Cc: "freebsd-hackers@freebsd.org" , freebsd-arch@freebsd.org Subject: Re: misc questions about the device&driver arch X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 05:20:34 -0000 william wallace wrote: [...] > MSI: > I've bantered around different suggestions for an API that will support > this. The basic thing that a driver needs from this is to know > exactly how many message interrupt vectors are available to it. It > can't just register vectors and handlers blindly since the purpose of > MSI is to assign special meanings to each vector and allow the driver to > handle each one in specifically. [...] I just wanted to briefly say that an MSI implementation has been done recently, and that it should start getting wider circulation and review soon. That's not to say that more work and design can't be done in this area, but we should probably wait a bit and see what has been done already. Scott From owner-freebsd-arch@FreeBSD.ORG Tue May 23 10:11:58 2006 Return-Path: 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 19E7516A425; Tue, 23 May 2006 10:11:58 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe13.swipnet.se [212.247.155.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE45643D45; Tue, 23 May 2006 10:11:56 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== X-Cloudmark-Score: 0.000000 [] Received: from mp-217-36-191.daxnet.no ([193.217.36.191] verified) by mailfe13.swip.net (CommuniGate Pro SMTP 5.0.8) with ESMTP id 32073808; Tue, 23 May 2006 12:11:54 +0200 From: Hans Petter Selasky To: freebsd-arch@freebsd.org Date: Tue, 23 May 2006 12:11:52 +0200 User-Agent: KMail/1.7 References: <86y7wum9ow.fsf@xps.des.no> <200605221518.03687.mistry.7@osu.edu> <20060522.164641.74674575.imp@bsdimp.com> In-Reply-To: <20060522.164641.74674575.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605231211.55151.hselasky@c2i.net> Cc: mistry.7@osu.edu, Arch@freebsd.org, rwatson@freebsd.org, freebsd-usb@freebsd.org, des@des.no Subject: Re: Resend with subject: No more non-MPSAFE network device drivers, please! X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 10:11:58 -0000 On Tuesday 23 May 2006 00:46, Warner Losh wrote: > > I'd be willing to help convert drivers if we can get the code into the > > tree (maybe as usb-ng?). Setting up a bounty for this stuff may be > > worthwhile since having a solid USB stack would be a boon for > > everyone. > > I'm not sure if it's possible with the HPS driver, but it would be > > nice if every USB device could expose ugen endpoints along with their > > device specific nodes. This is not impossible with my USB stack, but one will have to make ugen a special USB device driver then, hence every time the configuration value is changed, the device nodes , /dev/ugenX.Y, must be re-created. Two drivers can set the configuration value, ugen and the device specific driver. Maybe one has got to put some restrictions here, like disabling ugen from changing the configuration value if a USB device driver is attached. Else changing the configuration value can lead to a detach of attached device drivers. That is the problem from what I can see. > > Since I've been reviewing the HPS usb stack for a while now, I'd be > happy to act as coordinator for efforts in this area. > One question is wether we should have the emulation layer for the old USB system or not. I mean it is not very solid, hence it can suddenly sleep due to memory allocations, when it is not allowed to sleep. And then the system will issue a panic(). Everything that is there to support the old USB API has been enclosed with: #ifdef USB_COMPAT_OLD #endif You might consider it for removal. I have volunteered to do some work on the USB stack and drivers as a part of summer of code, but it is not sure yet wether my project will be accepted or not. --HPS From owner-freebsd-arch@FreeBSD.ORG Tue May 23 10:11:58 2006 Return-Path: X-Original-To: freebsd-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 19E7516A425; Tue, 23 May 2006 10:11:58 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe13.swipnet.se [212.247.155.129]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE45643D45; Tue, 23 May 2006 10:11:56 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== X-Cloudmark-Score: 0.000000 [] Received: from mp-217-36-191.daxnet.no ([193.217.36.191] verified) by mailfe13.swip.net (CommuniGate Pro SMTP 5.0.8) with ESMTP id 32073808; Tue, 23 May 2006 12:11:54 +0200 From: Hans Petter Selasky To: freebsd-arch@freebsd.org Date: Tue, 23 May 2006 12:11:52 +0200 User-Agent: KMail/1.7 References: <86y7wum9ow.fsf@xps.des.no> <200605221518.03687.mistry.7@osu.edu> <20060522.164641.74674575.imp@bsdimp.com> In-Reply-To: <20060522.164641.74674575.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605231211.55151.hselasky@c2i.net> Cc: mistry.7@osu.edu, Arch@freebsd.org, rwatson@freebsd.org, freebsd-usb@freebsd.org, des@des.no Subject: Re: Resend with subject: No more non-MPSAFE network device drivers, please! X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 10:11:58 -0000 On Tuesday 23 May 2006 00:46, Warner Losh wrote: > > I'd be willing to help convert drivers if we can get the code into the > > tree (maybe as usb-ng?). Setting up a bounty for this stuff may be > > worthwhile since having a solid USB stack would be a boon for > > everyone. > > I'm not sure if it's possible with the HPS driver, but it would be > > nice if every USB device could expose ugen endpoints along with their > > device specific nodes. This is not impossible with my USB stack, but one will have to make ugen a special USB device driver then, hence every time the configuration value is changed, the device nodes , /dev/ugenX.Y, must be re-created. Two drivers can set the configuration value, ugen and the device specific driver. Maybe one has got to put some restrictions here, like disabling ugen from changing the configuration value if a USB device driver is attached. Else changing the configuration value can lead to a detach of attached device drivers. That is the problem from what I can see. > > Since I've been reviewing the HPS usb stack for a while now, I'd be > happy to act as coordinator for efforts in this area. > One question is wether we should have the emulation layer for the old USB system or not. I mean it is not very solid, hence it can suddenly sleep due to memory allocations, when it is not allowed to sleep. And then the system will issue a panic(). Everything that is there to support the old USB API has been enclosed with: #ifdef USB_COMPAT_OLD #endif You might consider it for removal. I have volunteered to do some work on the USB stack and drivers as a part of summer of code, but it is not sure yet wether my project will be accepted or not. --HPS From owner-freebsd-arch@FreeBSD.ORG Tue May 23 06:21:44 2006 Return-Path: X-Original-To: freebsd-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 8F5B316A427; Tue, 23 May 2006 06:21:44 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id DFE7543D45; Tue, 23 May 2006 06:21:42 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5D288.dip.t-dialin.net [84.165.210.136]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.4/8.13.1) with ESMTP id k4N69iTX017903; Tue, 23 May 2006 08:09:45 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.4/8.13.3) with ESMTP id k4N6LFgX037938; Tue, 23 May 2006 08:21:15 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from pslux.cec.eu.int (pslux.cec.eu.int [158.169.9.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Tue, 23 May 2006 08:21:15 +0200 Message-ID: <20060523082115.v4832wbvhcgccwwk@netchild.homeip.net> X-Priority: 3 (Normal) Date: Tue, 23 May 2006 08:21:15 +0200 From: Alexander Leidinger To: gnn@freebsd.org References: <200605181516.15541.hm@kts.org> <39318.1147960050@critter.freebsd.dk> <20060519143116.9iuvd81es0g0owkc@netchild.homeip.net> <20060522101825.adfzv59y1eogwocs@netchild.homeip.net> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new X-Mailman-Approved-At: Tue, 23 May 2006 12:03:39 +0000 Cc: Poul-Henning Kamp , hellmuth.michaelis@t-online.de, Julian Elischer , freebsd-arch@freebsd.org Subject: Re: doxygen target (was: Re: cvs commit: src Makefile.inc1 ObsoleteFiles.inc src/etc/defaults rc.conf src/etc/mtree BSD.usr.dist src/etc/rc.d Makefile isdnd pcvt syscons src/release/picobsd/build picobsd src/share/man/man4 Makefile atkbd.4 kbdmux.4 pcvt.4 splash.4 vkbd.4 ...) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 May 2006 06:21:45 -0000 Quoting gnn@freebsd.org (from Mon, 22 May 2006 16:50:11 -0700): > At Mon, 22 May 2006 10:18:25 +0200, > Alexander Leidinger wrote: >> Regarding the make target, do you think about "cd /usr/src; make >> doxygen" or about "cd /usr/src/; make doxygen"? > > Yes :-) It hsould be possible to be as specific or non-specific as > possible. There can then be nightly builds of the docs, much like > running global nightly to get cross references like I put up on > codespelunking.org I try to come up with the /usr/src doxygen target first. >> The targets in the .tar.bz2 generate a HTML version too. Currently >> the HTML version is around 300 MB, and it only covers a small part >> of the kernel. Shall the HTML version also be generated (not >> available online)? What about the destination, where do you want the >> HTML version and/or the PDF version (needs pdflatex as a build tool) >> to be placed (I can't come up with a good destination)? The HTML >> version is generated by doxygen directly, the PDF needs to be >> generated from the latex version, so in case of the PDF version it >> would make sense to have a "doxygen" and "doxygeninstall" target, >> but not for the HTML version (except you want to generate everything >> in OBJDIR and then do a copy to the destination). >> >> Yes, I'm asking bikeshed questions... but only because I can't think >> of a good answer myself ATM. > > My preference, and I'm not a Doxygen guru, is that we generate HTML > from /usr/src into a /usr/doc directory, which is like /usr/obj, then Sounds fine to me. One directory per subsystem if we go the split-up way. > some folks can serve /usr/doc on the net. Sub directory builds should > make sub-directory doc directories. I.e. /usr/src/sys/netinet/doc. I > think that /usr/src/sys is already a special root which gets a doc > directory, and I think that's fine. For now I want to emphasize > simplicity. I'm not sure the subdirectory builds are that simple to implement in a =20 generic fashion (I have to play around with some ideas here...). =20 Adding a target by hand to each interesting subdirectory is easy. > THe other thing we need guidance on is, if people want to, how to most > easily add clear annotations to soiurce that make Doxygen happy. A > one page cheat sheet would go a long way towards making this usable by > people who don't like to write documentation :-) I think http://www.stack.nl/~dimitri/doxygen/docblocks.html provides a =20 good start (until someone writes doxygen_style(9) :-) ). A FAQ is available at http://www.stack.nl/~dimitri/doxygen/faq.html =20 and http://www.stack.nl/~dimitri/doxygen/commands.html contains a list =20 of all doxygen recognized documentation-commands. Bye, Alexander. --=20 Selling GoodYear Eagle F1 235/40ZR18, 2x 4mm + 2x 5mm, ~150 EUR you have to pick it up between Germany/Saarland and Luxembourg/Capellen http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137 From owner-freebsd-arch@FreeBSD.ORG Wed May 24 06:14:12 2006 Return-Path: X-Original-To: freebsd-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 3978516A424 for ; Wed, 24 May 2006 06:14:12 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout2-b.corp.dcn.yahoo.com (mrout2-b.corp.dcn.yahoo.com [216.109.112.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3548943D49 for ; Wed, 24 May 2006 06:14:11 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from unknown-10-72-12-208.yahoo.com.neville-neil.com (proxy7.corp.yahoo.com [216.145.48.98]) by mrout2-b.corp.dcn.yahoo.com (8.13.6/8.13.4/y.out) with ESMTP id k4O6DeHe058108; Tue, 23 May 2006 23:13:41 -0700 (PDT) Date: Tue, 23 May 2006 16:30:36 -0700 Message-ID: From: "George V. Neville-Neil" To: Alexander Leidinger In-Reply-To: <20060523082115.v4832wbvhcgccwwk@netchild.homeip.net> References: <200605181516.15541.hm@kts.org> <39318.1147960050@critter.freebsd.dk> <20060519143116.9iuvd81es0g0owkc@netchild.homeip.net> <20060522101825.adfzv59y1eogwocs@netchild.homeip.net> <20060523082115.v4832wbvhcgccwwk@netchild.homeip.net> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Poul-Henning Kamp , freebsd-arch@freebsd.org, Julian Elischer , hellmuth.michaelis@t-online.de Subject: Re: doxygen target (was: Re: cvs commit: src Makefile.inc1 ObsoleteFiles.inc src/etc/defaults rc.conf src/etc/mtree BSD.usr.dist src/etc/rc.d Makefile isdnd pcvt syscons src/release/picobsd/build picobsd src/share/man/man4 Makefile atkbd.4 kbdmux.4 pcvt.4 splash.4 vkbd.4 ...) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 May 2006 06:14:12 -0000 At Tue, 23 May 2006 08:21:15 +0200, Alexander Leidinger wrote: > I'm not sure the subdirectory builds are that simple to implement in > a generic fashion (I have to play around with some ideas here...). > Adding a target by hand to each interesting subdirectory is easy. OK, so probably only the set you've already done would be first. > > > THe other thing we need guidance on is, if people want to, how to most > > easily add clear annotations to soiurce that make Doxygen happy. A > > one page cheat sheet would go a long way towards making this usable by > > people who don't like to write documentation :-) > > I think http://www.stack.nl/~dimitri/doxygen/docblocks.html provides a > good start (until someone writes doxygen_style(9) :-) ). I'll look at that. > A FAQ is available at http://www.stack.nl/~dimitri/doxygen/faq.html > and http://www.stack.nl/~dimitri/doxygen/commands.html contains a > list of all doxygen recognized documentation-commands. Thanks, George From owner-freebsd-arch@FreeBSD.ORG Fri May 26 13:36:00 2006 Return-Path: X-Original-To: freebsd-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 68ACB16A438 for ; Fri, 26 May 2006 13:36:00 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from home.quip.cz (grimm.quip.cz [213.220.192.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id D823743D5E for ; Fri, 26 May 2006 13:35:58 +0000 (GMT) (envelope-from 000.fbsd@quip.cz) Received: from [192.168.1.2] (qwork.quip.test [192.168.1.2]) by home.quip.cz (Postfix) with ESMTP id BD8DA1A79; Fri, 26 May 2006 15:35:55 +0200 (CEST) Message-ID: <4477043B.7050401@quip.cz> Date: Fri, 26 May 2006 15:35:55 +0200 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: cs, cz, en, en-us MIME-Version: 1.0 To: Alexander Leidinger References: <20060415182413.GA8729@troutmask.apl.washington.edu> <20060416151128.5959ce56@Magellan.Leidinger.net> In-Reply-To: <20060416151128.5959ce56@Magellan.Leidinger.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-arch@freebsd.org Subject: Re: Google's summer of code topics? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 13:36:00 -0000 Alexander Leidinger wrote: > Feel free to submit an entry for http://www.freebsd.org/projects/ideas/ > (plain text is enough). It should be similar to the existing entries > there. > > Bye, > Alexander. I don't know where to submit project ideas, so I describe it here. I would like to see something like EclipseBSD QoS in current (6.x / 7.x) version of FreeBSD. (EclipseBSD project page: http://www.bell-labs.com/project/eclipse/release/). It means proportional-share cpu, disk and link schedulers with API to manipulate reservations. It would be nice in cooperation with Jails, so we could assign some maximal percentage of CPU / RAM / disk / net etc. per Jail. (the idea is very similar to Linux vserver implementation, but AFAIK EclipseBSD is earlier project [actual in FreeBSD 3.x days]) Because I am not a C programmer, it is just an idea for volunteers / Google's summer of code. Miroslav Lachman From owner-freebsd-arch@FreeBSD.ORG Fri May 26 15:45:17 2006 Return-Path: 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 3BC6F16A444 for ; Fri, 26 May 2006 15:45:17 +0000 (UTC) (envelope-from rink@rink.nu) Received: from mx0.rink.nu (morion.rink.nu [80.112.228.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id 24EFF43D82 for ; Fri, 26 May 2006 15:44:34 +0000 (GMT) (envelope-from rink@rink.nu) Received: from localhost (localhost [127.0.0.1]) by mx0.rink.nu (Postfix) with ESMTP id 8D63D3B for ; Fri, 26 May 2006 17:42:27 +0200 (CEST) Received: from mx0.rink.nu ([127.0.0.1]) by localhost (morion.rink.nu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12538-01 for ; Fri, 26 May 2006 17:42:09 +0200 (CEST) Received: by mx0.rink.nu (Postfix, from userid 1678) id F3CB63C; Fri, 26 May 2006 17:42:08 +0200 (CEST) Date: Fri, 26 May 2006 17:42:08 +0200 From: Rink Springer To: arch@FreeBSD.org Message-ID: <20060526154208.GD9715@rink.nu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HlL+5n6rz5pIUxbD" Content-Disposition: inline User-Agent: Mutt/1.5.11 X-Virus-Scanned: amavisd-new at rink.nu Cc: Subject: [RFC] Minor crunchgen patch X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 15:45:19 -0000 --HlL+5n6rz5pIUxbD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi, Apart from the syslogd patch, I have written a minor patch for crunchgen, which allows you to specify arguments to pass to all invoked make(1) instances. I used this to specify an alternative system makefile path (using -m), this made it much easier to build crunchgen(1)-ed binaries for -CURRENT on a -STABLE box (due to the new build knobs infrastructure). This is part of my FreeBSD/xbox installation/livecd, which will be released in a few days. You can find the patch at http://www.il.fontys.nl/~rink/crunchgen.diff. I intend to commit next week and MFC it after a few days. Thanks! --=20 Rink P.W. Springer - http://rink.nu "Richter: Tribute? You steal men's souls, and make them your slaves! Dracula: Perhaps the same could be said of all religions." - Castlevania: Symphony of the Night --HlL+5n6rz5pIUxbD Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (FreeBSD) iD8DBQFEdyHQb3O60uztv/8RApjlAJwOUPCxLErMbUUKy/8lEGv31pdKOACgwTvV PUdLpK/SiSUWYEyprvzhmxw= =2wMN -----END PGP SIGNATURE----- --HlL+5n6rz5pIUxbD-- From owner-freebsd-arch@FreeBSD.ORG Fri May 26 18:48:05 2006 Return-Path: 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 5DE8416AE64 for ; Fri, 26 May 2006 18:48:05 +0000 (UTC) (envelope-from ru@ip.net.ua) Received: from cielago.ip.net.ua (cielago.ip.net.ua [82.193.96.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id E41D043D6E for ; Fri, 26 May 2006 18:48:01 +0000 (GMT) (envelope-from ru@ip.net.ua) Received: from heffalump.ip.net.ua (heffalump.ip.net.ua [82.193.96.213]) by cielago.ip.net.ua (8.13.6/8.13.6) with ESMTP id k4QIl1OO017000 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 May 2006 21:47:02 +0300 (EEST) (envelope-from ru@ip.net.ua) Received: (from ru@localhost) by heffalump.ip.net.ua (8.13.6/8.13.6) id k4QIleZ0095688; Fri, 26 May 2006 21:47:40 +0300 (EEST) (envelope-from ru) Date: Fri, 26 May 2006 21:47:40 +0300 From: Ruslan Ermilov To: Rink Springer Message-ID: <20060526184740.GA95451@ip.net.ua> References: <20060526154208.GD9715@rink.nu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: <20060526154208.GD9715@rink.nu> User-Agent: Mutt/1.5.11 X-Virus-Scanned: by amavisd-new Cc: arch@freebsd.org Subject: Re: [RFC] Minor crunchgen patch X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 18:48:17 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, May 26, 2006 at 05:42:08PM +0200, Rink Springer wrote: > Hi, >=20 > Apart from the syslogd patch, I have written a minor patch for > crunchgen, which allows you to specify arguments to pass to all invoked > make(1) instances. >=20 > I used this to specify an alternative system makefile path (using -m), > this made it much easier to build crunchgen(1)-ed binaries for -CURRENT > on a -STABLE box (due to the new build knobs infrastructure). This is > part of my FreeBSD/xbox installation/livecd, which will be released in a > few days. >=20 > You can find the patch at http://www.il.fontys.nl/~rink/crunchgen.diff. > I intend to commit next week and MFC it after a few days. > What, the MAKEFLAGS environment variable supported by make(1) is not sufficient? Cheers,=20 --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEd01MqRfpzJluFF4RAuRDAJ42Tmo6HCekd4csh45geKOQ5/e9yACfR6JC 5kBi1v+sTYGzmmzmAsVbq+g= =8/OM -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J-- From owner-freebsd-arch@FreeBSD.ORG Fri May 26 20:54:56 2006 Return-Path: X-Original-To: freebsd-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 1CEA416B913 for ; Fri, 26 May 2006 20:54:56 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7F03E43D62 for ; Fri, 26 May 2006 20:54:43 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5FC6A.dip.t-dialin.net [84.165.252.106]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.4/8.13.4) with ESMTP id k4QKg4UA065018; Fri, 26 May 2006 22:42:07 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from Magellan.Leidinger.net (Magellan.Leidinger.net [192.168.1.1]) by Andro-Beta.Leidinger.net (8.13.4/8.13.3) with ESMTP id k4QIU256064942; Fri, 26 May 2006 20:30:02 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Date: Fri, 26 May 2006 20:30:03 +0200 From: Alexander Leidinger To: "George V. Neville-Neil" Message-ID: <20060526203003.26cd6db7@Magellan.Leidinger.net> In-Reply-To: References: <200605181516.15541.hm@kts.org> <39318.1147960050@critter.freebsd.dk> <20060519143116.9iuvd81es0g0owkc@netchild.homeip.net> <20060522101825.adfzv59y1eogwocs@netchild.homeip.net> <20060523082115.v4832wbvhcgccwwk@netchild.homeip.net> X-Mailer: Sylpheed-Claws 2.2.0 (GTK+ 2.8.17; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new Cc: Poul-Henning Kamp , freebsd-arch@FreeBSD.org, Julian Elischer , hellmuth.michaelis@t-online.de Subject: Re: doxygen target (was: Re: cvs commit: src Makefile.inc1 ObsoleteFiles.inc src/etc/defaults rc.conf src/etc/mtree BSD.usr.dist src/etc/rc.d Makefile isdnd pcvt syscons src/release/picobsd/build picobsd src/share/man/man4 Makefile atkbd.4 kbdmux.4 pcvt.4 splash.4 vkbd.4 ...) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 20:55:04 -0000 Quoting "George V. Neville-Neil" (Tue, 23 May 2006 16:30:36 -0700): > At Tue, 23 May 2006 08:21:15 +0200, > Alexander Leidinger wrote: > > I'm not sure the subdirectory builds are that simple to implement in > > a generic fashion (I have to play around with some ideas here...). > > Adding a target by hand to each interesting subdirectory is easy. > > OK, so probably only the set you've already done would be first. I've just committed the framework. Currently it's connected to the top-level Makefile which generates all HTML docs in OBJDIR. To build only specific subsystems and/or the PDF docs, you have to go to /usr/src/sys/doc/subsys and run make (you will see a message with available targets). The README tells you which programs you need to have installed and how to add more subsystems. I want to revise some defaults (e.g. destination directory, ...), but as it is now, people can start playing around with it (and it may be helpful for our SoC students). Oh, yes, you need a little bit of time or a very fast machine to generate all docs. In case someone wants to improve the framework, go ahead. I will not add further subsystems soon (except someone sends in a config for it) or change the doxygen configuration. My goals for the near term are to talk with doc@ how we can get the HTML version online (we're talking about several hundred MB) and because of this the default destination directory may change. An open task is to make "make doc" work in subsystem directories (e.g. via "cd /usr/src/sys/doc/subsys && ${MAKE} SUBSYS_TARGET mumble=${.CURDIR}) as requested in this thread, but I don't expect to work on this in the next days. Bye, Alexander. -- Selling GoodYear Eagle F1 235/40ZR18, 2x 4mm + 2x 5mm, ~150 EUR you have to pick it up between Germany/Saarland and Luxembourg/Capellen http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 From owner-freebsd-arch@FreeBSD.ORG Fri May 26 23:23:18 2006 Return-Path: X-Original-To: freebsd-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 3531116ADC7 for ; Fri, 26 May 2006 23:23:18 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1-b.corp.dcn.yahoo.com (mrout1-b.corp.dcn.yahoo.com [216.109.112.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id A9ECD43D46 for ; Fri, 26 May 2006 23:23:17 +0000 (GMT) (envelope-from gnn@neville-neil.com) Received: from traveling-laptop-140.corp.yahoo.com.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout1-b.corp.dcn.yahoo.com (8.13.6/8.13.4/y.out) with ESMTP id k4QNMYlX016282; Fri, 26 May 2006 16:22:35 -0700 (PDT) Date: Sat, 27 May 2006 08:22:29 +0900 Message-ID: From: gnn@neville-neil.com To: Alexander Leidinger In-Reply-To: <20060526203003.26cd6db7@Magellan.Leidinger.net> References: <200605181516.15541.hm@kts.org> <39318.1147960050@critter.freebsd.dk> <20060519143116.9iuvd81es0g0owkc@netchild.homeip.net> <20060522101825.adfzv59y1eogwocs@netchild.homeip.net> <20060523082115.v4832wbvhcgccwwk@netchild.homeip.net> <20060526203003.26cd6db7@Magellan.Leidinger.net> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/22.0.50 (i386-apple-darwin8.5.1) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: Poul-Henning Kamp , hellmuth.michaelis@t-online.de, Julian Elischer , freebsd-arch@freebsd.org Subject: Re: doxygen target (was: Re: cvs commit: src Makefile.inc1 ObsoleteFiles.inc src/etc/defaults rc.conf src/etc/mtree BSD.usr.dist src/etc/rc.d Makefile isdnd pcvt syscons src/release/picobsd/build picobsd src/share/man/man4 Makefile atkbd.4 kbdmux.4 pcvt.4 splash.4 vkbd.4 ...) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 May 2006 23:23:19 -0000 At Fri, 26 May 2006 20:30:03 +0200, Alexander Leidinger wrote: > I've just committed the framework. Currently it's connected to the > top-level Makefile which generates all HTML docs in OBJDIR. To build > only specific subsystems and/or the PDF docs, you have to go > to /usr/src/sys/doc/subsys and run make (you will see a message with > available targets). Excellent. I'll cvsup and try to play with it. Later, George From owner-freebsd-arch@FreeBSD.ORG Sat May 27 21:19:05 2006 Return-Path: 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 4F84C16B4E2 for ; Sat, 27 May 2006 21:18:29 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from pfepc.post.tele.dk (pfepc.post.tele.dk [195.41.46.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id C626C43D4C for ; Sat, 27 May 2006 21:18:28 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (0x50a07cfc.naenxx7.adsl-dhcp.tele.dk [80.160.124.252]) by pfepc.post.tele.dk (Postfix) with ESMTP id 12FD38A0010 for ; Sat, 27 May 2006 23:18:26 +0200 (CEST) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.6/8.13.6) with ESMTP id k4RLIOlM016030 for ; Sat, 27 May 2006 23:18:25 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: arch@freebsd.org From: Poul-Henning Kamp Date: Sat, 27 May 2006 23:18:24 +0200 Message-ID: <16029.1148764704@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Subject: A sort of plan for consoles in FreeBSD X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 May 2006 21:19:13 -0000 We have four concepts of "console" in FreeBSD: 1. Whatever boot0/boot1/boot2/loader uses Accessed from/via native boot/firmware environment 2. The boot/DDB/printf(9)/panic(9) console ("The low-level console"). Polled operation since interrupts may not be working. 3. The tty which /sbin/init uses for single-user and /etc/rc Can be any tty, but convention has been "/dev/console" 4. The /dev/console device in multi-user mode. Emergency output device for critical messages. Most often they will all four end up referring to the same piece of hardware (a good thing), but do not let this confuse you into beliving they are one and the same thing. The problem I'm trying to solve involves #4, the /dev/console device which currently has a rather nasty way of forcing the underlying console device driver open. Seen in the light of history, spitting messages out on /dev/console was the right thing to do back in the 1980ies, but the operators, (or tape-monkeys as we were called back then), and their DecWriter terminals hooked up to the VAX780 computers exist only in museums these days, and they didn't run FreeBSD7 anyway. Today we expect all relevant logging to happen to logfiles, either directly (like for instance apache provides for) or via syslogd(8), which adds the ability to send the logs to a remote machine in real-time. Spitting things out on /dev/console today will more likely than not, print stuff on a syscons or serial port which nobody looks at. For that reason, we added a hack to the kernel to make all stuff that went to /dev/console be sent to syslogd(8). I would like to redefine the semantics of "/dev/console" as follows: if any console-consumers like xconsole(8) are active send output to all console-consumers. else if a controlling terminal is available send output to controlling terminal (that is /dev/tty) else send output to syslogd, as if generated by printf(9). (but do not actually output to low-level console) If xconsole(8) or similar programs are run, or if syslogd(8) is told to record all console output, they will get what they expect. Alternatively, we try to send the message to the relevant user and if that fails (for daemons) we log it in syslog. This also involves number #3 from the list because today /sbin/init opens /dev/console for single user mode and /etc/rc. But /sbin/init can use any tty device so adding the necessary code to make the low-level console communicate the relevant tty name to /sbin/init, possibly making it overridable from the loader with a hint, will take care of that. Comments, ideas, suggestions etc welcome Poul-Henning -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.