Date: Fri, 27 Feb 2004 14:43:57 +0000 From: Colin Percival <colin.percival@wadham.ox.ac.uk> To: Chris Elsworth <chris@shagged.org> Cc: freebsd-current@freebsd.org Subject: Re: mdconfig unable to allocate memory Message-ID: <6.0.1.1.1.20040227143620.03c72150@imap.sfu.ca> In-Reply-To: <20040227141717.GA53143@shagged.org> References: <20040227101410.GA45369@shagged.org> <xzpwu68d4xy.fsf@dwp.des.no> <20040227135836.GA52534@shagged.org> <6.0.1.1.1.20040227140137.03e01818@imap.sfu.ca> <20040227141717.GA53143@shagged.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 14:17 27/02/2004, Chris Elsworth wrote: > > The fact that running out of kernel address space can cause > > problems is quite well documented. > >Well, yes, but why would "vinum start" on a clean boot before any >tweaking (this is an out of the box 5.2.1-R) cause that? Surely the >kernel address space is sufficiently large just by self-tuning on a >machine with 4GB, for a vinum start to succeed? Sorry, I misread the order of events. Vinum is somewhat broken right now, but it shouldn't be that bad. >I think I'm just missing the point of having a swap backed memory >disk, really; I assumed that it would immediately start dumping >anything I put in it, into swap, causing disk access. Does it only put >stuff into swap once it runs out of address space? I believe that swap-backed memory disks are treated the same way as other pageable allocations: Kept in memory until / unless the amount of free memory drops below a given watermark. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.1.1.1.20040227143620.03c72150>