GeezerVison is showing github.com — gh-111916: Make hashlib related modules thread-safe without the GIL by tomasr8 · Pull Request #111981 · python/cpython
Conversation
tomasr8
commented
Nov 11, 2023
•
edited by gpshead
Loading
Uh oh!
There was an error while loading. Please reload this page.
Still a work in progress but I'd be happy for feedback ;)
I'm not entirely sure what to do about HASHLIB_GIL_MINSIZE. IIUC the original code avoids releasing the GIL and getting a separate lock when the update buffer is short enough. I'm guessing that in the nogil version, we'll have to lock the mutex regardless of the length (i.e. essentially getting rid of the macro)? Is that correct?
As a side note, I'm failing to build this PR with the GIL enabled. Running ./configure --with-pydebug and make -s -j2, I'm getting this error:
In file included from ./Modules/hashlib.h:7,
from ./Modules/md5module.c:29:
./Include/internal/pycore_lock.h: In function ‘PyMutex_LockFast’:
./Include/internal/pycore_lock.h:60:12: error: implicit declaration of function ‘_Py_atomic_compare_exchange_uint8’; did you mean ‘__atomic_compare_exchange_n’? [-Werror=implicit-function-declaration]
60 | return _Py_atomic_compare_exchange_uint8(lock_bits, &expected, _Py_LOCKED);
Even if I add #include "pyatomic.h" to pycore_lock.h I get the same error.. any idea why that is?
Fixes #111916
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
colesbury
left a comment
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The build errors you're seeing are due to md5module.c being compiled with the limited API, which means internal-only functions like PyMutex_Lock are not available. You should remove these lines from md5module.c:
#ifndef _MSC_VER
#include "pyconfig.h" // Py_NOGIL
#endif
#ifndef Py_NOGIL
// Need limited C API version 3.12 for Py_MOD_PER_INTERPRETER_GIL_SUPPORTED
#define Py_LIMITED_API 0x030c0000
#endif
And instead add:
#ifndef Py_BUILD_CORE_BUILTIN
# define Py_BUILD_CORE_MODULE 1
#endif
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
tomasr8 reacted with thumbs up emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
|
(I edited my review comment to note that you also should add Py_BUILD_CORE_MODULE to md5module.c)
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
It looks like some of the generated parts of Modules/_blake2/blake2s_impl.c are out of date. You'll need to re-run Argument Clinic. I think python3 Tools/clinic/clinic.py --make --exclude Lib/test/clinic.test.c --srcdir . should do the trick.
|
tomasr8 reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Thanks for the thorough review! I reran AC as you suggested, so hopefully it should be good this time
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, @tomasr8! This LGTM.
@gpshead - would you be able to review this PR? (I saw your name on the git log for these files.)
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
gpshead reacted with thumbs up emoji
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one minor style nit, overall looks great. thanks!
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
tomasr8 reacted with hooray emoji
the original code avoids releasing the GIL and getting a separate lock when the update buffer is short enough. I'm guessing that in the nogil version, we'll have to lock the mutex regardless of the length
Yep, the old HASHLIB_GIL_MINSIZE logic doesn't make sense in a free threaded build - always locking as this PR does works there. This PR could probably elide the concept from the code entirely during a free-threaded build, but that'd just makes the maintenance harder with additional ifdefs. For little value. It'll be an always-taken branch because use_mutex = true in free-threaded builds so the size will never get checked. Good enough - it won't have a measurable performance impact.
|
tomasr8 reacted with thumbs up emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
aisk
pushed a commit
to aisk/cpython
that referenced
this pull request
Feb 11, 2024
Reviewers
gpshead
gpshead approved these changes
tiran
Awaiting requested review from tiran
Uh oh!
There was an error while loading. Please reload this page.
Milestone
No milestone
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
|