Searched full:pages (Results 1 – 25 of 224) sorted by relevance
123456789
... Content_Types].xml _rels/.rels visio/pages/pages.xml visio/_rels/document. ...
43 /** Number of unmapped pages. */46 /** Number of mapped pages. */49 /** Maximum number of mapped pages since last counter reset. */59 * it will start with all pages mapped. In next phase of driver initialization60 * unused pages will be unmapped.63 * @param[in] bank_pages Number of pages in the memory bank70 * This function is used to update the number of mapped pages within the75 * @return The number of pages mapped within the memory bank82 * This function is used to update the number of unmapped pages within the87 * @return The number of unmapped pages within the memory bank[all …]
15 pages-count:16 description: Number of consecutive pages with size pages-size bytes20 pages-size:
26 sector-0a-pages:32 and has its size equal to eight pages (one block) and the second one34 This property allows specifying the size (in pages) of that first sector35 and defaults to the commonly used value of eight pages.
32 pages-count = <8>;33 pages-size = <DT_SIZE_K(16)>;36 pages-count = <1>;37 pages-size = <DT_SIZE_K(128)>;40 pages-count = <3>;41 pages-size = <DT_SIZE_K(256)>;
26 pages-count = <8>;27 pages-size = <DT_SIZE_K(16)>;30 pages-count = <1>;31 pages-size = <DT_SIZE_K(128)>;34 pages-count = <7>;35 pages-size = <DT_SIZE_K(256)>;
18 This implements a backing store using physical RAM pages that the45 int "Number of pages for RAM backing store"48 Number of pages of backing store memory to reserve in RAM. All test49 cases for demand paging assume that there are at least 16 pages of
23 * management is necessary. Clean copies of paged-in data pages may be kept30 * are freed as soon as pages are paged in, in32 * This implies that all data pages are treated as dirty as45 * eviction algorithm, to free backing store locations for loaded data pages
28 * Test 3 pages at a time, but another set of 3 pages43 /* First N_PAGES pages of page_buf */47 /* Map our physical pages to the new location */52 /* Mark the new pages */81 /* Remap to another region (this will unmap the first virtual pages) */99 /* Now copy the remapped pages to a third virtual region */104 /* N_PAGES after the first N_PAGES pages of page_buf */169 /* Uses pages #0, #2, #4 */ in ZTEST()173 /* Map our physical pages to the new location */ in ZTEST()178 /* Mark the new pages */ in ZTEST()[all …]
19 - pages-count20 - pages-size
20 # - check that Composition Data pages 0 (old comp data) and 128 (new comp data) are different21 # - check that Composition Data pages 1 (old comp data) and 129 (new comp data) are different23 # - verify Composition Data pages 0 (new comp data) and 128 (same as page 0)24 # - verify Composition Data pages 1 (new comp data) and 129 (same as page 1)
18 bool "Emulate byte-sized pages"23 Emulate a device with byte-sized pages by doing a
84 int "Pages under statistic"89 Only up to this number of beginning pages will be tracked94 This is why it's not possible to calculate the number of pages with
35 Erase is usually performed in pages, as we have chosen to name37 specifications, like pages, sectors or blocks, and may vary74 retrieving the layout of flash memory pages.143 bool "API for retrieving the layout of pages"146 Enables API for retrieving the layout of flash memory pages.
19 The entire contiguous block of RRAM gets logically divided into pages,68 the multiplication would allow erasing all nRF flash pages in
23 A periodic timer will clear the accessed state of all virtual pages.37 Usage is tracked based on MMU protection making pages unaccessible51 pages that are capable of being paged out. At eviction time, if a page
17 - "free memory pages: from (.*) to 0, (.*) page faults"19 - "free memory pages: from 0 to 0, (.*) page faults"
40 /* It set mapped state for all pages */ in ZTEST()48 /* Now unmap all pages */ in ZTEST()60 /* Verify mapped pages are counted correctly */ in ZTEST()78 /* Verify unmapped pages are counted correctly */ in ZTEST()82 "MM Page Unmapped Error: Pages mapped = %u, not 1\n", in ZTEST()90 /* Verify max mapped pages are counted correctly */ in ZTEST()
110 printk(" - Total pages evicted: %lu\n", in print_paging_stats()112 printk(" - Clean pages evicted: %lu\n", in print_paging_stats()114 printk(" - Dirty pages evicted: %lu\n", in print_paging_stats()165 "there should be dirty pages being evicted."); in touch_anon_pages()171 /* There should be some clean pages to be evicted now, in touch_anon_pages()186 "there should be clean pages being evicted."); in touch_anon_pages()195 "test thread should have dirty pages evicted."); in touch_anon_pages()197 "test thread should have clean pages evicted."); in touch_anon_pages()385 "test thread should have dirty pages evicted."); in ZTEST_USER()387 "test thread should have clean pages evicted."); in ZTEST_USER()[all …]
14 API for retrieving the layout of pages (see :kconfig:option:`CONFIG_FLASH_PAGE_LAYOUT`).18 API for retrieving the layout of pages).
12 The TLB stores virtual to physical translation for individual pages of14 4-way-set-associative bank of entries mapping 4k pages, and 3-616 for mapping pages larger than 4k, which Zephyr does not directly66 occupied by the running code. The 1024 pages in that range (not all69 virtual memory. Note especially that exactly one of those pages74 can fail: there are 1024 possible pages in a complete page table149 note below) is to have an 8-entry set ("way 6") of 512M pages able to193 are in different 512M way6 pages, disable the mapping for the199 where the way 5/6 pages are immutable, and specify a set of232 the statically allocated array of L1 page table pages.[all …]
15 * different pages.19 * never placed across two different pages.
20 The pages in this section are a high-level guide to using devicetree for Zephyr41 These pages contain reference material for Zephyr's devicetree APIs and
132 * mappings for zeroed and uninitialized pages respectively.171 * Pages mapped in this way have write-back cache settings.177 * Note that the allocation includes two guard pages immediately before179 * the requested size plus the size of these two guard pages.219 * Allocated pages will have write-back cache settings.225 * Note that the allocation includes two guard pages immediately before227 * the requested size plus the size of these two guard pages.248 * virtual address region. Any paged out data pages may be discarded.
62 will be represented by Composition Data Pages 128, 129, and 130. The Models Metadata of the new63 firmware image will be represented by Models Metadata Page 128. Composition Data Pages 0, 1 and 2,70 Metadata pages before booting into the firmware with the updated Composition Data and Models71 Metadata. The old Composition Data will then be loaded into Composition Data Pages 0, 1 and 2,72 while the Composition Data in the new firmware will be loaded into Composition Data Pages 128, 129
