Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openanolis
cloud-kernel
提交
5b0830cb
cloud-kernel
项目概览
openanolis
/
cloud-kernel
12 个月 前同步成功
通知
152
Star
36
Fork
7
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
10
列表
看板
标记
里程碑
合并请求
2
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
cloud-kernel
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
10
Issue
10
列表
看板
标记
里程碑
合并请求
2
合并请求
2
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
5b0830cb
编写于
9月 23, 2009
作者:
J
Jens Axboe
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
writeback: get rid to incorrect references to pdflush in comments
Signed-off-by:
N
Jens Axboe
<
jens.axboe@oracle.com
>
上级
71fd05a8
变更
5
隐藏空白更改
内联
并排
Showing
5 changed file
with
17 addition
and
19 deletion
+17
-19
fs/buffer.c
fs/buffer.c
+5
-5
fs/fs-writeback.c
fs/fs-writeback.c
+1
-4
mm/page-writeback.c
mm/page-writeback.c
+4
-4
mm/shmem.c
mm/shmem.c
+3
-2
mm/vmscan.c
mm/vmscan.c
+4
-4
未找到文件。
fs/buffer.c
浏览文件 @
5b0830cb
...
...
@@ -274,7 +274,7 @@ void invalidate_bdev(struct block_device *bdev)
}
/*
* Kick
pdflush
then try to free up some ZONE_NORMAL memory.
* Kick
the writeback threads
then try to free up some ZONE_NORMAL memory.
*/
static
void
free_more_memory
(
void
)
{
...
...
@@ -1699,9 +1699,9 @@ static int __block_write_full_page(struct inode *inode, struct page *page,
/*
* If it's a fully non-blocking write attempt and we cannot
* lock the buffer then redirty the page. Note that this can
* potentially cause a busy-wait loop from
pdflush and kswapd
* a
ctivity, but those code paths have their own higher-level
* throttling.
* potentially cause a busy-wait loop from
writeback threads
* a
nd kswapd activity, but those code paths have their own
*
higher-level
throttling.
*/
if
(
wbc
->
sync_mode
!=
WB_SYNC_NONE
||
!
wbc
->
nonblocking
)
{
lock_buffer
(
bh
);
...
...
@@ -3191,7 +3191,7 @@ void block_sync_page(struct page *page)
* still running obsolete flush daemons, so we terminate them here.
*
* Use of bdflush() is deprecated and will be removed in a future kernel.
* The `
pdflush
' kernel threads fully replace bdflush daemons and this call.
* The `
flush-X
' kernel threads fully replace bdflush daemons and this call.
*/
SYSCALL_DEFINE2
(
bdflush
,
int
,
func
,
long
,
data
)
{
...
...
fs/fs-writeback.c
浏览文件 @
5b0830cb
...
...
@@ -320,7 +320,7 @@ static bool inode_dirtied_after(struct inode *inode, unsigned long t)
* For inodes being constantly redirtied, dirtied_when can get stuck.
* It _appears_ to be in the future, but is actually in distant past.
* This test is necessary to prevent such wrapped-around relative times
* from permanently stopping the whole
pdflush
writeback.
* from permanently stopping the whole
bdi
writeback.
*/
ret
=
ret
&&
time_before_eq
(
inode
->
dirtied_when
,
jiffies
);
#endif
...
...
@@ -1085,9 +1085,6 @@ EXPORT_SYMBOL(__mark_inode_dirty);
* If older_than_this is non-NULL, then only write out inodes which
* had their first dirtying at a time earlier than *older_than_this.
*
* If we're a pdlfush thread, then implement pdflush collision avoidance
* against the entire list.
*
* If `bdi' is non-zero then we're being asked to writeback a specific queue.
* This function assumes that the blockdev superblock's inodes are backed by
* a variety of queues, so all inodes are searched. For other superblocks,
...
...
mm/page-writeback.c
浏览文件 @
5b0830cb
...
...
@@ -58,7 +58,7 @@ static inline long sync_writeback_pages(unsigned long dirtied)
/* The following parameters are exported via /proc/sys/vm */
/*
* Start background writeback (via
pdflush
) at this percentage
* Start background writeback (via
writeback threads
) at this percentage
*/
int
dirty_background_ratio
=
10
;
...
...
@@ -477,8 +477,8 @@ get_dirty_limits(unsigned long *pbackground, unsigned long *pdirty,
* balance_dirty_pages() must be called by processes which are generating dirty
* data. It looks at the number of dirty pages in the machine and will force
* the caller to perform writeback if the system is over `vm_dirty_ratio'.
* If we're over `background_thresh' then
pdflush is woken to perform some
* writeout.
* If we're over `background_thresh' then
the writeback threads are woken to
*
perform some
writeout.
*/
static
void
balance_dirty_pages
(
struct
address_space
*
mapping
,
unsigned
long
write_chunk
)
...
...
@@ -582,7 +582,7 @@ static void balance_dirty_pages(struct address_space *mapping,
bdi
->
dirty_exceeded
=
0
;
if
(
writeback_in_progress
(
bdi
))
return
;
/* pdflush is already working this queue */
return
;
/*
* In laptop mode, we wait until hitting the higher threshold before
...
...
mm/shmem.c
浏览文件 @
5b0830cb
...
...
@@ -1046,8 +1046,9 @@ static int shmem_writepage(struct page *page, struct writeback_control *wbc)
* sync from ever calling shmem_writepage; but a stacking filesystem
* may use the ->writepage of its underlying filesystem, in which case
* tmpfs should write out to swap only in response to memory pressure,
* and not for pdflush or sync. However, in those cases, we do still
* want to check if there's a redundant swappage to be discarded.
* and not for the writeback threads or sync. However, in those cases,
* we do still want to check if there's a redundant swappage to be
* discarded.
*/
if
(
wbc
->
for_reclaim
)
swap
=
get_swap_page
();
...
...
mm/vmscan.c
浏览文件 @
5b0830cb
...
...
@@ -1709,10 +1709,10 @@ static void shrink_zones(int priority, struct zonelist *zonelist,
*
* If the caller is !__GFP_FS then the probability of a failure is reasonably
* high - the zone may be full of dirty or under-writeback pages, which this
* caller can't do much about. We kick
pdflush and take explicit naps in the
*
hope that some of these pages can be written. But if the allocating task
*
holds filesystem locks which prevent writeout this might not work, and the
* allocation attempt will fail.
* caller can't do much about. We kick
the writeback threads and take explicit
*
naps in the hope that some of these pages can be written. But if the
*
allocating task holds filesystem locks which prevent writeout this might not
*
work, and the
allocation attempt will fail.
*
* returns: 0, if no pages reclaimed
* else, the number of pages reclaimed
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录