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 4/4] Readme: update POC result and next step
Date: Tue,  4 Apr 2023 17:54:33 +0800	[thread overview]
Message-ID: <6c3b90518493fe6591cf100cda66e4e16dd09b0e.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, 14 insertions(+), 2 deletions(-)

diff --git a/CryptoPkg/Readme-OpenSSL3.0.md b/CryptoPkg/Readme-OpenSSL3.0.md
index 1c77628b75..5b660959e7 100644
--- a/CryptoPkg/Readme-OpenSSL3.0.md
+++ b/CryptoPkg/Readme-OpenSSL3.0.md
@@ -16,7 +16,18 @@ This branch is for investigating how to reduce the size increase.
 The branch owner: Li Yi <yi1.li@intel.com>  
 
 ## Latest update
-Will update latest result here (Build based on Intel platform).  
+The goal of POC has been reached, next step:
+1.  Optimize code quality  
+2.  Upstream OpenSsl code change  
+3.  Fully validation  
+  
+Risk:  
+1.  Upstream the openssl code is a long process. if all goes well, it can be completed before the next openssl stable release (July 2023).  
+	If missed, the next stable release will be in September 2023.  
+2.  If bugs are found during validation, some size optimization work will have to be discarded.   
+	This will result in that size increase greater than the current result.  
+
+## POC result
 Binaries mode (use crypto drivers)  
 |     Driver      |   1.1.1    |    3.0     |   percent  |  
 |-----------------|------------|------------|------------|  
@@ -35,7 +46,8 @@ Binaries mode (use crypto drivers)
 Library mode (use crypto library)  
 |     Driver         |   1.1.1    |    3.0     |    delta   |  
 |--------------------|------------|------------|------------|  
-|      FV            |   2377     |    2639    |     262    |  
+|      FV            |   2377     |    2636    |     262    |  
+|      FV (LZMA)     |   459      |    539     |     80     |  
 |SecurityStubDxe.efi |   562      |    605     |     43     |  
 
 ## Limitation
-- 
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 ` [edk2-staging/OpenSSL11_EOL][PATCH 3/4] Readme: 0330 update Li, Yi
2023-04-04  9:54 ` Li, Yi [this message]

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=6c3b90518493fe6591cf100cda66e4e16dd09b0e.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