zhoubin
zhoubin
### Ⅰ. Issue Description 使用tengine+xquic+tongsuo+QAT测试QUIC的性能，对比不用QAT硬件加速时性能无提升 ### Ⅱ. Describe what happened 使用tengine+xquic+tongsuo搭建HTTP3的server环境，同时使用QAT硬件对加解密算法进行加速，但是测试效果发现使用QAT硬件无法提升HTTPS的性能 ### Ⅲ. Describe what you expected to happen intel使用NGINX-QUIC(async-mode)+boringSSL+QAT，性能提升了4.6倍。 参考file:///home/zhoubin/Downloads/IETF%20QUIC%20Acceleration%20using%20Intel%C2%AE%20QuickAssist%20Technology%20-Intel%20QAT%20(1).pdf 期望使用tengine+xquic+tongsuo+QAT也能有4倍左右的性能提升 ### Ⅳ. How to reproduce it (as minimally...
## Question Tengine是否支持QUIC以及是否支持在QUIC中使用国密套件？
### What happened? xquic调用babaSSL实现的tls1.3，babaSSL支持async_job，也就是异步SSL，这样的话把加解密等耗时操作卸载到QAT后，job能立刻返回，cpu还能处理其他请求，可以大幅提升性能。但是实际测试下来xquic不支持babaSSL的异步job。比如xquic会调用SSL_do_handshake发起握手，在发起握手前可以设置ssl的mode是异步的，这样SSL_do_handshake的返回结果是SSL_ERROR_WANT_ASYNC，但是xquic直接当错误处理了，从代码角度未看到有对async_job的支持。 ### Steps To Reproduce 使用tengine+xquic+tongsuo搭建HTTP3的server环境，同时使用QAT硬件对加解密算法进行加速，但是测试效果发现使用QAT硬件无法提升HTTPS的性能。 大概分析了握手过程中的调用栈，原因应该是xquic不支持async_mode导致的。 Thread 1 "tengine" hit Breakpoint 1, qat_engine_ecdh_compute_key (out=out@entry=0x7fff4fcf0b18, outlen=outlen@entry=0x7fff4fcf0b20, pub_key=0x55a8bd93d870, ecdh=0x55a8bd92ff30) at qat_hw_ec.c:795 795 { (gdb) bt #0 qat_engine_ecdh_compute_key (out=out@entry=0x7fff4fcf0b18,...
### Before request a new feature - [X] I have searched the [issues](https://github.com/alibaba/xquic/issues) of this repository and believe that this is not a duplicate. ### Describe the feature you'd like...
### Before request a new feature - [X] I have searched the [issues](https://github.com/alibaba/xquic/issues) of this repository and believe that this is not a duplicate. ### Describe the feature you'd like...
https://github.com/alibaba/xquic/blob/f3cab8816d4a68227df298df0cf9da90b18aae52/src/tls/xqc_tls.c#L1066 从抓取的报文来看，h2load没有填写SNI字段，导致server端进入xqc_ssl_cert_cb处理时报hostname为空的错误，此处server端是否应该做正确处理，比如允许没有SNI字段呢
tongsuo是否支持QUIC？
s_time什么时候能支持NTLS，用来测试NTLS套件的握手性能
Currently, does this branch support quic?
Please tell me which ssl_ciphers will use the chained cipher AES-256-CBC-HMAC-SHA256 , thanks.