This web page takes a better look on the Raspberry Pi memory hierarchy. Every stage of the Memory Wave clarity support hierarchy has a capability and speed. Capacities are relatively simple to find by querying the working system or studying the ARM1176 technical reference manual. Pace, nonetheless, isn't as easy to discover and must normally be measured. I take advantage of a simple pointer chasing method to characterize the behavior of each level in the hierarchy. The technique also reveals the conduct of memory-related efficiency counter events at each stage. The Raspberry Pi implements five levels in its memory hierarchy. The levels are summarized within the table below. The highest degree consists of digital memory pages that are maintained in secondary storage. Raspbian Wheezy keeps its swap area within the file /var/swap on the SDHC card. That is enough house for 25,600 4KB pages. You're allowed as many pages as will fit into the preallocated swap house.

The Raspberry Pi has either 256MB (Mannequin A) or 512MB (Mannequin B) of primary memory. This is sufficient area for 65,536 pages or 131,072 bodily pages, if all of primary memory had been available for paging. It isn’t all accessible for user-house programs as a result of the Linux kernel wants area for its personal code and data. Linux also helps giant pages, but that’s a separate matter for now. The vmstat command displays details about digital memory utilization. Please discuss with the man page for usage. Vmstat is an effective software for troubleshooting paging-related performance points because it shows web page in and out statistics. The processor within the Raspberry Pi is the Broadcom BCM2835. The BCM2835 does have a unified stage 2 (L2) cache. Nevertheless, the L2 cache is devoted to the VideoCore GPU. Memory references from the CPU facet are routed across the L2 cache. The BCM2835 has two stage 1 (L1) caches: a 16KB instruction cache and a 16KB information cache.

Our analysis below concentrates on the data cache. The information cache is 4-approach set associative. Each manner in an associative set stores a 32-byte cache line. The cache can handle as much as 4 active references to the same set without battle. If all 4 ways in a set are valid and a fifth reference is made to the set, then a battle happens and one of the 4 methods is victimized to make room for the brand new reference. The info cache is just about listed and Memory Wave clarity support bodily tagged. Cache strains and tags are saved individually in DATARAM and TAGRAM, respectively. Virtual deal with bits 11:5 index the TAGRAM and DATARAM. Given a 16KB capability, 32 byte strains and 4 ways, Memory Wave there should be 128 units. Virtual deal with bits 4:Zero are the offset into the cache line. The data MicroTLB translates a digital deal with to a bodily deal with and sends the physical handle to the L1 data cache.

The L1 data cache compares the physical handle with the tag and determines hit/miss status and the right approach. The load-to-use latency is three (3) cycles for an L1 knowledge cache hit. The BCM2835 implements a two degree translation lookaside buffer (TLB) construction for virtual to bodily tackle translation. There are two MicroTLBs: a ten entry information MicroTLB and a ten entry instruction MicroTLB. The MicroTLBs are backed by the primary TLB (i.e., Memory Wave the second stage TLB). The MicroTLBs are totally associative. Each MicroTLB translates a virtual address to a bodily tackle in one cycle when the web page mapping data is resident within the MicroTLB (that's, a hit within the MicroTLB). The primary TLB is a unified TLB that handles misses from the instruction and knowledge MicroTLBs. A 64-entry, 2-approach associative structure. Principal TLB misses are dealt with by a hardware web page table walker. A page desk walk requires not less than one further memory access to search out the page mapping information in major memory.

• 글쓰기

• 수정
• 삭제
• 목록