From owner-freebsd-current@FreeBSD.ORG  Wed Aug  6 05:35:12 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 645B437B401
	for <current@freebsd.org>; Wed,  6 Aug 2003 05:35:12 -0700 (PDT)
Received: from phk.freebsd.dk (phk.freebsd.dk [212.242.86.175])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7988543F3F
	for <current@freebsd.org>; Wed,  6 Aug 2003 05:35:11 -0700 (PDT)
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163])
	by phk.freebsd.dk (8.12.8/8.12.8) with ESMTP id h76CZ9V3030894
	for <current@freebsd.org>; Wed, 6 Aug 2003 12:35:09 GMT
	(envelope-from phk@phk.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.12.9/8.12.9) with ESMTP id h76CZ8PI041628
	for <current@freebsd.org>; Wed, 6 Aug 2003 14:35:09 +0200 (CEST)
	(envelope-from phk@phk.freebsd.dk)
To: current@freebsd.org
From: Poul-Henning Kamp <phk@phk.freebsd.dk>
Date: Wed, 06 Aug 2003 14:35:08 +0200
Message-ID: <41627.1060173308@critter.freebsd.dk>
Subject: [HEADSDOWN] swap_pager.c calming down...
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Aug 2003 12:35:12 -0000


I'm through with my first level of changes to swap_pager.c and the
results are better than even I had hoped.

The new per-device round-robin allocation performs a tad _better_
than the old striping when it comes to distribution of I/O requests
over multiple devices, given that there now is no upper limit on
the number of swap devices, this is a clear win-win.

For systems with less than the (previously) hardconfigured NSWAPDEV
limit, kernel malloc usage is lower, now we only allocate that space
which we need.

The next level of changes will be to go directly to GEOM for disk
devices, rather than take the detour over vnodes and specfs.
This will not happen in the first couple of weeks I suspect.

-- 
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.