From owner-cvs-all Tue Jul 18 14:56:44 2000 Delivered-To: cvs-all@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-51.dsl.snfc21.pacbell.net [63.202.177.51]) by hub.freebsd.org (Postfix) with ESMTP id 8D51E37B896; Tue, 18 Jul 2000 14:56:35 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA19358; Tue, 18 Jul 2000 15:05:24 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007182205.PAA19358@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/cam cam_ccb.h cam_xpt.c src/sys/cam/scsi scsi_all.c scsi_message.h src/sys/dev/aic7xxx aicasm_insformat.h 93cx6.c 93cx6.h ahc_eisa.c ahc_pci.c aic7xxx.c aic7xxx.h aic7xxx.reg aic7xxx.seq aicasm.c aicasm.h aicasm_gram.y ... In-reply-to: Your message of "Tue, 18 Jul 2000 13:29:23 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 Jul 2000 15:05:24 -0700 From: Mike Smith Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >Also- maybe it's time to start considering 64 bit PCI > > > > I'm hoping that being able to address 512GB will be enough > > for a while. I'd rather not expand the size of the S/G list > > members for address space no-one will be touching for the > > foreseeable future. > > Oh, I think I'm thinking more about the general PCI and bus_dma implementation > where we might consider starting to have 64 bit versions RSN..... Definitely. The current crop of Mylex products are all 64-bit aware, for example; even the 32-bit-wide devices support DAC and can thus directly address the 64-bit space with a supporting bridge. The first order of battle is going to be passing a busdma tag down from the nexus through each bus/bridge, which will have to modify it accordingly to constrain the path. This will let us get the 'parent' DMA tag from the parent, rather than inventing it in the PCI bus attach routines. We'll also need PCI bouncebuffering added to the PCI bus_dma code. I guess this is all pretty obvious, and the real question is just "who is going to do this". 8) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message