Return to BSD News archive
Newsgroups: comp.unix.bsd
Path: sserve!manuel.anu.edu.au!munnari.oz.au!spool.mu.edu!darwin.sura.net!mojo.eng.umd.edu!pandora.pix.com!stripes
From: stripes@pix.com (Josh Osborne)
Subject: Re: Adding Swapspace ??
Message-ID: <BwMr51.Gou@pix.com>
Sender: news@pix.com (The News Subsystem)
Nntp-Posting-Host: pandora.pix.com
Organization: Pix Technologies -- The company with no adult supervision
References: <1992Oct16.201806.21519@fcom.cc.utah.edu> <Bw8Mw5.IFC@pix.com> <1992Oct23.192806.22485@ninja.zso.dec.com>
Date: Sat, 24 Oct 1992 14:34:12 GMT
Lines: 22
In article <1992Oct23.192806.22485@ninja.zso.dec.com> alan@ulka.zso.dec.com (F. Alan Jones) writes:
[...]
>I believe that if you define secondary swap space it will "stripe" the
>access to them.
Well, sort of. (In 4.3 at least) the space on the disk was interleaved with
each chunk being as big as the largest single swap allocation could make
(a single sbrk can cause more then one swap alloc, this size is offen between
..5M and 2M). The blocks were then given out without regard to the device they
reside on. That will distribute I/O across N disks randomally, which isn't
quite striping.
> You can also do striping at the "pesudo-device" level
>and configure swap on such a device (without the file system inbetween).
Right, that's prob the best way to implment striping.
--
stripes@pix.com "Security for Unix is like
Josh_Osborne@Real_World,The Multitasking for MS-DOS"
"The dyslexic porgramer" - Kevin Lockwood
We all agree on the necessity of compromise. We just can't agree on
when it's necessary to compromise. - Larry Wall