From owner-freebsd-hackers@FreeBSD.ORG Tue Nov 29 19:55:00 2005 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E151C16A422 for ; Tue, 29 Nov 2005 19:54:59 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from speedfactory.net (mail6.speedfactory.net [66.23.216.219]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01D3C43D6A for ; Tue, 29 Nov 2005 19:54:51 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (unverified [66.23.211.162]) by speedfactory.net (SurgeMail 3.5b3) with ESMTP id 2822667 for multiple; Tue, 29 Nov 2005 14:55:02 -0500 Received: from localhost (john@localhost [127.0.0.1]) by server.baldwin.cx (8.13.1/8.13.1) with ESMTP id jATJse3g074079; Tue, 29 Nov 2005 14:54:45 -0500 (EST) (envelope-from jhb@freebsd.org) From: John Baldwin To: kylin Date: Tue, 29 Nov 2005 14:49:44 -0500 User-Agent: KMail/1.8.2 References: <87ab37ab0511032030o134b9316j83295dd303e4e44b@mail.gmail.com> <200511061007.03634.jhb@FreeBSD.org> <87ab37ab0511100248n474f3ee1wd952ae3f12cbecc3@mail.gmail.com> In-Reply-To: <87ab37ab0511100248n474f3ee1wd952ae3f12cbecc3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200511291449.46391.jhb@freebsd.org> X-Spam-Status: No, score=-2.8 required=4.2 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on server.baldwin.cx X-Server: High Performance Mail Server - http://surgemail.com r=1653887525 Cc: freebsd-hackers@freebsd.org Subject: Re: misc questions about the device&driver arch X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Nov 2005 19:55:00 -0000 On Thursday 10 November 2005 05:48 am, kylin wrote: > Sir ,i am still puzzled by the windows and freebsd arch similar. > 1 > the window TPS say that windwo allocate the resource window in default > size of 1M or 2M,so there may be hole ,does that happen in freebsd 5 > or 6? No. > 2 > in my view i believe that freebsd us the "just enough "tactics,so > the nexus level of resource view is ===continuous====with NO hole in > a boot up system, IF hot remove do not happen .am i right? Sorta. We actually will use whatever the BIOS uses by default. We only try to alloc resources if the BIOS doesn't, and I'm not sure how we handle a bridge running out of resources. I think we might just fail the allocation. > 3 > IF i do a PCI hotplug under a bridge, and the bridge 's MEM Window is > full ,i have to do reballacne (including use the device_pause > method:)), and if i can not declaim the resource from other bridge > because "nexus level of resource view is ===continuous====with NO hole > ", can i extend the physical address space beyond the boot time > locate range to PCI host bridge ? Well, if you had device_pause() you would be able to shuffle resources from one bridge to another perhaps. Preallocating bigger chunks as your first question suggested might be a lot simpler though not completely fool proof. > On 11/6/05, John Baldwin wrote: > > On Sunday 06 November 2005 06:14 am, kylin wrote: > > > On 11/6/05, M. Warner Losh wrote: > > > > In message: > > > > <87ab37ab0511032030o134b9316j83295dd303e4e44b@mail.gmail.com> > > > > > > > > kylin writes: > > > > : /////////////// > > > > : pci bridge dynamic resize > > > > : ///////////// > > > > : it seems that the device arch of freebsd is similar to what is > > > > : revealed in window OS. i have read the pcie hotplug tps of windows > > > > : longhorn ,it is said that with some hardware mechanisms the pci > > > > : bridge driver can do global pci resource window reconfiguration.so > > > > : good to the hotplugin pci device for it avoid prelocating resource > > > > : for the device . > > > > : i wonder ,if the mem /io/irq reconfiguration possible under freebsd > > > > : .:) 1 > > > > > > > > Yes. Cardbus does it all the time. However, there's no pcie > > > > hot-plug support yet, so the process for kicking off configuration of > > > > the new device doesn't happen. > > > > > > > > Warner > > > > > > sorry for my poor grammar ,i think i confused the public:) i will make > > > myself clear with the words below about the PCI Multi-level Rebalance > > > > > > PCI Multi-level Rebalance in Windows Longhorn > > > Updated: November 25, 2003 > > > > No, FreeBSD doesn't currently do what this decribes yet. It would be > > possible to do it by adding a new device_pause() method that drivers > > would be required to implement while the resources were shuffled around > > though and possibly a device_unpause() method so that they could update > > their state if their resources were changed while the device was paused. > > > > -- > > John Baldwin <>< http://www.FreeBSD.org/~jhb/ > > "Power Users Use the Power to Serve" = http://www.FreeBSD.org > > -- > we who r about to die,salute u! -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org