From: Perry Smith <email@example.com> To: firstname.lastname@example.org Subject: Re: Parallel processing Date: Mon, 28 Mar 2022 08:47:18 -0500 [thread overview] Message-ID: <1193520F-22B1-4786-AA20-E9B0FE9D1596@easesoftware.com> (raw) In-Reply-To: <20220327113705.1799@sachi> > On Mar 27, 2022, at 13:37, jdh <email@example.com> wrote: > > Re: the phrase "parallel processing": > > So that beginners do not get the wrong idea I wish to make clear that Unix based systems are not designed to, and can not do parallel processing. Strictly speaking it is also not designed to do real time processing. Unix/Linux does do multitasking by using task switching. Unix based systems does allow users with the proper priviledge to set task priority, which helps in deciding which task gets more run time. Well… drifting off the original topic: parallel processing, real time processing, and SMP are all somewhat orthogonal concepts from each other. The original "parallel processing" systems ran a version of AT&T unix (e.g. Sequent). It predated SMP. Or I suppose you could say that IBM was doing parallel processing even before that. “Real time” processing is requirements that responses to events fall within the manufacture’s specifications. i.e. “all context switches are guaranteed to occur within 50ms”. Then the designers of the end applications can work with those constraints and develop systems that meet the requirements of their end users. SMP is about the very tight coupling between the CPUs. Apple’s latest glossy keynote on the M1 Ultra gives a whiff of the problems that parallel processing introduces which SMP solves.
next prev parent reply other threads:[~2022-03-28 13:48 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-03-27 18:37 jdh 2022-03-27 19:06 ` Bart Schaefer 2022-03-27 19:24 ` Ray Andrews 2022-03-28 13:47 ` Perry Smith [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-03-26 4:34 jdh 2022-03-25 4:34 Perry Smith 2022-03-25 18:27 ` Bart Schaefer 2022-03-26 18:10 ` Philippe Troin 2022-03-26 22:19 ` Bart Schaefer 2022-03-27 17:32 ` Philippe Troin 2022-03-27 17:42 ` Bart Schaefer 2022-03-27 19:23 ` Dominik Vogt 2022-03-28 13:26 ` Perry Smith 2022-03-28 13:31 ` Perry Smith
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=1193520F-22B1-4786-AA20-E9B0FE9D1596@easesoftware.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Parallel processing' \ /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
Code repositories for project(s) associated with this inbox: https://git.vuxu.org/mirror/zsh/ 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).