Re: [GSoC'19] First Evaluations: Implementing OpenMP Work Stealing Scheduling

2019-06-29 Thread 김규래
> > Implementation of competing systems: > > The intel OpenMP implementation [1] is simpler. > > It uses a single queue for each thread and a single subroutine for > > dequeuing and executing the tasks [2, 3]. > > The taskgroup tasks and childen tasks are only counted (not queued) [4, 5, > > 6].

Re: [GSoC'19] First Evaluations: Implementing OpenMP Work Stealing Scheduling

2019-06-27 Thread Jakub Jelinek
On Thu, Jun 27, 2019 at 05:20:56AM +0900, 김규래 wrote: > I'll share my status for GSoC first evaluation. > > Current status of libgomp task system: > I'll first summarize my understanding of libgomp. > Please correct me if I'm wrong. > Currently libgomp has 3 different queues: children_queue, taskl

[GSoC'19] First Evaluations: Implementing OpenMP Work Stealing Scheduling

2019-06-26 Thread 김규래
Hi everyone, I'll share my status for GSoC first evaluation. Current status of libgomp task system: I'll first summarize my understanding of libgomp. Please correct me if I'm wrong. Currently libgomp has 3 different queues: children_queue, taskloop_queue and team_queue. These three queues are pr