d/freebsd-dev
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

PG_BUSY -> VPO_BUSY, PG_WANTED -> VPO_WANTED in manual pages and comments

Browse Source 
Reviewed by:	alc
MFC after:	4 days
This commit is contained in:
Andriy Gapon 2010-10-20 05:17:23 +00:00
parent 7e54c6db1f
commit 55144670c2
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=214095
4 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
share/man/man9/vm_page_io.9
View File

@ -52,9 +52,9 @@ function lowers the busy count on the page by one, if the resulting busy
count is zero, a
.Xr wakeup 9
will be issued if the page has been marked
.Dv PG_WANTED .
.Dv VPO_WANTED .
A page is typically marked
.Dv PG_WANTED
.Dv VPO_WANTED
by a thread to register its interest in
the page to either complete I/O or becoming available for general use.
.Sh AUTHORS

2
share/man/man9/vm_page_sleep_busy.9
View File

@ -42,7 +42,7 @@
The
.Fn vm_page_sleep_busy
function waits until the
.Dv PG_BUSY
.Dv VPO_BUSY
flag is cleared.
If
.Fa also_m_busy

8
share/man/man9/vm_page_wakeup.9
View File

@ -50,20 +50,20 @@ of a page.
.Pp
.Fn vm_page_busy
sets the
.Dv PG_BUSY
.Dv VPO_BUSY
flag in the page.
.Pp
.Fn vm_page_flash
checks to see if there is anybody waiting on the page
.Dv ( PG_WANTED
.Dv ( VPO_WANTED
will be set), and if so, clears the
.Dv PG_WANTED
.Dv VPO_WANTED
flag and notifies whoever is waiting via
.Fn wakeup .
.Pp
.Fn vm_page_wakeup
clears the
.Dv PG_BUSY
.Dv VPO_BUSY
flag on the page, and calls
.Fn vm_page_flash
in case somebody has been waiting for it.

4
sys/vm/swap_pager.c
View File

@ -1460,8 +1460,8 @@ swap_pager_putpages(vm_object_t object, vm_page_t *m, int count,
* Completion routine for asynchronous reads and writes from/to swap.
* Also called manually by synchronous code to finish up a bp.
*
* For READ operations, the pages are PG_BUSY'd. For WRITE operations,
* the pages are vm_page_t->busy'd. For READ operations, we PG_BUSY
* For READ operations, the pages are VPO_BUSY'd. For WRITE operations,
* the pages are vm_page_t->busy'd. For READ operations, we VPO_BUSY
* unbusy all pages except the 'main' request page. For WRITE
* operations, we vm_page_t->busy'd unbusy all pages ( we can do this
* because we marked them all VM_PAGER_PEND on return from putpages ).