9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9 go output faults on 9vx with rfork
Date: Wed, 19 Jan 2011 22:59:09 -0800	[thread overview]
Message-ID: <AANLkTi=OE2_rZ=ktiw-Rq0c0cHYZVBu9EVtoXhA_UY0z@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinAe_r2EbqOHZGVjaN8yDbhja0m5MUuJfMrn6Cs@mail.gmail.com>

OK, Pavel sent me a nice piece of code that implements cmpswap using a
gcc trick. I did not want to use the trick for a few reasons, and
thought to use futex instead, as it seemed appropriate. Weirdly
enough, I can not find a simple implementation of cmpswap that uses
futex, though I can find several papers describing how tricky futex
is, and one Linux person who told me that futex had evolved in ways
not necessarily to our advantage.

Every time I'm ready to throw in the towel on Plan 9 and just go with
Linux I hit something like futex and it's back into the fray ... :-)

So, I have committed changes to my vx32 repo and Pavel's sieve now
works on 9vx on a 32-bit linux vmware image. It should also work if
you build on freebsd. It should also work if you build on 64-bit linux
but there are no guarantees, since all this relies on some gcc
builtins.

You can see what I've done if you look at my repo.

BTW, the sieve ran to 17xxx on linux and then I got some kind of
malloc failure, I'll assume it's another 32-bit gc issue. I'm up to
57917 on osx.

You're going to need Pavel's mods to go, I suppose. but that's another story ...

ron



       reply	other threads:[~2011-01-20  6:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikJ3y5exFtTic+8dhUsUqeZBDmR=S-8VzKDK0GH@mail.gmail.com>
     [not found] ` <AANLkTink4CrELJfGf3W15caSYX8Se5ygsm_WeMRdCBz=@mail.gmail.com>
     [not found]   ` <AANLkTikUa1KF+8NP54BHicus++YbeZbD48E7z=1H0Y5V@mail.gmail.com>
     [not found]     ` <AANLkTinAe_r2EbqOHZGVjaN8yDbhja0m5MUuJfMrn6Cs@mail.gmail.com>
2011-01-20  6:59       ` ron minnich [this message]
2011-01-20 16:48         ` David Leimbach
     [not found]         ` <AANLkTintaOjTpC6Eaz3Ka7256KXYzaDeYg3jsqbCT5Wx@mail.gmail.com>
     [not found]           ` <AANLkTim3MH0t6H1522DnHf-P_E7a0rtt6FzY9f3ti10i@mail.gmail.com>
     [not found]             ` <AANLkTi=1btTKGVd_gKk+abAjTEwsEPMBhP4L3agrDubg@mail.gmail.com>
     [not found]               ` <AANLkTimuhE_G46f0J3nRBos1kVSDvTvUwvUb8u0RsR4A@mail.gmail.com>
     [not found]                 ` <AANLkTiki2v5MgdxwgjQpJopnrRQhBXKm80+aua_FFAef@mail.gmail.com>
     [not found]                   ` <AANLkTi=fi2Xm0R1Jx2NcrKUkyJaYqnizDP0xJPgaenMY@mail.gmail.com>
2011-01-23  2:43                     ` ron minnich
2011-01-23  2:48                       ` erik quanstrom
2011-01-23  2:56                         ` ron minnich
2011-01-23  3:00                           ` erik quanstrom
2011-01-23 19:20                             ` Charles Forsyth
2011-01-23 19:15                               ` Devon H. O'Dell
2011-01-23 20:40                                 ` EBo
2011-01-23 22:00                                   ` ron minnich
2011-01-24 12:11                                     ` EBo
2011-01-24 17:18                                     ` yy
2011-01-24 17:24                                       ` erik quanstrom
2011-01-25 14:28                                         ` Richard Miller
2011-01-24 17:24                                       ` ron minnich
2011-02-08  0:05                                         ` yy
2011-01-24 20:02                                       ` Steve Simon
2011-01-23 23:40                                   ` Charles Forsyth
2011-01-24  1:18                                     ` ron minnich
2011-01-24 12:17                                       ` EBo
2011-01-24 17:16                                         ` ron minnich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='AANLkTi=OE2_rZ=ktiw-Rq0c0cHYZVBu9EVtoXhA_UY0z@mail.gmail.com' \
    --to=rminnich@gmail.com \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).