From: lm@mcvoy.com (Larry McVoy)
Subject: [TUHS] Article on 'not meant to understand this'
Date: Sun, 15 Jan 2017 19:15:10 -0800 [thread overview]
Message-ID: <20170116031510.GB6647@mcvoy.com> (raw)
In-Reply-To: <20170116014444.GA32261@minnie.tuhs.org>
Yeah, saw it. I'm of the opinion that you aren't really truly an OS
person unless you've written a context switcher. I wrote one for a
user level threading package I did for Udi Manber as a grad student.
I did most of the work in C and then dropped to assembler for the
trampoline.
It's really not that complicated, I think people make it out to be
a bigger deal than it is. You're saving state (registers), switching
stacks, and changing the return address so you return in the new
process.
Well, not that complicated on a simple machine line a VAX or a 68K
or a PDP11. I sort of stopped playing in assembler when super scalar
out of order stuff came around and I couldn't get the mental picture
of what was where.
On Mon, Jan 16, 2017 at 11:44:44AM +1000, Warren Toomey wrote:
> http://thenewstack.io/not-expected-understand-explainer/
>
> in case you haven't seen it yet.
>
> Cheers, Warren
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2017-01-16 3:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 1:44 Warren Toomey
2017-01-16 3:15 ` Larry McVoy [this message]
2017-01-16 10:11 ` Brantley Coile
2017-01-16 17:49 ` Marc Rochkind
2017-01-16 11:19 ` Tony Finch
2017-01-16 11:26 ` Angelo Papenhoff
2017-01-16 15:35 ` Random832
2017-01-16 17:16 Noel Chiappa
2017-01-16 19:10 Steve Johnson
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=20170116031510.GB6647@mcvoy.com \
--to=lm@mcvoy.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).