search

AntelopeIO / leap

C++ implementation of the Antelope protocol
Other
116 stars 68 forks source link

Calculate total VM size properly for EOS-VM-OC in parallel read-only transaction execution #801

Closed linh2931 closed 1 year ago

linh2931 commented 1 year ago

Currently we use VmallocTotal in /proc/meminfo to determine how many threads allowed for EOS-VM-OC. On a 5-level paging system, VmallocTotal might report 64PB but mmap() will not give access to the extended range unless providing a hint which we currently don't do. Investigate a way to get a correct VM size we can access.

linh2931 commented 1 year ago

This is not needed any more. We don't rely on actual VM size to determine how many threads to support. See https://github.com/AntelopeIO/leap/issues/1256 and https://github.com/eosnetworkfoundation/product/pull/161.