linux-4.4.1/GFP_DMA32
をテンプレートにして作成
[
トップ
] [
新規
|
一覧
|
検索
|
最終更新
|
ヘルプ
|
ログイン
]
開始行:
*参照元 [#g488b31c]
#backlinks
*説明 [#ab3c0f0e]
-パス: [[linux-4.4.1/include/linux/gfp.h]]
-FIXME: これは何？
--説明
**参考 [#we9d2f6c]
*実装 [#p42e56b6]
/*
* Useful GFP flag combinations that are commonly used. ...
* that subsystems start with one of these combinations ...
* __GFP_FOO flags as necessary.
*
* GFP_ATOMIC users can not sleep and need the allocatio...
* watermark is applied to allow access to "atomic res...
*
* GFP_KERNEL is typical for kernel-internal allocations...
* ZONE_NORMAL or a lower zone for direct access but c...
*
* GFP_NOWAIT is for kernel allocations that should not ...
* reclaim, start physical IO or use any filesystem ca...
*
* GFP_NOIO will use direct reclaim to discard clean pag...
* that do not require the starting of any physical IO.
*
* GFP_NOFS will use direct reclaim but will not use any...
*
* GFP_USER is for userspace allocations that also need ...
* accessibly by the kernel or hardware. It is typical...
* for buffers that are mapped to userspace (e.g. grap...
* still must DMA to. cpuset limits are enforced for t...
*
* GFP_DMA exists for historical reasons and should be a...
* The flags indicates that the caller requires that t...
* used (ZONE_DMA or 16M on x86-64). Ideally, this wou...
* it would require careful auditing as some users rea...
* others use the flag to avoid lowmem reserves in ZON...
* lowest zone as a type of emergency reserve.
*
* GFP_DMA32 is similar to GFP_DMA except that the calle...
* address.
*
* GFP_HIGHUSER is for userspace allocations that may be...
* do not need to be directly accessible by the kernel...
* move once in use. An example may be a hardware allo...
* data directly into userspace but has no addressing ...
*
* GFP_HIGHUSER_MOVABLE is for userspace allocations tha...
* need direct access to but can use kmap() when acces...
* are expected to be movable via page reclaim or page...
* pages on the LRU would also be allocated with GFP_H...
*
* GFP_TRANSHUGE is used for THP allocations. They are c...
* that will fail quickly if memory is not available a...
* kswapd on failure.
*/
#define GFP_ATOMIC (__GFP_HIGH|__GFP_ATOMIC|__GFP_KSWAPD...
#define GFP_KERNEL (__GFP_RECLAIM | __GFP_IO | __GFP_FS)
#define GFP_NOWAIT (__GFP_KSWAPD_RECLAIM)
#define GFP_NOIO (__GFP_RECLAIM)
#define GFP_NOFS (__GFP_RECLAIM | __GFP_IO)
#define GFP_TEMPORARY (__GFP_RECLAIM | __GFP_IO | __GFP_...
__GFP_RECLAIMABLE)
#define GFP_USER (__GFP_RECLAIM | __GFP_IO | __GFP_FS | ...
#define GFP_DMA __GFP_DMA
#define GFP_DMA32 __GFP_DMA32
#define GFP_HIGHUSER (GFP_USER | __GFP_HIGHMEM)
#define GFP_HIGHUSER_MOVABLE (GFP_HIGHUSER | __GFP_MOVAB...
#define GFP_TRANSHUGE ((GFP_HIGHUSER_MOVABLE | __GFP_COM...
__GFP_NOMEMALLOC | __GFP_NORETRY | __GFP_NOWARN) & \
~__GFP_KSWAPD_RECLAIM)
-
--[[linux-4.4.1/__GFP_DMA32]]
*コメント [#wa00af03]
終了行:
*参照元 [#g488b31c]
#backlinks
*説明 [#ab3c0f0e]
-パス: [[linux-4.4.1/include/linux/gfp.h]]
-FIXME: これは何？
--説明
**参考 [#we9d2f6c]
*実装 [#p42e56b6]
/*
* Useful GFP flag combinations that are commonly used. ...
* that subsystems start with one of these combinations ...
* __GFP_FOO flags as necessary.
*
* GFP_ATOMIC users can not sleep and need the allocatio...
* watermark is applied to allow access to "atomic res...
*
* GFP_KERNEL is typical for kernel-internal allocations...
* ZONE_NORMAL or a lower zone for direct access but c...
*
* GFP_NOWAIT is for kernel allocations that should not ...
* reclaim, start physical IO or use any filesystem ca...
*
* GFP_NOIO will use direct reclaim to discard clean pag...
* that do not require the starting of any physical IO.
*
* GFP_NOFS will use direct reclaim but will not use any...
*
* GFP_USER is for userspace allocations that also need ...
* accessibly by the kernel or hardware. It is typical...
* for buffers that are mapped to userspace (e.g. grap...
* still must DMA to. cpuset limits are enforced for t...
*
* GFP_DMA exists for historical reasons and should be a...
* The flags indicates that the caller requires that t...
* used (ZONE_DMA or 16M on x86-64). Ideally, this wou...
* it would require careful auditing as some users rea...
* others use the flag to avoid lowmem reserves in ZON...
* lowest zone as a type of emergency reserve.
*
* GFP_DMA32 is similar to GFP_DMA except that the calle...
* address.
*
* GFP_HIGHUSER is for userspace allocations that may be...
* do not need to be directly accessible by the kernel...
* move once in use. An example may be a hardware allo...
* data directly into userspace but has no addressing ...
*
* GFP_HIGHUSER_MOVABLE is for userspace allocations tha...
* need direct access to but can use kmap() when acces...
* are expected to be movable via page reclaim or page...
* pages on the LRU would also be allocated with GFP_H...
*
* GFP_TRANSHUGE is used for THP allocations. They are c...
* that will fail quickly if memory is not available a...
* kswapd on failure.
*/
#define GFP_ATOMIC (__GFP_HIGH|__GFP_ATOMIC|__GFP_KSWAPD...
#define GFP_KERNEL (__GFP_RECLAIM | __GFP_IO | __GFP_FS)
#define GFP_NOWAIT (__GFP_KSWAPD_RECLAIM)
#define GFP_NOIO (__GFP_RECLAIM)
#define GFP_NOFS (__GFP_RECLAIM | __GFP_IO)
#define GFP_TEMPORARY (__GFP_RECLAIM | __GFP_IO | __GFP_...
__GFP_RECLAIMABLE)
#define GFP_USER (__GFP_RECLAIM | __GFP_IO | __GFP_FS | ...
#define GFP_DMA __GFP_DMA
#define GFP_DMA32 __GFP_DMA32
#define GFP_HIGHUSER (GFP_USER | __GFP_HIGHMEM)
#define GFP_HIGHUSER_MOVABLE (GFP_HIGHUSER | __GFP_MOVAB...
#define GFP_TRANSHUGE ((GFP_HIGHUSER_MOVABLE | __GFP_COM...
__GFP_NOMEMALLOC | __GFP_NORETRY | __GFP_NOWARN) & \
~__GFP_KSWAPD_RECLAIM)
-
--[[linux-4.4.1/__GFP_DMA32]]
*コメント [#wa00af03]
ページ名:
![[PukiWiki]](image/pukiwiki.png "[PukiWiki]")
