public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: shenglei <shenglei.zhang@intel.com>
To: edk2-devel@lists.01.org
Cc: Bob Feng <bob.c.feng@intel.com>,
	Liming Gao <liming.gao@intel.com>,
	Yonghong Zhu <yonghong.zhu@intel.com>,
	Michael D Kinney <michael.d.kinney@intel.com>
Subject: [PATCH v2 0/3] Improve performance of boundary validation in MakeTable()
Date: Thu, 21 Mar 2019 14:31:46 +0800	[thread overview]
Message-ID: <20190321063149.13260-1-shenglei.zhang@intel.com> (raw)

The boundary validation checking in MakeTable() performs on
every loop iteration. This could be improved by checking
just once before the loop.
https://bugzilla.tianocore.org/show_bug.cgi?id=1329

v2:1.Change the the algorithm implementation of the judgement in all patches.
   2.Remove previous 3/4 in v1.

Cc: Bob Feng <bob.c.feng@intel.com>
Cc: Liming Gao <liming.gao@intel.com>
Cc: Yonghong Zhu <yonghong.zhu@intel.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Shenglei Zhang (3):
  BaseTools/TianoCompress: Improve performance of boundary validation
  BaseTools/C/Common: Improve performance of boundary validation
  MdePkg/BaseUefiDecompressLib: Improve performance of boundary
    validation

 BaseTools/Source/C/Common/Decompress.c                     | 7 ++++---
 BaseTools/Source/C/TianoCompress/TianoCompress.c           | 7 ++++---
 .../Library/BaseUefiDecompressLib/BaseUefiDecompressLib.c  | 7 ++++---
 3 files changed, 12 insertions(+), 9 deletions(-)

-- 
2.18.0.windows.1



             reply	other threads:[~2019-03-21  6:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21  6:31 shenglei [this message]
2019-03-21  6:31 ` [PATCH v2 1/3] BaseTools/TianoCompress: Improve performance of boundary validation shenglei
2019-03-21  6:31 ` [PATCH v2 2/3] BaseTools/C/Common: " shenglei
2019-03-21  6:31 ` [PATCH v2 3/3] MdePkg/BaseUefiDecompressLib: " shenglei
2019-03-22  6:34 ` [PATCH v2 0/3] Improve performance of boundary validation in MakeTable() Gao, Liming

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=20190321063149.13260-1-shenglei.zhang@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