summaryrefslogtreecommitdiffstats
path: root/crypto/async/build.info
diff options
context:
space:
mode:
authorMatt Caswell <matt@openssl.org>2016-01-25 15:28:57 +0000
committerMatt Caswell <matt@openssl.org>2016-02-29 12:58:44 +0000
commitff75a25749c7fceaff7503af6f09d4299a052996 (patch)
tree4f7d8161e709ea1b82e9ceef0d27f78393b18127 /crypto/async/build.info
parentb32166b4fabd2a3aeec382521b0173b24a5d7c02 (diff)
Refactor the async wait fd logic
Implementation experience has shown that the original plan for async wait fds was too simplistic. Originally the async logic created a pipe internally and user/engine code could then get access to it via API calls. It is more flexible if the engine is able to create its own fd and provide it to the async code. Another issue is that there can be a lot of churn in the fd value within the context of (say) a single SSL connection leading to continually adding and removing fds from (say) epoll. It is better if we can provide some stability of the fd value across a whole SSL connection. This is problematic because an engine has no concept of an SSL connection. This commit refactors things to introduce an ASYNC_WAIT_CTX which acts as a proxy for an SSL connection down at the engine layer. Reviewed-by: Richard Levitte <levitte@openssl.org>
Diffstat (limited to 'crypto/async/build.info')
-rw-r--r--crypto/async/build.info3
1 files changed, 2 insertions, 1 deletions
diff --git a/crypto/async/build.info b/crypto/async/build.info
index d975003888..278e3e9f89 100644
--- a/crypto/async/build.info
+++ b/crypto/async/build.info
@@ -1,3 +1,4 @@
LIBS=../../libcrypto
SOURCE[../../libcrypto]=\
- async.c async_err.c arch/async_posix.c arch/async_win.c arch/async_null.c
+ async.c async_wait.c async_err.c arch/async_posix.c arch/async_win.c \
+ arch/async_null.c