From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web08.30547.1652095688033588167 for ; Mon, 09 May 2022 04:28:08 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=bqItV+XB; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1652095687; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=epeA/H3vSXY6FhvApClbg4fYoD5Uuuq4FELh06Jp3yY=; b=bqItV+XBB/Wo3KkZ5y3E5hZR5gw5CKQaZGzcaGGyT50gjjXwaX/2oBMpp152s8RRzes5T2 vL87NXUJVdVdSAFjQxTda6ptOFfoKJr1wSbMhKGD7eFdhVJPaeTVTWmo5ZhjrVIlrzLru4 Irgwp+7kQCTGFxHiFw301uD6ylJXz0w= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-358-n-SF4xSuOn2Zs2haqno6Ww-1; Mon, 09 May 2022 07:28:06 -0400 X-MC-Unique: n-SF4xSuOn2Zs2haqno6Ww-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.rdu2.redhat.com [10.11.54.5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 990068015BA; Mon, 9 May 2022 11:28:05 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.13]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 283BA7B64; Mon, 9 May 2022 11:28:02 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 2F844180062C; Mon, 9 May 2022 13:27:44 +0200 (CEST) Date: Mon, 9 May 2022 13:27:44 +0200 From: "Gerd Hoffmann" To: "Yao, Jiewen" Cc: "devel@edk2.groups.io" , Pawel Polawski , "Li, Yi1" , Oliver Steffen , "Wang, Jian J" , Ard Biesheuvel , "Jiang, Guomin" , "Lu, Xiaoyu1" , "Justen, Jordan L" Subject: Re: [edk2-devel] [PATCH 0/5] CryptoPkg/openssl: enable EC unconditionally. Message-ID: <20220509112744.msdph5d35ph24l4p@sirius.home.kraxel.org> References: <20220502103436.3274412-1-kraxel@redhat.com> <20220505080638.rmrw3f773rkw3ljl@sirius.home.kraxel.org> <20220505091536.llguh4dzozqtiiob@sirius.home.kraxel.org> <20220509094511.px6cl7jtjejr4y4x@sirius.home.kraxel.org> MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 2.79 on 10.11.54.5 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, > Old == the launched platform, or the platform will be launched shortly > where the flash size and layout are locked. So everything you can buy today. > It is huge risk to change the layout suddenly. And it is not practical > to change the flash size. (E.g. How can you change your flash size on > your laptop? ) Sure. > However, we also have size concern on OPENSSL3.0, according to the data you provided. Yes. > 1) Please keep the good work to enable OPENSSL3.0 in your personal branch. > 2) If you have some way to control the size, then do it. If there is > no much size difference by default, then you can submit to EDKII > directly. I suspect I wouldn't get it down to 1.1.1 levels even if I find some ways to make it smaller than it is in my branch today. The code for the new "provider" concept simply needs space and I think it also makes LTO optimization less effective. Maybe creating our own crypto providers which include only the algorithms actually needed by edk2 gets the size down a bit. take care, Gerd