Project

General

Profile

Actions

Task #5673

closed

Memory scalability for large memory ranges (address space for 48 and 64 bit addresses)

Added by Andrei Tatarnikov about 9 years ago. Updated almost 9 years ago.

Status:
Closed
Priority:
Urgent
Assignee:
Andrei Tatarnikov
Category:
-
Target version:
Start date:
03/03/2015
Due date:
% Done:

100%

Estimated time:
Detected in build:
svn
Published in build:
150619

Description

Verify and review (if needed) the scalability of memory in the simulator for large memory ranges (address space for 48 and 64 bit addresses).

Question:

o ISPRAS to review and confirm the sparseness of the implementation of memory
• Does memory use of generation scale with number of locations touched or the range of (min, max)

Answer

In the current implementation of the simulator, memory is divided into 4KB regions which are allocated only when touched (written to).

Check whether the current way to avoid excessive memory consumption is sufficient. This includes more intensive testing. If not, the algorithm must be reviewed.

Basic ideas on sparse distributed memory:

http://en.wikipedia.org/wiki/Sparse_distributed_memory

Actions #1

Updated by Alexander Kamkin about 9 years ago

  • Subject changed from [model] Memory scalability for large memory ranges (address space for 48 and 64 bit addresses) to Memory scalability for large memory ranges (address space for 48 and 64 bit addresses)
  • Category set to ISA Simulator
  • Target version set to 2.1
Actions #2

Updated by Alexander Kamkin about 9 years ago

  • Category changed from ISA Simulator to 90
Actions #3

Updated by Alexander Kamkin about 9 years ago

  • Target version changed from 2.1 to 2.2
Actions #4

Updated by Andrei Tatarnikov almost 9 years ago

  • Status changed from New to Resolved

Supported in microtesk-2.2.5-beta-150611.

Immediate values of arbitrary size will be supported in version 2.2.6 (r3871 - "Test templates: support for immediate values of arbitrary size (> 32 bit).")

Actions #5

Updated by Andrei Tatarnikov almost 9 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Published in build set to 150619
Actions

Also available in: Atom PDF