From mboxrd@z Thu Jan 1 00:00:00 1970 References: <3816729a-a9d5-4f63-9850-c7247edae37e@c16g2000yqe.googlegroups.com> From: steve Content-Type: text/plain; charset=us-ascii In-Reply-To: Message-Id: <4A0E7310-9D9D-45C5-88A3-62B4A3191267@quintile.net> Date: Sat, 3 Nov 2012 06:53:24 +0000 To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: [9fans] Kernel panic when allocating a huge memory Topicbox-Message-UUID: d07fb196-ead7-11e9-9d60-3106f5b1d025 if you use the 9front distribution swap works, if you use the either 9atom or the labs distribution it does not. the labs or erik may take the fixes from 9front but there are good reasons for dropping swap all together - it is very slow, rarely used, and ram is cheap these days. i think this is a fair summary. -Steve On 3 Nov 2012, at 05:43, pmarin wrote: > To be clear, is the swap partition completely useless in Plan9? >=20 > pmarin. >=20 > On Fri, Nov 2, 2012 at 9:28 PM, Charles Forsyth > wrote: >> There's a non-trivial chance that what now goes wrong with paging >> (which did once work, even if it isn't great) is a symptom of a bug >> that afflicts the virtual memory code itself. (For instance, a page unloc= ked >> during a critical period, a race, and so on.) >>=20 >>=20 >>=20 >> On 2 November 2012 19:18, erik quanstrom wrote: >>>=20 >>> On Fri Nov 2 15:10:00 EDT 2012, skip.tavakkolian@gmail.com wrote: >>>> it's by design: >>>> http://9fans.net/archive/2006/07/229 >>>>=20 >>>> -Skip >>>>=20 >>>> On Fri, Nov 2, 2012 at 10:36 AM, Pavel Klinkovsky >>>> wrote: >>>>>>> It really seems as a problem with swap. :( >>>>>>=20 >>>>>> this is well known, and solutions are available >>>>>> even if you don't care to use them. >>>>>=20 >>>>> Oh, does it mean the official Plan 9 distribution contains non-working= >>>>> swap? :O >>>>> It is clear I missed something... >>>>>=20 >>>>> Sorry for the noise. >>>=20 >>> i don't think that's quite fair to the current situation. there >>> was a swapper, and it's broken. it should either be fixed or >>> removed. leaving the thing in in the state it's in (buffalo >>> buffalo?) doesn't make any sense, and is as seperate from >>> the question of whether to page (to disk) or not as, ahem, vm is from >>> paging (to disk). >>>=20 >>> imo, swap needs to go. >>>=20 >>> - erik >>=20