From owner-freebsd-arch@FreeBSD.ORG Thu Jul 17 11:18:54 2003 Return-Path: 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 48F0237B401 for ; Thu, 17 Jul 2003 11:18:54 -0700 (PDT) Received: from HAL9000.homeunix.com (ip114.bella-vista.sfo.interquest.net [66.199.86.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3BA4743F93 for ; Thu, 17 Jul 2003 11:18:53 -0700 (PDT) (envelope-from das@freebsd.org) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.9/8.12.9) with ESMTP id h6HIITLv048849; Thu, 17 Jul 2003 11:18:29 -0700 (PDT) (envelope-from das@freebsd.org) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.9/8.12.9/Submit) id h6HIISiU048848; Thu, 17 Jul 2003 11:18:28 -0700 (PDT) (envelope-from das@freebsd.org) Date: Thu, 17 Jul 2003 11:18:28 -0700 From: David Schultz To: Poul-Henning Kamp Message-ID: <20030717181828.GA48738@HAL9000.homeunix.com> Mail-Followup-To: Poul-Henning Kamp , arch@freebsd.org, Luoqi Chen , John De Boskey References: <20030714170024.GA27936@HAL9000.homeunix.com> <8011.1058461818@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8011.1058461818@critter.freebsd.dk> cc: arch@freebsd.org cc: Luoqi Chen cc: John De Boskey Subject: Re: swap partition > 4G X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jul 2003 18:18:54 -0000 On Thu, Jul 17, 2003, Poul-Henning Kamp wrote: > In message <20030714170024.GA27936@HAL9000.homeunix.com>, David Schultz writes: > > >As far as moving the responsibility for striping swap to ccd(4) is > >concerned, that sounds like a step in the right direction. > >However, it's a completely orthogonal issue. > > Fully agreed. > > >The ~150 bogus lines > >of code that could be killed have nothing to do with the size > >limitation. Also note that ccd(4) can't fix all of the bogosity. > >For instance, you're still stuck with static striping, and you > >have to pretend that (MAXDEVS - curdevs) packs are full. > > First of all, there is little point in striping things the way it > is done today, it would probably be equally efficient, if not more > so (due to larger chunks being possible), to concatenate the swapon'ed > devices and allocate from the in a round-robin or even, now that > we have the statistics supporting such decisions, based on > disk-busyness. We will be able to do that with ccd(4)? Cool! Having a way to stripe based on disk business and add and remove space dynamically is basically what I was looking for. How would the interface work, though? I assumed you would just have the swap subsystem use one big virtual concatenated device, but that seems to limit ccd's ability to make any striping decisions dynamically, since ccd only understands read and write, not allocate and free.