Yes, I’d characterize it as necessary overhead. Note that in all comm layer implementations the polling thread is careful to yield when it has nothing to do, so as to use no more time than really required.
greg > On Aug 29, 2017, at 7:54 PM, Hui Zhang <[email protected]> wrote: > > Hello, Greg > > So basically it's communication cost (request and reply messages) right? > Thanks > > On Tue, Aug 29, 2017 at 5:41 PM, Greg Titus <[email protected]> wrote: > Hello Hui -- > > The polling thread on each node processes Active Messages which are inbound > to that node. Among other things, we use these to implement the executeOn > operations that underlie on-stmts. > > greg > > > > On Aug 29, 2017, at 3:18 PM, Hui Zhang <[email protected]> wrote: > > > > Hello, > > > > I'm wondering what a polling task does in multi-locale Chapel? I see a > > thread is created for comm_task_wrapper which ends up calling "polling" in > > Chapel communication layer, and it costs some time, what's the purpose of > > it? > > > > Thanks > > > > -- > > Best regards > > > > > > Hui Zhang > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! > > http://sdm.link/slashdot_______________________________________________ > > Chapel-developers mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/chapel-developers > > > > > -- > Best regards > > > Hui Zhang ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Chapel-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-developers
