Home
last modified time | relevance | path

Searched refs:zspage (Results 1 – 5 of 5) sorted by relevance

/linux-6.12.1/mm/
Dzsmalloc.c246 struct zspage { struct
269 static void SetZsHugePage(struct zspage *zspage) in SetZsHugePage() argument
271 zspage->huge = 1; in SetZsHugePage()
274 static bool ZsHugePage(struct zspage *zspage) in ZsHugePage() argument
276 return zspage->huge; in ZsHugePage()
279 static void migrate_lock_init(struct zspage *zspage);
280 static void migrate_read_lock(struct zspage *zspage);
281 static void migrate_read_unlock(struct zspage *zspage);
282 static void migrate_write_lock(struct zspage *zspage);
283 static void migrate_write_unlock(struct zspage *zspage);
[all …]
DKconfig222 int "Maximum number of physical pages per-zspage"
228 that a zmalloc page (zspage) can consist of. The optimal zspage
233 such as the number of pages per zspage and the number of objects
234 per zspage. This can also result in different configurations of
/linux-6.12.1/Documentation/translations/zh_CN/mm/
Dzsmalloc.rst20 页面的边界。代码将这些链接的页面作为一个实体,称为zspage
54 zspage存储对象大小
56 ZS_ALMOST_EMPTY zspage的数量(见下文)。
58 ZS_ALMOST_FULL zspage的数量(见下图)
66 组成一个zspage的0-order页面的数量
68 当n <= N / f时,我们将一个zspage分配给ZS_ALMOST_EMPTYfullness组,其中
71 * N = zspage可以存储的对象总数
74 同样地,我们将zspage分配给:
/linux-6.12.1/Documentation/mm/
Dzsmalloc.rst17 called zspage.
55 object size zspage stores
85 the number of 0-order pages to make a zspage
89 Each zspage maintains inuse counter which keeps track of the number of
90 objects stored in the zspage. The inuse counter determines the zspage's
92 the total number of objects the zspage can hold (objs_per_zspage). The
99 Each zspage can contain up to ZSMALLOC_CHAIN_SIZE physical (0-order) pages.
100 The optimal zspage chain size for each size class is calculated during the
104 characteristics in terms of the number of pages per zspage and the number
105 of objects that each zspage can store.
[all …]
Dslub.rst100 slab_debug=FZ;-,zs_handle,zspage