From: scj@yaccman.com (scj@yaccman.com)
Subject: [TUHS] Early Unix function calls: expensive?
Date: Tue, 5 Jan 2016 12:26:44 -0800 [thread overview]
Message-ID: <afab31664ef8e081c99bcf2e3e0b014f.squirrel@webmail.yaccman.com> (raw)
In-Reply-To: <96168193-CFB6-433D-8085-4EDBDC0F564B@ronnatalie.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
> Ah, this brings back memories. We had this MACRO-11 concept called
> âthreaded codeâ (not threads in the multiprocessing sense).
> Essentially we had very small code fragments that were loaded into a table
> and weâd run them to process data with very light JSR/RET linkage
> (minimal register saves).
>
> Getting back to Richieâs idea of lightweight functions, it indeed is a
> more maintainable style and perhaps ahead of itâs time when modern
> highly optimized inlining compilers came around it made it efficient
> without the programmer needing to wrap his head around it too much.
>
It brought back memories for me, too. At Ardent, we had a 4-processor
system with each processor a vector processor. We wanted to be able to go
between parallel and serial very quickly, and the key to achieving this
was to have all 4 threads share the stack. So in the parallel sections,
all function calls had to be lightweight (only JSR/RET) and keep their
paws off some of the registers (including the stack pointer). It worked
beautifully, giving us a 3.99 times speedup with 4 processors when we were
in its sweet spot.
next prev parent reply other threads:[~2016-01-05 20:26 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-03 23:35 Warren Toomey
2016-01-03 23:53 ` Tim Bradshaw
2016-01-04 0:01 ` John Cowan
2016-01-04 4:40 ` Armando Stettner
2016-01-04 8:52 ` Tim Bradshaw
2016-01-04 17:29 ` Larry McVoy
2016-01-04 13:50 ` Clem Cole
2016-01-05 2:00 ` Ronald Natalie
2016-01-05 15:13 ` Clem Cole
2016-01-05 16:46 ` John Cowan
2016-01-05 17:33 ` Diomidis Spinellis
2016-01-05 17:42 ` Clem Cole
2016-01-05 17:28 ` Ronald Natalie
2016-01-05 17:43 ` Clem Cole
2016-01-05 17:46 ` Ronald Natalie
2016-01-05 18:03 ` Warner Losh
2016-01-05 18:24 ` Ronald Natalie
2016-01-05 20:26 ` scj [this message]
2016-01-05 20:49 ` John Cowan
2016-01-05 23:24 ` Dave Horsfall
2016-01-05 23:55 ` Ronald Natalie
2016-01-04 0:00 ` John Cowan
2016-01-04 0:42 ` scj
2016-01-04 11:35 ` Tony Finch
[not found] <mailman.3.1451865187.15972.tuhs@minnie.tuhs.org>
2016-01-04 1:08 ` Johnny Billquist
2016-01-04 1:29 ` Larry McVoy
2016-01-04 1:31 Noel Chiappa
2016-01-04 2:24 ` scj
2016-01-04 4:24 ` Larry McVoy
2016-01-04 1:59 Norman Wilson
2016-01-04 15:09 ` John Cowan
2016-01-04 2:21 Clem Cole
2016-01-04 12:53 Noel Chiappa
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=afab31664ef8e081c99bcf2e3e0b014f.squirrel@webmail.yaccman.com \
--to=scj@yaccman.com \
/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).