Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update threadpool.rst #146

Closed
wants to merge 1 commit into from
Closed

Update threadpool.rst #146

wants to merge 1 commit into from

Conversation

almosnow
Copy link
Contributor

From here: #145

Just so that someone won't ask the same thing again.

@bnoordhuis
Copy link
Member

LGTM but can you amend the commit log per the guidelines in CONTRIBUTING.md?

@almosnow almosnow force-pushed the patch-1 branch 2 times, most recently from f2e235a to 8dad909 Compare January 20, 2015 01:02
@almosnow
Copy link
Contributor Author

Check it out 👌

@@ -12,7 +12,11 @@ Its default size is 4, but it can be changed at startup time by setting the
``UV_THREADPOOL_SIZE`` environment variable to any value (the absolute maximum
is 128).

The threadpool is global and shared across all event loops.
The threadpool is global and shared across all event loops. When a particular
function makes use of the threadpool (i.e. when using uv_queue_work) libuv
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use :c:func:uv_queue_work so Sphix creates a link automagically.

@saghul
Copy link
Member

saghul commented Jan 20, 2015

The "subsystem" for the commit log should be "doc".

@almosnow almosnow force-pushed the patch-1 branch 3 times, most recently from c2f33fa to bd85600 Compare January 20, 2015 12:45
@almosnow
Copy link
Contributor Author

@saghul There it is and thanks for the reference about the threadpool handle. If everything's fine and you're going to merge, could it please be @bnoordhuis the one that does the commit? It would be nice for me.

@@ -12,7 +12,11 @@ Its default size is 4, but it can be changed at startup time by setting the
``UV_THREADPOOL_SIZE`` environment variable to any value (the absolute maximum
is 128).

The threadpool is global and shared across all event loops.
The threadpool is global and shared across all event loops. When a particular
function makes use of the threadpool (i.e. when using :c:func:uv_queue_work)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The correct syntax is:

:c:func:`uv_queue_work`

Note the backticks.

@saghul
Copy link
Member

saghul commented Jan 20, 2015

If everything's fine and you're going to merge, could it please be @bnoordhuis the one that does the commit? It would be nice for me.

Sure, after that last nit Ben will do the honors :-)

@almosnow
Copy link
Contributor Author

Ready.

@saghul
Copy link
Member

saghul commented Jan 20, 2015

LGTM 👍

@bnoordhuis
Copy link
Member

@almosnow I don't want to be that guy but... can you sign the commit with your real name? Thanks!

Added an explanation about how does libuv implements the threadpool and
why. This is so users know what behavior they should expect when they
make use of threads.

Related issue: libuv/libuv#145
@almosnow
Copy link
Contributor Author

Ok

[Definitely learning a lot about git/github today]

bnoordhuis pushed a commit that referenced this pull request Jan 21, 2015
Add an explanation about how libuv implements the threadpool and why.
This is so users know what behavior they should expect when they make
use of threads.

Related issue: #145

PR-URL: #146
Reviewed-By: Ben Noordhuis <info@bnoordhuis.nl>
@bnoordhuis
Copy link
Member

Thanks Alex, landed in ea5f1f9!

@bnoordhuis bnoordhuis closed this Jan 21, 2015
gagern pushed a commit to gagern/libuv that referenced this pull request Apr 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants