root
/
openssl
mirror of https://github.com/openssl/openssl.git
1
0
Fork 0
Code Issues Actions 7 Packages Projects Releases Wiki Activity

QUIC I/O Architecture Design: Add block diagram, tweak wording 

Reviewed-by: Tomas Mraz <tomas@openssl.org>
Reviewed-by: Paul Dale <pauli@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/19770)
This commit is contained in:
Hugo Landau 2022-11-28 13:18:53 +00:00
parent aed7082419
commit dda864793e
2 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
doc/designs/quic-design/images/quic-io-arch-1.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 11 KiB

10
doc/designs/quic-design/quic-io-arch.md
View File

@ -104,10 +104,10 @@ parallel threads. Under this model, there would be three threads:
This has a large number of disadvantages: This has a large number of disadvantages:
- There is a hard requirement for threading functionality in order to be - There is a hard requirement for threading functionality in order to be
able to support blocking semantics at the application level. Use of blocking able to support blocking semantics at the application level. Applications
semantics at the application level will have a hard requirement on use of the which require blocking semantics would only be able to function in thread
thread assisted mode. In environments where threading support is not available assisted mode. In environments where threading support is not available or
or desired, our APIs will only be usable in a non-blocking fashion. desired, our APIs would only be usable in a non-blocking fashion.
- Several threads are spawned which the application is not in control of. - Several threads are spawned which the application is not in control of.
This undermines our general approach of providing the application with control This undermines our general approach of providing the application with control
@ -282,6 +282,8 @@ non-blocking I/O internally. Applications can use blocking or non-blocking I/O
at the libssl API level. Network-level BIOs must operate in a non-blocking mode at the libssl API level. Network-level BIOs must operate in a non-blocking mode
or be configurable by QUIC to this end. or be configurable by QUIC to this end.
![Block Diagram](images/quic-io-arch-1.png "Block Diagram")
### Support of arbitrary BIOs ### Support of arbitrary BIOs
We need to support not just socket FDs but arbitrary BIOs as the basis for the We need to support not just socket FDs but arbitrary BIOs as the basis for the