public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: 김규래 <msca8h@naver.com>
Cc: gcc@gcc.gnu.org
Subject: Re:  Re: [GSoC'19, libgomp work-stealing] Task parallelism runtime
Date: Sat, 13 Jul 2019 06:28:00 -0000	[thread overview]
Message-ID: <20190713062848.GE2125@tucnak> (raw)
In-Reply-To: <2ec486a9ba251a2ffc757ed3b06192@cweb004.nm.nfra.io>

On Tue, Jul 09, 2019 at 09:56:00PM +0900, 김규래 wrote:
> Hi, 
> This is an update about my status.
> I've been working on unifying the three queues into a single queue.
> I'm almost finished and passed all the tests except for the dependency handling part.

For dependencies, I can imagine taking a lock on the parent task rather than
a team lock when dealing with the dependency data structures, and outside of
the lock perhaps do a quick check if there are any dependencies using atomic
load.  I can't imagine how one could get away without that though, and while
that can scale well if you have many tasks that spawn many other tasks, it
will still act as a team lock if say all tasks are spawned from the same
parent task.

	Jakub

  reply	other threads:[~2019-07-13  6:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e2a9f7c55311795785d0f2c47f70acbd@cweb001.nm.nfra.io>
2019-06-24 19:55 ` 김규래
2019-06-24 20:13   ` Jakub Jelinek
2019-07-13  7:46   ` John Pinkerton
2019-07-09 12:56 ` 김규래
2019-07-13  6:28   ` Jakub Jelinek [this message]
2019-07-21  7:46     ` 김규래
2019-07-22 18:54       ` Jakub Jelinek
2019-07-22 19:00         ` 김규래
2019-08-03  9:12           ` 김규래
2019-08-05 10:32             ` Jakub Jelinek
2019-08-05 11:01               ` 김규래
     [not found]                 ` <20190819061020.GA27842@laptop.zalov.cz>
2019-08-25  7:49                   ` 김규래

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190713062848.GE2125@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=msca8h@naver.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).