From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>, Pedro Alves <pedro@palves.net>,
Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH][gdbsupport] Use task size in parallel_for_each
Date: Fri, 22 Jul 2022 21:17:06 -0600 [thread overview]
Message-ID: <87v8rosekt.fsf@tromey.com> (raw)
In-Reply-To: <0f84af97-ddf4-a9f7-b374-eeee46f94303@simark.ca> (Simon Marchi's message of "Fri, 22 Jul 2022 15:38:25 -0400")
Simon> Just a nit, if we are talking about a centralized work pool that threads
Simon> pick from to get their next work item, that's not really work stealing.
Simon> Work stealing is when threads all have their own work queue, and threads
Simon> with empty queues go steal some work from other threads' queues.
Thanks, that's a clear explanation.
Simon> Given our work items are fairly large, I'm guessing that having one
Simon> centralized queue is fine. Well, benchmarks will tell if that is faster
Simon> than Tom de Vries' balancing approach.
Yeah. Also I didn't see a straightforward way to implement work
stealing.
Tom
next prev parent reply other threads:[~2022-07-23 3:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 19:42 Tom de Vries via Gdb-patches
2022-07-21 17:35 ` Pedro Alves
2022-07-21 20:23 ` Tom de Vries via Gdb-patches
2022-07-22 0:03 ` Pedro Alves
2022-07-22 11:07 ` Pedro Alves
2022-07-22 17:07 ` Tom de Vries via Gdb-patches
2022-07-22 19:08 ` Tom Tromey
2022-07-22 19:38 ` Simon Marchi via Gdb-patches
2022-07-23 3:17 ` Tom Tromey [this message]
2022-07-22 21:21 ` Tom Tromey
2022-07-23 6:51 ` Tom de Vries via Gdb-patches
2022-07-31 8:38 ` Tom de Vries via Gdb-patches
2022-07-23 5:55 ` Tom de Vries via Gdb-patches
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=87v8rosekt.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
--cc=simark@simark.ca \
/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