summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoralex <alex@FreeBSD.org>1996-11-13 23:55:28 +0000
committeralex <alex@FreeBSD.org>1996-11-13 23:55:28 +0000
commit76176371e0be8ba2aa9a0d55063bdabc84fcbf46 (patch)
treecbcb4a71b29a2b511afea12bedcac2e319473150
parent7523dfa587381e08aab416063123b0403d447574 (diff)
downloadFreeBSD-src-76176371e0be8ba2aa9a0d55063bdabc84fcbf46.zip
FreeBSD-src-76176371e0be8ba2aa9a0d55063bdabc84fcbf46.tar.gz
Slight rewording of the BUGS section.
-rw-r--r--lib/libc/sys/mmap.28
1 files changed, 4 insertions, 4 deletions
diff --git a/lib/libc/sys/mmap.2 b/lib/libc/sys/mmap.2
index d70d871..32fcb44 100644
--- a/lib/libc/sys/mmap.2
+++ b/lib/libc/sys/mmap.2
@@ -213,13 +213,13 @@ was specified and insufficient memory was available.
.Sh BUGS
.Ar len
-is limit to 2GB. Mmapping slightly more than 2GB doesn't work, but
-mapping a window of size (filesize % 2GB) for file sizes of slightly
-less than 2G, 4GB, 6GB and 8GB.
+is limited to 2GB. Mmapping slightly more than 2GB doesn't work, but
+it is possible to map a window of size (filesize % 2GB) for file sizes
+of slightly less than 2G, 4GB, 6GB and 8GB.
The limit is imposed for a variety of reasons. Most of them have to do
with FreeBSD not wanting to use 64 bit offsets in the VM system due to
-the extreme performance penalty. So FreeBSD use 32bit page indexes and
+the extreme performance penalty. So FreeBSD uses 32bit page indexes and
this gives FreeBSD a maximum of 8TB filesizes. It's actually bugs in
the filesystem code that causes the limit to be further restricted to
1TB (loss of precision when doing blockno calculations).
OpenPOWER on IntegriCloud