From: "Lluís Batlle i Rossell" <viric@viric.name>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9pi + apple keyboard
Date: Sat, 26 Jan 2013 12:59:21 +0100 [thread overview]
Message-ID: <20130126115921.GN2324@vicerveza.homeunix.net> (raw)
In-Reply-To: <9aaa301130543ac6bc01a5b08a6133be@ladd.quanstro.net>
On Wed, Jan 23, 2013 at 04:10:48PM -0500, erik quanstrom wrote:
> On Wed Jan 23 10:49:47 EST 2013, quanstro@quanstro.net wrote:
> > > Interesting results, thank you!
> > > The difference between the Pi and the Sheeva is quite huge,
> > > I wasn't excepting such difference. This seems to confirm my
> > > initial thoughts regarding the Atom perfs.
> >
> > that's just for floating point, which the sheeva doesn't have.
> > the newer model from the same line does have floating point:
> >
> > http://www.globalscaletechnologies.com/p-58-mirabox-development-kit.aspx
>
> richard, thanks for the floating point. this is good stuff.
> this is better than 100x faster:
>
> ; >/dev/null time factor 281476419553081
> 146.60u 0.01s 148.24r factor 281476419553081
> ; >/dev/null time /sys/src/cmd/5.factor 281476419553081
> 1.20u 0.01s 1.22r /sys/src/cmd/5.factor 281476419553081
Umh how does 'factor' relate to a FPU?
I don't have a plan9 running there, but the gnu 'factor' runs in 2.2s in
a raspberrypi, and 0.05s in a sheevaplug, here.
> (burncycles calculates the digits of pi using a taylor series
> expansion. it uses all the tricks in the book to generate as
> few bits of the result per cycle possible, without being verbose,
> obtuse, or off task. obviously, it was an accident.
> the very fast machines have the advantage of non-emulated
> vlongs, running amd64 kernels)
What are these emulated vlongs? Would that mean an atom computer would run
relevantly faster i686 code over x86_64 code?
Regards,
Lluís.
next prev parent reply other threads:[~2013-01-26 11:59 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 10:31 James Chapman
2013-01-22 10:39 ` Richard Miller
2013-01-22 10:58 ` James Chapman
2013-01-22 17:02 ` a
2013-01-22 17:06 ` erik quanstrom
2013-01-22 17:45 ` Nicolas Bercher
2013-01-22 18:50 ` Aram Hăvărneanu
2013-01-23 7:46 ` Lyndon Nerenberg
2013-01-22 21:36 ` erik quanstrom
2013-01-23 10:36 ` Richard Miller
2013-01-23 10:55 ` Lluís Batlle i Rossell
2013-01-23 12:11 ` Richard Miller
2013-01-23 15:45 ` Nicolas Bercher
2013-01-23 15:48 ` erik quanstrom
2013-01-23 21:10 ` erik quanstrom
2013-01-23 22:21 ` Richard Miller
2013-01-23 22:37 ` erik quanstrom
2013-01-23 23:15 ` Richard Miller
2013-01-23 23:33 ` erik quanstrom
2013-01-24 1:37 ` erik quanstrom
2013-01-24 10:29 ` Phineas Pett
2013-01-24 12:42 ` lucio
2013-01-24 13:06 ` Phineas Pett
2013-01-24 13:33 ` lucio
2013-01-24 13:40 ` Richard Miller
2013-01-24 14:55 ` lucio
2013-01-24 20:56 ` Steve Simon
2013-01-24 15:16 ` erik quanstrom
2013-01-26 11:59 ` Lluís Batlle i Rossell [this message]
2013-01-26 12:12 ` erik quanstrom
2013-01-26 13:18 ` Lluís Batlle i Rossell
2013-01-23 8:05 ` Harri Haataja
2013-01-23 10:45 ` Richard Miller
2013-01-23 12:05 ` James Chapman
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=20130126115921.GN2324@vicerveza.homeunix.net \
--to=viric@viric.name \
--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).