unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Davis Herring" <herring@lanl.gov>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>
Cc: Andreas Schwab <schwab@linux-m68k.org>, emacs-devel@gnu.org
Subject: Re: Async DNS lookups
Date: Thu, 4 Nov 2010 13:40:27 -0700 (PDT)	[thread overview]
Message-ID: <49950.130.55.118.19.1288903227.squirrel@webmail.lanl.gov> (raw)
In-Reply-To: <jwvwrotw5l4.fsf-monnier+emacs@gnu.org>

>    lock(pending_funcalls);
>    setcar(result, pending_funcalls);
>    pending_funcalls = result;
>    unlock(pending_funcalls);
[snip]
> I.e. you'll probably want to use some new variable, very similar to
> pending_funcalls, but for "pending_c_funcalls" so that the pending calls
> can first do some C preprocessing to turn the C result data into Lisp data
> and then call the Elisp callback.

And then you don't want to lock the pending_funcalls variable after all:
you want to have a lock on the pending_c_funcalls and do something like

/* DNS thread */
x->data=lookup(...); /* slow */
lock(pending_c_funcalls_mutex);
x->next=pending_c_funcalls;
pending_c_funcalls=x;
unlock(pending_c_funcalls_mutex);

/* main thread */
lock(pending_c_funcalls_mutex);
for(;pending_c_funcalls;pending_c_funcalls=pending_c_funcalls->next)
  pending_funcalls=Fcons(convert_async(pending_c_funcalls),
                         pending_funcalls);
unlock(pending_c_funcalls_mutex);
/* ...existing Ffuncall() code... */

Right?

Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.



  parent reply	other threads:[~2010-11-04 20:40 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-30 11:57 Async DNS lookups Lars Magne Ingebrigtsen
2010-10-30 13:11 ` Julien Danjou
2010-10-30 13:34 ` Ted Zlatanov
2010-10-30 15:40 ` Helmut Eller
2010-10-31  4:01 ` Stefan Monnier
2010-10-31 17:16   ` Lars Magne Ingebrigtsen
2010-11-01 16:09 ` Tom Tromey
2010-11-02 16:15   ` Ken Raeburn
2010-11-02 16:29     ` Lars Magne Ingebrigtsen
2010-11-02 17:28       ` Stefan Monnier
2010-11-02 18:13         ` Lars Magne Ingebrigtsen
2010-11-02 18:30           ` Tom Tromey
2010-11-02 18:28             ` Lars Magne Ingebrigtsen
2010-11-02 18:47               ` Tom Tromey
2010-11-02 21:28           ` Stefan Monnier
2010-11-03 19:46             ` Lars Magne Ingebrigtsen
2010-11-03 21:29               ` Davis Herring
2010-11-03 21:46                 ` Lars Magne Ingebrigtsen
2010-11-04  2:24                   ` Stefan Monnier
2010-11-04  8:27                     ` Andreas Schwab
2010-11-04 14:15                       ` Stefan Monnier
2010-11-04 16:09                         ` Ken Raeburn
2010-11-04 19:49                         ` Lars Magne Ingebrigtsen
2010-11-04 20:40                         ` Davis Herring [this message]
2010-11-04 21:32                           ` Stefan Monnier

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49950.130.55.118.19.1288903227.squirrel@webmail.lanl.gov \
    --to=herring@lanl.gov \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=schwab@linux-m68k.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).