🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: pl.comp.lang.c
Article #309594

Re: future i threads pools

#309594
From: M.M.
Date: Fri, 12 Jan 2018 20:47
25 lines
2485 bytes
On Friday, January 12, 2018 at 5:35:29 PM UTC+1, bartekltg wrote:
> On Friday, January 12, 2018 at 5:34:35 PM UTC+1, bartekltg wrote:
> > On Friday, January 12, 2018 at 4:51:12 PM UTC+1, Borneq wrote:
> > > Jest co prawda w Google:
> > > http://en.cppreference.com/w/cpp/thread/future
> > > http://www.cplusplus.com/reference/future/future/
> > > 
> > > Ale są tam raczej szczegóły które można czytać gdy się mniej więcej wie 
> > > co to jest. A jakby można to wytłumaczyć? Jaka różnica future i threads 
> > > pools w porównaniu z wątkami?
> > 
> > -Gdzie tam widzisz poole?
> > -Wytłumaczyć co? Musizz dać nam konkretny problem;>
> > -Wątki sa 'niższego poziomu'. async/future to klocki, z których wygodnie
> > możesz _pewne_ rzeczy budować. 
> 
> Samy tytuł
> https://www.youtube.com/watch?v=4OCUEgSNIAY
> ;-)

Skoczyłem tylko do rezultatów, nie na razie godziny czasu aby obejrzeć
całość. Wygląda na to, że HPX Blocked wygrywa. Co takiego złego jest w
OpenMP?

Pozdrawiam
Technical Details
Message-ID: <ec2a42d5-baee-4c63-977e-4ae4cbc190e8@googlegroups.com>
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!peer01.am4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!z1no872652qta.0!news-out.google.com!e39ni207qtk.1!nntp.google.com!z1no872650qta.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
References: <p3alhe$9nn$1@node1.news.atman.pl> <6d7bbe96-f0ff-4a58-9cd0-302fdba2b359@googlegroups.com> <5f9795b0-c666-4ce6-981a-9d80f2c2c11d@googlegroups.com>

Show Full Headers
Complete Article Headers
X-Received: by 10.55.25.230 with SMTP id 99mr12399072qkz.41.1515790039455;        Fri, 12 Jan 2018 12:47:19 -0800 (PST)
X-Received: by 10.31.174.73 with SMTP id x70mr2918077vke.8.1515790039252; Fri, 12 Jan 2018 12:47:19 -0800 (PST)
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.icm.edu.pl!news.nask.pl!news.nask.org.pl!news.unit0.net!peer01.am4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!z1no872652qta.0!news-out.google.com!e39ni207qtk.1!nntp.google.com!z1no872650qta.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: pl.comp.lang.c
Date: Fri, 12 Jan 2018 12:47:19 -0800 (PST)
In-Reply-To: <5f9795b0-c666-4ce6-981a-9d80f2c2c11d@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=159.205.159.52; posting-account=xjvq9QoAAAATMPC2X3btlHd_LkaJo_rj
NNTP-Posting-Host: 159.205.159.52
References: <p3alhe$9nn$1@node1.news.atman.pl> <6d7bbe96-f0ff-4a58-9cd0-302fdba2b359@googlegroups.com> <5f9795b0-c666-4ce6-981a-9d80f2c2c11d@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ec2a42d5-baee-4c63-977e-4ae4cbc190e8@googlegroups.com>
Subject: Re: future i threads pools
From: "M.M." <mmarszik@gmail.com>
Injection-Date: Fri, 12 Jan 2018 20:47:19 +0000
X-Received-Body-CRC: 332425285
X-Received-Bytes: 2546
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit