diff options
| author | Yann Ylavic <ylavic@apache.org> | 2017-04-07 00:01:16 +0000 |
|---|---|---|
| committer | Yann Ylavic <ylavic@apache.org> | 2017-04-07 00:01:16 +0000 |
| commit | f7b5a5f20e3edfb8ef2f4077147acb0bf17b3fab (patch) | |
| tree | 5c5c8a818d677acc7cf00a9b3cd5bfbf9a669977 /test/testlockperf.c | |
| parent | 0ea4c151aa5f650867a0afa3e92f90fc1bdbf114 (diff) | |
| download | apr-f7b5a5f20e3edfb8ef2f4077147acb0bf17b3fab.tar.gz | |
locks: follow up to r1667900.
Axe the 'absolute' argument of apr_{thread,proc,global}_mutex_timedlock()
which was confusing, hence 'timeout' is always relative now.
It still makes sense (to me) to handle a negative timeout as INFINITE, a nul
one as IMMEDIATE, and a positive one as an upper bound timeout (like most if
not all of the underlying system calls...).
git-svn-id: https://svn.apache.org/repos/asf/apr/apr/trunk@1790488 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'test/testlockperf.c')
| -rw-r--r-- | test/testlockperf.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/test/testlockperf.c b/test/testlockperf.c index 10442710d..c91f1a87b 100644 --- a/test/testlockperf.c +++ b/test/testlockperf.c @@ -61,7 +61,7 @@ void * APR_THREAD_FUNC thread_mutex_func(apr_thread_t *thd, void *data) for (i = 0; i < max_counter; i++) { if (data) { - apr_thread_mutex_timedlock(thread_lock, *(apr_time_t *)data, 0); + apr_thread_mutex_timedlock(thread_lock, *(apr_time_t *)data); } else { apr_thread_mutex_lock(thread_lock); |