From owner-freebsd-current@FreeBSD.ORG Thu May 19 19:14:07 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C4CE916A4CE for ; Thu, 19 May 2005 19:14:07 +0000 (GMT) Received: from harmony.village.org (rover.village.org [168.103.84.182]) by mx1.FreeBSD.org (Postfix) with ESMTP id 51B5F43DAF for ; Thu, 19 May 2005 19:14:07 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (warner@rover2.village.org [10.0.0.1]) by harmony.village.org (8.13.3/8.13.1) with ESMTP id j4JJB1fZ076203; Thu, 19 May 2005 13:11:01 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Thu, 19 May 2005 13:11:15 -0600 (MDT) Message-Id: <20050519.131115.87763610.imp@bsdimp.com> To: nate@root.org From: "M. Warner Losh" In-Reply-To: <428CE32F.20307@root.org> References: <428C1EA6.7020907@root.org> <20050519104207.GA1259@shapeshifter.se> <428CE32F.20307@root.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: fli+freebsd-current@shapeshifter.se cc: current@FreeBSD.org Subject: Re: Patch to make powerd(8) devd(8)-aware X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 May 2005 19:14:07 -0000 In message: <428CE32F.20307@root.org> Nate Lawson writes: : Fredrik Lindberg wrote: : > On Wed, May 18, 2005 at 10:05:42PM -0700, Nate Lawson (nate@root.org) wrote: : > : >>I appreciate you working on a patch for this. However, I'd prefer the : >>work on the devd side go into making devctl a clonable device or follow : >>the bpf route and hook up /dev/devctl0,1,2,... If you start using the : >>/var/run/devd.pipe, it's not available for other consumers. : > : > Yes, devctl should probably be able to have more readers, I won't argue with that. : > However, devd allows any number of consumers to the devd.pipe. I've had : > upto 4 programs reading devd.pipe simultaneously and they all got the same data. : : Ah, I wasn't aware of that. I thought there might be a race for who got : each message. This is fine then, and perhaps we should retire devctl as : a way to read messages since it is limited for that purpose and : duplicates the pipe. We could keep it around for reverse signaling : (sending messages to the kernel, which is needed eventually). Ummm, devctl is the way that devd gets its info that it distributes to the pipe from the kernel. Can't easily eliminate it. The plan is also to add ioctls and/or sysctl so that devices can be told to detach, power off, etc. The exact form of these messages is still TBD. Warner