[argobots-discuss] ULT scheduler switching to Tasklet

Iwasaki, Shintaro siwasaki at anl.gov
Fri Dec 7 12:29:51 CST 2018

Hi, Polykarpos,

Thank you for your comment.
Currently, schedulers do not manage `ABT_self_xxx` (specifically `lp_ABTI_local->p_thread`); they are only for non-scheduler ULTs.
It includes not only the type you mentioned, but also the descriptor (i.e., `ABT_thread_self`) for example.

This behavior change is introduced by the following commit:
I note that they are not managed correctly even in the previous version.

This change was for performance; it can reduce the overheads of the `lp_ABTI_local` management.

Are you using this functionality?
If you think this functionality is useful, we will implement it. Even if not, we still need to clarify this specification.
We will appreciate it if you make an GitHub issue about it.

Thank you,
Shintaro Iwasaki

On Thu, Dec 6, 2018 at 4:16 PM POLYKARPOS THOMADAKIS via discuss <discuss at lists.argobots.org<mailto:discuss at lists.argobots.org>> wrote:

I have observed the following behavior when I have a custom scheduler that runs a Tasklet:

I retrieve the type of the scheduler before I run the Tasklet unit popped from the argobots pool and it is ULT which is what expected.
The scheduler runs the Tasklet, and after it's done I retrieve its type again and it has changed to Tasklet which is unexpected.

This seems a bit weird for me and I would like to know whether this shall be the functionality.
I also checked against an older version of argobots and I found out that this is not happening there.

Specifically, in version 1.0a1 the function ABTI_xstream_schedule_task<https://press3.mcs.anl.gov//wp-content/blogs.dir/231/files/argobots/doxygen/latest/d8/d4d/stream_8c.html#a0e222490fec0b8b0c5513a17ed5774b6> saves the state of current thread/task and recovers it after it's done executing the Tasklet. This is removed in current version.

Thank you for your time,

discuss mailing list
discuss at lists.argobots.org<mailto:discuss at lists.argobots.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.argobots.org/pipermail/discuss/attachments/20181207/c3398800/attachment.html>

More information about the discuss mailing list