From: "David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
"David Prévot" <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
Subject: [PATCH] madvise.2: tfix
Date: Wed, 21 Sep 2011 22:13:46 -0400 [thread overview]
Message-ID: <1316657626-30903-1-git-send-email-taffit@debian.org> (raw)
Signed-off-by: David Prévot <taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
---
man2/madvise.2 | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/man2/madvise.2 b/man2/madvise.2
index 59e6846..c87877c 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -226,9 +226,9 @@ to replace them with huge pages.
The kernel will also allocate huge pages directly when the region is
naturally aligned to the huge page size (see
.BR posix_memalign (2)).
-This feature is primarily aimmed at applications that use large mappings of
+This feature is primarily aimed at applications that use large mappings of
data and access large regions of that memory at a time (e.g. virtualization
-systems such as qemu).
+systems such as QEMU).
It can very easily waste memory (e.g. a 2MB mapping that only ever accesses
1 byte will result in 2MB of wired memory instead of one 4KB page).
See the kernel source file
--
1.7.6.3
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2011-09-22 2:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 2:13 David Prévot [this message]
[not found] ` <1316657626-30903-1-git-send-email-taffit-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2011-09-22 2:59 ` [PATCH] madvise.2: tfix Michael Kerrisk
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 17:28 Matheus Tavares
2021-12-06 19:20 ` Alejandro Colomar (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1316657626-30903-1-git-send-email-taffit@debian.org \
--to=taffit-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox