summaryrefslogtreecommitdiffstats
path: root/sys/vm
diff options
context:
space:
mode:
authorrwatson <rwatson@FreeBSD.org>2008-10-22 16:50:12 +0000
committerrwatson <rwatson@FreeBSD.org>2008-10-22 16:50:12 +0000
commit3667673537759b789eadce36fa09143b45b442a1 (patch)
tree7bd7d596e922f444bb2a1367ce8909f226961fd3 /sys/vm
parentc16b8be4793f74b96b99f111cd2dafdd854c0e9e (diff)
downloadFreeBSD-src-3667673537759b789eadce36fa09143b45b442a1.zip
FreeBSD-src-3667673537759b789eadce36fa09143b45b442a1.tar.gz
Update mmap() comment: no more block devices, so no more block device
cache coherency questions. MFC after: 3 days
Diffstat (limited to 'sys/vm')
-rw-r--r--sys/vm/vm_mmap.c4
1 files changed, 0 insertions, 4 deletions
diff --git a/sys/vm/vm_mmap.c b/sys/vm/vm_mmap.c
index c3f08b0..3f1d43d 100644
--- a/sys/vm/vm_mmap.c
+++ b/sys/vm/vm_mmap.c
@@ -187,10 +187,6 @@ ogetpagesize(td, uap)
* memory-based, such as a video framebuffer, can be mmap'd. Otherwise
* there would be no cache coherency between a descriptor and a VM mapping
* both to the same character device.
- *
- * Block devices can be mmap'd no matter what they represent. Cache coherency
- * is maintained as long as you do not write directly to the underlying
- * character device.
*/
#ifndef _SYS_SYSPROTO_H_
struct mmap_args {
OpenPOWER on IntegriCloud