public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Li, Yi" <yi1.li@intel.com>
To: devel@edk2.groups.io
Cc: Yi Li <yi1.li@intel.com>
Subject: [edk2-staging/OpenSSL11_EOL][PATCH 3/4] Readme: 0330 update
Date: Tue,  4 Apr 2023 17:54:32 +0800	[thread overview]
Message-ID: <f833b5f1160cb3aa6269f00cad4c00220b508e82.1680601312.git.yi1.li@intel.com> (raw)
In-Reply-To: <cover.1680601312.git.yi1.li@intel.com>

Signed-off-by: Yi Li <yi1.li@intel.com>
---
 CryptoPkg/Readme-OpenSSL3.0.md | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/CryptoPkg/Readme-OpenSSL3.0.md b/CryptoPkg/Readme-OpenSSL3.0.md
index fc5d24d074..1c77628b75 100644
--- a/CryptoPkg/Readme-OpenSSL3.0.md
+++ b/CryptoPkg/Readme-OpenSSL3.0.md
@@ -20,17 +20,17 @@ Will update latest result here (Build based on Intel platform).
 Binaries mode (use crypto drivers)  
 |     Driver      |   1.1.1    |    3.0     |   percent  |  
 |-----------------|------------|------------|------------|  
-|CryptoPei        |   386      |    398     |    3.1%    |  
+|CryptoPei        |   386      |    400     |    3.6%    |  
 |CryptoPeiPreMem  |   31       |    31      |    0%      |  
-|CryptoDxeFull    |   1014     |    997     |    -1.6%   |  
-|CryptoDxe        |   804      |    871     |    8.3%    |  
-|CryptoSmm        |   558      |    581     |    4.1%    |  
+|CryptoDxeFull    |   1014     |    935     |    -7.7%   |  
+|CryptoDxe        |   804      |    813     |    1.2%    |  
+|CryptoSmm        |   558      |    587     |    5.2%    |  
   
 | LZMA Compressed |   1.1.1    |    3.0     |   percent  |  
 |-----------------|------------|------------|------------|  
-|CryptoDxe        |   311      |    346     |    11.2%   |  
+|CryptoDxe        |   311      |    321     |    3.3%    |  
 |CryptoSmm        |   211      |    233     |    10.4%   |  
-|FV (Dxe+Smm)     |   357      |    406     |    13.7%   |  
+|FV (Dxe+Smm)     |   357      |    381     |    6.8%    |  
 
 Library mode (use crypto library)  
 |     Driver         |   1.1.1    |    3.0     |    delta   |  
@@ -61,6 +61,7 @@ SM2,
 SM3 - 12KB,  
 MD5 - 8KB,  
 PEM - 19KB,  
+TlsServer - 51KB (Only for DXE),
 ...  
 #### Risk:
 1. SM3  
@@ -154,5 +155,8 @@ https://github.com/liyi77/openssl/commit/faa5d6781c3af601bcbc11ff199e2955d7ff430
 https://github.com/liyi77/openssl/commit/8488c75701cdd5e626785e6d9d002f6fb30ae0ff  
 (commit: x509: remove unused extentions 19KB)  
 https://github.com/liyi77/openssl/commit/c27b3428708eb240b626946ce10d4219806d8adf  
+(commit: ssl: block out dtls code when OPENSSL_NO_DTLS defined 7KB)  
+https://github.com/liyi77/openssl/commit/a92f19cb85232a153f20303d7c9035b2b614fdb3  
+
 ## Timeline
 Target for 2023 Q1
\ No newline at end of file
-- 
2.31.1.windows.1


  parent reply	other threads:[~2023-04-04  9:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-04  9:54 [edk2-staging/OpenSSL11_EOL][PATCH 0/4] Openssl 3.0 POC update Apr 4 Li, Yi
2023-04-04  9:54 ` [edk2-staging/OpenSSL11_EOL][PATCH 1/4] CryptoPkg: disabled ssl server Li, Yi
2023-04-04  9:54 ` [edk2-staging/OpenSSL11_EOL][PATCH 2/4] CryptoPkg: sync latest change in uefiprov to minprov Li, Yi
2023-04-04  9:54 ` Li, Yi [this message]
2023-04-04  9:54 ` [edk2-staging/OpenSSL11_EOL][PATCH 4/4] Readme: update POC result and next step Li, Yi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f833b5f1160cb3aa6269f00cad4c00220b508e82.1680601312.git.yi1.li@intel.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox