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

Fix grammar.

Browse Source 
Submitted by:	bf
MFC after:	2 weeks
This commit is contained in:
Konstantin Belousov 2011-09-28 16:12:15 +00:00
parent 578113aaa3
commit 2042bb377a
Notes: svn2git 2020-12-20 02:59:44 +00:00 
svn path=/head/; revision=225843
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
sys/vm/vm_page.c
View File

@ -2363,7 +2363,7 @@ vm_page_clear_dirty_mask(vm_page_t m, int pagebits)
* For PAGE_SIZE == 32768 case, compiler already
* properly aligns the dirty field, so no forcible
* alignment is needed. Only require existence of
* atomic_clear_64 when page size if 32768.
* atomic_clear_64 when page size is 32768.
*/
addr = (uintptr_t)&m->dirty;
#if PAGE_SIZE == 32768
@ -2373,9 +2373,9 @@ vm_page_clear_dirty_mask(vm_page_t m, int pagebits)
atomic_clear_32((uint32_t *)addr, pagebits);
#else /* PAGE_SIZE <= 8192 */
/*
* Use a trick to perform an 32bit atomic on the
* contained aligned word, to not depend on existence
* of the atomic_clear_{8, 16}.
* Use a trick to perform a 32-bit atomic on the
* containing aligned word, to not depend on the existence
* of atomic_clear_{8, 16}.
*/
shift = addr & (sizeof(uint32_t) - 1);
#if BYTE_ORDER == BIG_ENDIAN

2
sys/vm/vm_page.h
View File

@ -105,7 +105,7 @@
* the field without holding that lock. If the underlying
* architecture does not support atomic read-modify-write
* operations on the field's type, then the machine-independent
* layer uses 32bit atomic on the aligned 32bit word that
* layer uses a 32-bit atomic on the aligned 32-bit word that
* contains the dirty field. In the machine-independent layer,
* the implementation of read-modify-write operations on the
* field is encapsulated in vm_page_clear_dirty_mask().