[lldb-dev] Parallelizing loading of shared libraries
Zachary Turner via lldb-dev
lldb-dev at lists.llvm.org
Mon May 1 22:12:22 PDT 2017
I think that's all the more reason we *should* work on getting something
into LLVM first. Anything we already have in LLDB, or any modifications we
make will likely not be pushed up to LLVM, especially since LLVM already
has a ThreadPool, so any changes you make to LLDB's thread pool will likely
have to be re-written when trying to get it to LLVM. And since, as you
said, more projects depend on LLVM than LLDB, there's a good chance that
the baseline you'd be starting from when making improvements is more easily
adaptable to what you want to do. LLDB has a long history of being shy of
making changes in LLVM where appropriate, and myself and others have
started pushing back on that more and more, because it accumulates long
term technical debt.
In my experience, "let's just get it into LLDB first and then work on
getting it up to LLVM later" ends up being "well, it's in LLDB now, so
since my immediate problem is solved I may or may not have time to revisit
this in the future" (even if the original intent is sincere).
If there is some resistance getting changes into LLVM, feel free to add me
as a reviewer, and I can find the right people to move it along. I'd still
like to at least hear a strong argument for why the existing implementation
in LLVM is unacceptable for what we need. I'm ok with "non optimal".
Unless it's "unsuitable", we should start there and make incremental
On Mon, May 1, 2017 at 9:56 PM Scott Smith <scott.smith at purestorage.com>
> IMO we should start with proving a better version in the lldb codebase,
> and then work on pushing it upstream. I have found much more resistance
> getting changes in to llvm than lldb, and for good reason - more projects
> depend on llvm than lldb.
> On Mon, May 1, 2017 at 9:48 PM, Zachary Turner <zturner at google.com> wrote:
>> I would still very much prefer we see if there is a way we can adapt
>> LLVM's ThreadPool class to be suitable for our needs. Unless some
>> fundamental aspect of its design results in unacceptable performance for
>> our needs, I think we should just use it and not re-invent another one. If
>> there are improvements to be made, let's make them there instead of in LLDB
>> so that other LLVM users can benefit.
>> On Mon, May 1, 2017 at 2:58 PM Scott Smith via lldb-dev <
>> lldb-dev at lists.llvm.org> wrote:
>>> On Mon, May 1, 2017 at 2:42 PM, Pavel Labath <labath at google.com> wrote:
>>>> Besides, hardcoding the nesting logic into "add" is kinda wrong.
>>>> Adding a task is not the problematic operation, waiting for the result
>>>> of one is. Granted, generally these happen on the same thread, but
>>>> they don't have to be -- you can write a continuation-style
>>>> computation, where you do a bit of work, and then enqueue a task to do
>>>> the rest. This would create an infinite pool depth here.
>>> True, but that doesn't seem to be the style of code here. If it were
>>> you wouldn't need multiple pools, since you'd just wait for the callback
>>> that your work was done.
>>>> Btw, are we sure it's not possible to solve this with just one thread
>>>> pool. What would happen if we changed the implementation of "wait" so
>>>> that if the target task is not scheduled yet, we just go ahead an
>>>> compute it on our thread? I haven't thought through all the details,
>>>> but is sounds like this could actually give better performance in some
>>> My initial reaction was "that wouldn't work, what if you ran another
>>> posix dl load?" But then I suppose *it* would run more work, and
>>> eventually you'd run a leaf task and finish something.
>>> You'd have to make sure your work could be run regardless of what
>>> mutexes the caller already had (since you may be running work for another
>>> subsystem), but that's probably not too onerous, esp given how many
>>> recursive mutexes lldb uses..
>>> lldb-dev mailing list
>>> lldb-dev at lists.llvm.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-dev