• 목록
• 답변
• 글쓰기
• 게시판 리스트 옵션
  • 수정
  • 삭제

A web page, memory web page, or digital web page is a hard and fast-length contiguous block of virtual memory, described by a single entry in a web page table. It is the smallest unit of knowledge for Memory Wave clarity support administration in an operating system that makes use of digital memory. Similarly, a page frame is the smallest fixed-length contiguous block of bodily memory into which memory pages are mapped by the working system. A switch of pages between essential memory and an auxiliary store, reminiscent of a hard disk drive, is known as paging or Memory Wave swapping. Pc memory is divided into pages so that data can be found extra rapidly. The concept is named by analogy to the pages of a printed book. If a reader needed to search out, for instance, the 5,000th word in the book, they might depend from the first phrase. This would be time-consuming. It can be much quicker if the reader had an inventory of what number of words are on each web page.

From this listing they could decide which web page the 5,000th word seems on, and what number of words to count on that page. This listing of the words per web page of the guide is analogous to a page table of a pc file system. Page size is normally determined by the processor structure. Historically, pages in a system had uniform size, comparable to 4,096 bytes. However, processor designs typically permit two or more, typically simultaneous, page sizes as a consequence of its advantages. There are several points that may issue into selecting one of the best web page size. A system with a smaller page dimension makes use of more pages, requiring a web page desk that occupies extra space. 232 / 212). Nevertheless, if the page size is increased to 32 KiB (215 bytes), only 217 pages are required. A multi-degree paging algorithm can lower the memory price of allocating a large web page table for every process by further dividing the page desk up into smaller tables, successfully paging the page desk.

Since every entry to memory should be mapped from virtual to bodily address, studying the web page desk every time could be fairly expensive. Due to this fact, a really fast kind of cache, the translation lookaside buffer (TLB), is commonly used. The TLB is of restricted measurement, and when it can not fulfill a given request (a TLB miss) the web page tables should be searched manually (both in hardware or software, relying on the structure) for the proper mapping. Larger page sizes mean that a TLB cache of the same measurement can keep monitor of bigger quantities of memory, which avoids the pricey TLB misses. Rarely do processes require the use of a precise variety of pages. Because of this, the final web page will possible solely be partially full, wasting some quantity of memory. Larger web page sizes result in a large amount of wasted memory, as more potentially unused parts of memory are loaded into the main memory. Smaller web page sizes guarantee a better match to the precise amount of memory required in an allocation.

For example, assume the web page measurement is 1024 B. If a course of allocates 1025 B, Memory Wave two pages should be used, resulting in 1023 B of unused space (the place one page absolutely consumes 1024 B and the other only 1 B). When transferring from a rotational disk, a lot of the delay is caused by seek time, the time it takes to appropriately position the learn/write heads above the disk platters. Due to this, large sequential transfers are extra environment friendly than several smaller transfers. Transferring the same quantity of data from disk to memory typically requires much less time with bigger pages than with smaller pages. Most operating systems allow applications to find the web page dimension at runtime. This enables packages to use memory more efficiently by aligning allocations to this dimension and lowering overall inside fragmentation of pages. In many Unix techniques, the command-line utility getconf can be utilized. For example, getconf PAGESIZE will return the web page size in bytes.

Some instruction set architectures can help a number of page sizes, together with pages considerably larger than the usual web page dimension. The available page sizes depend upon the instruction set architecture, processor kind, and working (addressing) mode. The working system selects a number of sizes from the sizes supported by the architecture. Be aware that not all processors implement all outlined bigger page sizes. This support for bigger pages (referred to as "huge pages" in Linux, "superpages" in FreeBSD, and "giant pages" in Microsoft Home windows and IBM AIX terminology) allows for "the better of both worlds", reducing the strain on the TLB cache (sometimes growing pace by as much as 15%) for large allocations while nonetheless preserving memory usage at a reasonable level for small allocations. Xeon processors can use 1 GiB pages in lengthy mode. IA-sixty four helps as many as eight different web page sizes, from four KiB as much as 256 MiB, and another architectures have related options. Bigger pages, regardless of being obtainable within the processors utilized in most contemporary private computer systems, should not in common use besides in large-scale functions, the applications typically present in large servers and in computational clusters, and within the working system itself.