Received: by 10.204.144.202 with SMTP id a10mr1369392bkv.0.1318678044839; Sat, 15 Oct 2011 04:27:24 -0700 (PDT) X-BeenThere: erlang-programming@googlegroups.com Received: by 10.204.134.87 with SMTP id i23ls3624420bkt.2.gmail; Sat, 15 Oct 2011 04:27:24 -0700 (PDT) Received: by 10.204.132.194 with SMTP id c2mr1341100bkt.7.1318678044230; Sat, 15 Oct 2011 04:27:24 -0700 (PDT) Received: by 10.204.132.194 with SMTP id c2mr1341099bkt.7.1318678044217; Sat, 15 Oct 2011 04:27:24 -0700 (PDT) Return-Path: Received: from hades.cslab.ericsson.net (hades.cslab.ericsson.net. [192.121.151.104]) by gmr-mx.google.com with ESMTP id p10si1876447bkq.2.2011.10.15.04.27.24; Sat, 15 Oct 2011 04:27:24 -0700 (PDT) Received-SPF: pass (google.com: domain of erlang-questions-bounces+erlang-programming+garchive-81772=googlegroups....@erlang.org designates 192.121.151.104 as permitted sender) client-ip=192.121.151.104; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of erlang-questions-bounces+erlang-programming+garchive-81772=googlegroups....@erlang.org designates 192.121.151.104 as permitted sender) smtp.mail=erlang-questions-bounces+erlang-programming+garchive-81772=googlegroups....@erlang.org; dkim=neutral (body hash did not verify) header...@gmail.com Received: from hades.cslab.ericsson.net (hades [192.121.151.104]) by hades.cslab.ericsson.net (Postfix) with ESMTP id 6990E5C27A; Sat, 15 Oct 2011 13:27:15 +0200 (CEST) X-Original-To: erlang-questi...@erlang.org Delivered-To: erlang-questi...@erlang.org Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.216.181]) by hades.cslab.ericsson.net (Postfix) with ESMTP id E1D415C008 for ; Sat, 15 Oct 2011 13:27:12 +0200 (CEST) Received: by qyk27 with SMTP id 27so559611qyk.19 for ; Sat, 15 Oct 2011 04:27:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LOqpy8D7Mj6GkmMWwMIZ52n65xunqBgUdQTv4v2IH7A=; b=hL8jXjoBfjZUK0uMffP30qyFVjqvShRPYHdGS8ZbYzqEC6KR+pwFWNWhIlXBLyKty5 c1ygqMfoAINghfsILkNH/PVwc5Q3WQFs9fwGE2gq3kR/ZilSywWAjkXVA6TcE8f6jSku xglqEjbwqq7m3WCXn1hXYmUX9r3dc5tjS9sww= MIME-Version: 1.0 Received: by 10.229.36.14 with SMTP id r14mr2615040qcd.23.1318678030277; Sat, 15 Oct 2011 04:27:10 -0700 (PDT) Received: by 10.229.237.209 with HTTP; Sat, 15 Oct 2011 04:27:10 -0700 (PDT) In-Reply-To: References: Date: Sat, 15 Oct 2011 12:27:10 +0100 Message-ID: From: Tim Watson To: Rapsey Cc: erlang-questi...@erlang.org Subject: Re: [erlang-questions] New NIF behavior in R15??? X-BeenThere: erlang-questi...@erlang.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: General Erlang/OTP discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7203343621044416215==" Errors-To: erlang-questions-boun...@erlang.org Sender: erlang-questions-boun...@erlang.org --===============7203343621044416215== Content-Type: multipart/alternative; boundary=0016367b700a915e5d04af54a785 --0016367b700a915e5d04af54a785 Content-Type: text/plain; charset=ISO-8859-1 My mistake - I haven't used NIFs yet, as most of the native code I've had to integrate has required threading and I was under the impression that linked-in drivers are the way to go if you want to avoid blocking the emulator whilst potentially long running tasks execute. On 15 October 2011 11:44, Rapsey wrote: > NIFs already have threading support. > > > Sergej > > > On Sat, Oct 15, 2011 at 11:28 AM, Tim Watson wrote: > >> I was under the impression that a concept like "Native Processes" was >> going to be introduced as well, to make the writing of linked-in driver code >> a lot easier. Is that still on the roadmap as well, and if so why are NIFs >> getting threading support? >> >> On 15 October 2011 02:29, Matthew Evans wrote: >> >>> Hi >>> >>> Within the next month or two we will be starting a project interfacing >>> Erlang to a C driver. This requires the use of a thread pool to support >>> asynchronous behaviors. Ordinarily I would implement this with a linked in >>> port driver. However, Rickard Green at his 2011 SF Erlang conference talk >>> indicated that new support in the NIF framework might be forthcoming in R15 >>> to support linked in driver style threading behavior in NIFS. >>> >>> I would rather hold off implementing a linked in driver if the new NIF >>> features are around the corner. Can anyone give any hints if this will be >>> the case? >>> >>> Thanks >>> >>> Matt >>> >>> _______________________________________________ >>> erlang-questions mailing list >>> erlang-questi...@erlang.org >>> http://erlang.org/mailman/listinfo/erlang-questions >>> >>> >> >> _______________________________________________ >> erlang-questions mailing list >> erlang-questi...@erlang.org >> http://erlang.org/mailman/listinfo/erlang-questions >> >> > --0016367b700a915e5d04af54a785 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable My mistake - I haven't used NIFs yet, as most of the native code I'= ve had to integrate has required threading and I was under the impression t= hat linked-in drivers are the way to go if you want to avoid blocking the e= mulator whilst potentially long running tasks execute.

On 15 October 2011 11:44, Rapsey <rap...@gmail.com> wrote:
NIFs already have threading support.


Sergej


On Sat, Oct 15, 2011 at 11:= 28 AM, Tim Watson <watson.timo...@gmail.com> wrote:
I was under the impression that a concept li= ke "Native Processes" was going to be introduced as well, to make= the writing of linked-in driver code a lot easier. Is that still on the ro= admap as well, and if so why are NIFs getting threading support?=A0

On 15 October 2011 02:2= 9, Matthew Evans <mattevans...@hotmail.com> wrote:
Hi

Within the next month or two we will be sta= rting a project interfacing Erlang to a C driver. This requires the use of = a thread pool to support asynchronous behaviors. Ordinarily I would impleme= nt this with a linked in port driver. However, Rickard Green at his 2011 SF= Erlang conference talk indicated that new support in the NIF framework mig= ht be forthcoming in R15 to support linked in driver style threading behavi= or in NIFS.

I would rather hold off implementing a linked in driver if the new NIF = features are around the corner. Can anyone give any hints if this will be t= he case?

Thanks

Matt

_______________________________________________
erlang-questions mailing list
erlang-que= sti...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions



_______________________________________________
erlang-questions mailing list
erlang-que= sti...@erlang.org
http://erlang.org/mailman/listinfo/erlang-questions



--0016367b700a915e5d04af54a785-- --===============7203343621044416215== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ erlang-questions mailing list erlang-questi...@erlang.org http://erlang.org/mailman/listinfo/erlang-questions --===============7203343621044416215==--