From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <3816729a-a9d5-4f63-9850-c7247edae37e@c16g2000yqe.googlegroups.com> Date: Fri, 2 Nov 2012 20:28:01 +0000 Message-ID: From: Charles Forsyth To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=047d7b3a7fe2dd911604cd88f835 Subject: Re: [9fans] Kernel panic when allocating a huge memory Topicbox-Message-UUID: d072b63a-ead7-11e9-9d60-3106f5b1d025 --047d7b3a7fe2dd911604cd88f835 Content-Type: text/plain; charset=UTF-8 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 unlocked during a critical period, a race, and so on.) On 2 November 2012 19:18, erik quanstrom wrote: > 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 > > > > -Skip > > > > On Fri, Nov 2, 2012 at 10:36 AM, Pavel Klinkovsky > > wrote: > > >>> It really seems as a problem with swap. :( > > >> > > >> this is well known, and solutions are available > > >> even if you don't care to use them. > > > > > > Oh, does it mean the official Plan 9 distribution contains non-working > swap? :O > > > It is clear I missed something... > > > > > > Sorry for the noise. > > 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). > > imo, swap needs to go. > > - erik > > --047d7b3a7fe2dd911604cd88f835 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 u= nlocked
during a critical period, a race, and so on.)



On 2 November 201= 2 19:18, erik quanstrom <quanstro@quanstro.net> wrote:
On F= ri Nov =C2=A02 15:10:00 EDT 2012, skip.tavakkolian@gmail.com wrote:
> it's by design:
> htt= p://9fans.net/archive/2006/07/229
>
> -Skip
>
> On Fri, Nov 2, 2012 at 10:36 AM, Pavel Klinkovsky
> <pavel.klinkovsky@gma= il.com> wrote:
> >>> It really seems as a problem with swap. :(
> >>
> >> this is well known, and solutions are available
> >> even if you don't care to use them.
> >
> > Oh, does it mean the official Plan 9 distribution contains non-wo= rking swap? :O
> > It is clear I missed something...
> >
> > Sorry for the noise.

i don't think that's quite fair to the current situatio= n. =C2=A0there
was a swapper, and it's broken. =C2=A0it should either be fixed or
removed. =C2=A0leaving 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).

imo, swap needs to go.

- erik


--047d7b3a7fe2dd911604cd88f835--