From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: try-this-for ?
Date: Thu, 18 Jan 2018 14:16:40 +0100 [thread overview]
Message-ID: <20180118131640.GD29536@tuxteam.de> (raw)
In-Reply-To: <86vafz4922.fsf@zoho.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, Jan 18, 2018 at 01:59:17PM +0100, Emanuel Berg wrote:
> tomas wrote:
>
> >> True concurrency isn't possible even for
> >> multicore architectures IIUC.
> >
> > To a certain extent yes: the processors/cores
> > have to cooperate to access common resources
> > (e.g. memory), but as long as they are
> > operating e.g. from local cache they do run
> > in parallel.
>
> Yes, but I meant with respect to Emacs, can one
> have, for example
>
> (let*((value-one (compute it)) ; on CPU1
> (value-two (compute it)) )) ; on CPU2
>
> execute in parallel?
No, but see threads: they *can* execute on different CPUs
(whether Emacs will give you control over that is another
question; moreover it's a pretty new feature anyway).
> > central event loop
>
> Is this the KERNEL?
No, I was talkint about Emacs input queue.
> > to "keep running", you have to explicitly
[...]
> The problem with yielding is it won't work to
> interrupt something that has put Emacs into
> a hanged state...
That's true about most programs out there.
Cheers
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iEYEARECAAYFAlpgnjgACgkQBcgs9XrR2ka8RgCdFeu2XIJvDaOMwyIGsUWD2Tn+
H50An3aXGw2SOr1o1mk6/uUbsUwwdEu7
=I0xt
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2018-01-18 13:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 21:04 try-this-for ? Emanuel Berg
2018-01-17 23:50 ` John Mastro
2018-01-18 2:08 ` Bob Newell
[not found] ` <mailman.7535.1516241346.27995.help-gnu-emacs@gnu.org>
2018-01-18 2:52 ` Emanuel Berg
[not found] ` <mailman.7534.1516233062.27995.help-gnu-emacs@gnu.org>
2018-01-18 2:56 ` Emanuel Berg
2018-01-18 9:27 ` tomas
[not found] ` <mailman.7540.1516267658.27995.help-gnu-emacs@gnu.org>
2018-01-18 12:00 ` Emanuel Berg
2018-01-18 12:03 ` Emanuel Berg
2018-01-18 12:11 ` Emanuel Berg
2018-01-18 12:43 ` tomas
2018-01-18 15:14 ` Eli Zaretskii
2018-01-18 15:23 ` tomas
[not found] ` <mailman.7544.1516279427.27995.help-gnu-emacs@gnu.org>
2018-01-18 12:59 ` Emanuel Berg
2018-01-18 13:16 ` tomas [this message]
[not found] ` <mailman.7546.1516281409.27995.help-gnu-emacs@gnu.org>
2018-01-18 22:44 ` Emanuel Berg
2018-01-19 8:38 ` tomas
[not found] ` <mailman.7613.1516351115.27995.help-gnu-emacs@gnu.org>
2018-01-19 8:55 ` Emanuel Berg
2018-01-19 9:25 ` tomas
[not found] ` <mailman.7614.1516353949.27995.help-gnu-emacs@gnu.org>
2018-01-19 10:47 ` Emanuel Berg
2018-01-19 11:22 ` tomas
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=20180118131640.GD29536@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.