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>, Jiewen Yao <jiewen.yao@intel.com>,
	Wenxing Hou <wenxing.hou@intel.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: [edk2-staging/OpenSSL11_EOL][PATCH 0/4] Openssl 3.0 POC update Apr 4
Date: Tue,  4 Apr 2023 17:54:29 +0800	[thread overview]
Message-ID: <cover.1680601312.git.yi1.li@intel.com> (raw)

Updated POC result and next step.
Please check the patch series if interested.
PR: https://github.com/tianocore/edk2-staging/pull/366

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 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 current result.

## POC result
Binaries mode (use crypto drivers)  
|     Driver      |   1.1.1    |    3.0     |   percent  |  
|-----------------|------------|------------|------------|  
|CryptoPei        |   386      |    400     |    3.6%    |  
|CryptoPeiPreMem  |   31       |    31      |    0%      |  
|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      |    321     |    3.3%    |  
|CryptoSmm        |   211      |    233     |    10.4%   |  
|FV (Dxe+Smm)     |   357      |    381     |    6.8%    |  

Library mode (use crypto library)  
|     Driver         |   1.1.1    |    3.0     |    delta   |  
|--------------------|------------|------------|------------|  
|      FV            |   2377     |    2636    |     262    |  
|      FV (LZMA)     |   459      |    539     |     80     |  
|SecurityStubDxe.efi |   562      |    605     |     43     |  

Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Wenxing Hou <wenxing.hou@intel.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Signed-off-by: Yi Li <yi1.li@intel.com>

Yi Li (4):
  CryptoPkg: disabled ssl server
  CryptoPkg: sync latest change in uefiprov to minprov
  Readme: 0330 update
  Readme: update POC result and next step

 CryptoPkg/Library/OpensslLib/OpensslLib.inf   |   6 +-
 .../Library/OpensslLib/OpensslLibFull.inf     |   6 +-
 .../Library/OpensslLib/OpensslStub/minprov.c  |  30 +-
 CryptoPkg/Library/OpensslLib/SslExtServNull.c | 329 ++++++++++++++++++
 .../Library/OpensslLib/SslStatServNull.c      | 219 ++++++++++++
 CryptoPkg/Readme-OpenSSL3.0.md                |  32 +-
 6 files changed, 587 insertions(+), 35 deletions(-)
 create mode 100644 CryptoPkg/Library/OpensslLib/SslExtServNull.c
 create mode 100644 CryptoPkg/Library/OpensslLib/SslStatServNull.c

-- 
2.31.1.windows.1


             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 Li, Yi [this message]
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 ` [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=cover.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