public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Li, Yi1" <yi1.li@intel.com>
Cc: "Hou, Wenxing" <wenxing.hou@intel.com>,
	Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel] [edk2-staging/OpenSSL11_EOL][PATCH 0/4] Openssl 3.0 POC update Mar 22
Date: Fri, 24 Mar 2023 17:07:46 +0000	[thread overview]
Message-ID: <MW4PR11MB5872955A8F6A7DF692F9BEEC8C849@MW4PR11MB5872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CO1PR11MB49297104E4CDF01E6DD6B65FD2879@CO1PR11MB4929.namprd11.prod.outlook.com>

I think we almost finished POC.

My feeling for the final openssl 3.0 size increasement would be 10% ~ 20%, based upon how many patch we can upstream to openssl community.




> -----Original Message-----
> From: Kinney, Michael D <michael.d.kinney@intel.com>
> Sent: Friday, March 24, 2023 12:00 AM
> To: devel@edk2.groups.io; Li, Yi1 <yi1.li@intel.com>; Yao, Jiewen
> <jiewen.yao@intel.com>
> Cc: Yao, Jiewen <jiewen.yao@intel.com>; Hou, Wenxing
> <wenxing.hou@intel.com>; Gerd Hoffmann <kraxel@redhat.com>; Kinney,
> Michael D <michael.d.kinney@intel.com>
> Subject: RE: [edk2-devel] [edk2-staging/OpenSSL11_EOL][PATCH 0/4]
> Openssl 3.0 POC update Mar 22
> 
> Hi Jiewen,
> 
> What is your assessment of the progress on Openssl 3.0 from a size
> perspective.
> 
> What is the goal and how close are we now?
> 
> Thanks,
> 
> Mike
> 
> > -----Original Message-----
> > From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Li, Yi
> > Sent: Wednesday, March 22, 2023 7:45 PM
> > To: devel@edk2.groups.io
> > Cc: Li, Yi1 <yi1.li@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>; Hou,
> Wenxing <wenxing.hou@intel.com>; Gerd Hoffmann
> > <kraxel@redhat.com>
> > Subject: [edk2-devel] [edk2-staging/OpenSSL11_EOL][PATCH 0/4] Openssl
> 3.0 POC update Mar 22
> >
> > Please check the patch series if interested.
> > PR: https://github.com/tianocore/edk2-staging/pull/363
> >
> > Latest size data:
> > Binaries:
> > 	CryptoDxeFull	1.70%	->	-1.6%	-17KB
> > 	CryptoDxe		10.1%	->	8.3%	68KB
> > 	CryptoSmm		8.20%	->	4.1%	23KB
> > After LZMA:
> > 	CryptoDxe		12.2%	->	11.20%	35KB
> > 	CryptoSmm		12.8%	->	10.40%	22KB
> > 	FV (Dxe+Smm)	15.4%	->	13.70%	49KB
> >
> > 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):
> >   bugfix: use null md5 onlyif no-md5 defined
> >   CryptoPkg: remove unnecessary sig, ec and rsa prov
> >   CryptoPkg: update openssl submodule
> >   Readme: 0322 update
> >
> >  CryptoPkg/Library/OpensslLib/HashNull.c       |  3 +
> >  .../Library/OpensslLib/OpensslStub/uefiprov.c | 23 -------
> >  CryptoPkg/Library/OpensslLib/openssl          |  2 +-
> >  CryptoPkg/Readme-OpenSSL3.0.md                | 65 ++++++++++++++++---
> >  4 files changed, 61 insertions(+), 32 deletions(-)
> >
> > --
> > 2.31.1.windows.1
> >
> >
> >
> > 
> >


      reply	other threads:[~2023-03-24 17:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  2:44 [edk2-staging/OpenSSL11_EOL][PATCH 0/4] Openssl 3.0 POC update Mar 22 Li, Yi
2023-03-23  2:44 ` [edk2-staging/OpenSSL11_EOL][PATCH 1/4] bugfix: use null md5 onlyif no-md5 defined Li, Yi
2023-03-23  2:44 ` [edk2-staging/OpenSSL11_EOL][PATCH 2/4] CryptoPkg: remove unnecessary sig, ec and rsa prov Li, Yi
2023-03-23  2:44 ` [edk2-staging/OpenSSL11_EOL][PATCH 3/4] CryptoPkg: update openssl submodule Li, Yi
2023-03-23  2:44 ` [edk2-staging/OpenSSL11_EOL][PATCH 4/4] Readme: 0322 update Li, Yi
2023-03-23  8:56   ` [edk2-devel] " Gerd Hoffmann
2023-03-24  1:46     ` Li, Yi
2023-03-24  6:11       ` Yao, Jiewen
2023-03-24  7:50         ` Li, Yi
2023-03-24  7:54           ` Yao, Jiewen
2023-03-23 16:00 ` [edk2-devel] [edk2-staging/OpenSSL11_EOL][PATCH 0/4] Openssl 3.0 POC update Mar 22 Michael D Kinney
2023-03-24 17:07   ` Yao, Jiewen [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=MW4PR11MB5872955A8F6A7DF692F9BEEC8C849@MW4PR11MB5872.namprd11.prod.outlook.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