> I thought we don't want to go lock-free, the queue operations > aren't easily > implementable lock-free, but instead with a lock for each of > the queues, Hi, By lock-free I meant to use locks only for the queues, But my terminology was indeed confusing sorry about that. > mean we don't in some cases wake anybody, so there will be > threads idling > instead of doing useful work, but at least one thread > probably should handle > it later. I was personally worried about this case Since this could result in huge inefficiencies, but maybe it'll be fine. I'll first try to implement it. Thanks Ray Kim
- Re: [GSoC'19, libgomp work-stealing] Task parallelism runt... 김규래
- Re: Re: [GSoC'19, libgomp work-stealing] Task paralle... Jakub Jelinek
- Re: Re: [GSoC'19, libgomp work-stealing] Task paralle... John Pinkerton
- Re: [GSoC'19, libgomp work-stealing] Task parallelism runt... 김규래
- Re: Re: [GSoC'19, libgomp work-stealing] Task paralle... Jakub Jelinek
- Re: Re: [GSoC'19, libgomp work-stealing] Task para... 김규래
- Re: Re: [GSoC'19, libgomp work-stealing] Task ... Jakub Jelinek
- Re: Re: [GSoC'19, libgomp work-stealing] T... 김규래
- Re: Re: [GSoC'19, libgomp work-steali... 김규래
- Re: Re: [GSoC'19, libgomp work-st... Jakub Jelinek
- Re: Re: [GSoC'19, libgomp work-st... 김규래
- Re: Re: [GSoC'19, libgomp work-st... 김규래