Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modified to use senderCache when prefetching with Lock unlike #962 #964

Merged
merged 3 commits into from
May 18, 2021

Conversation

KimKyungup
Copy link
Contributor

@KimKyungup KimKyungup commented May 13, 2021

Proposed changes

Like #962, this PR can resolve the issue. But the added lock can protects a race condition of the uint64 variable.

Test Result

EN0 : v1.6.1
EN1 : v1.6.2.rc3
image

Types of changes

Please put an x in the boxes related to your change.

  • Bugfix
  • New feature or enhancement
  • Others

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

  • I have read the CONTRIBUTING GUIDELINES doc
  • I have signed the CLA
  • Lint and unit tests pass locally with my changes ($ make test)
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

Related issues

  • Please leave the issue numbers or links related to this PR here.

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

@KimKyungup KimKyungup force-pushed the prefetch_cpu_usage_issue_with_lock branch from 440bd53 to 56f1063 Compare May 13, 2021 07:34
ehnuje
ehnuje previously approved these changes May 14, 2021
@KimKyungup
Copy link
Contributor Author

PTAL. :)

@joowon-byun
Copy link
Contributor

Could you explain specifically how this modification solves the problem?
To me, it looks like currentBlockNumber is only used in AccountCreationGas and SigValidationGas, which only read currentBlockNumber.

@KimKyungup
Copy link
Contributor Author

Could you explain specifically how this modification solves the problem?
To me, it looks like currentBlockNumber is only used in AccountCreationGas and SigValidationGas, which only read currentBlockNumber.

I added this lock to prohibit a race condition between below logics.
tx.validatedIntrinsicGas = intrinsicGas + gasFrom
tx.validatedIntrinsicGas += gasFeePayer

But After your comment, I figure out that the blocknumber can make a race condition with different blocknumber.
We need to find a better way. @winnie-byun @ehnuje

@KimKyungup
Copy link
Contributor Author

PTAL. :)

@KimKyungup KimKyungup merged commit 110168b into klaytn:dev May 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants