From: SeongJae Park <sj38.park@gmail.com>
To: corbet@lwn.net
Cc: akpm@linux-foundation.org, hughd@google.com,
mike.kravetz@oracle.com, joern@logfs.org,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
SeongJae Park <sj38.park@gmail.com>
Subject: [PATCH] Documentation: update libhugetlbfs site url
Date: Wed, 13 Jan 2016 16:47:56 +0900 [thread overview]
Message-ID: <1452671276-21284-1-git-send-email-sj38.park@gmail.com> (raw)
The site for libhugetlbfs has moved from sourceforge to github. This
commit updates the old url.
Signed-off-by: SeongJae Park <sj38.park@gmail.com>
---
Documentation/filesystems/proc.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt
index e95aa1c..fde9fd0 100644
--- a/Documentation/filesystems/proc.txt
+++ b/Documentation/filesystems/proc.txt
@@ -820,7 +820,7 @@ by migrate-type and finishes with details on how many page blocks of each
type exist.
If min_free_kbytes has been tuned correctly (recommendations made by hugeadm
-from libhugetlbfs http://sourceforge.net/projects/libhugetlbfs/), one can
+from libhugetlbfs https://github.com/libhugetlbfs/libhugetlbfs/), one can
make an estimate of the likely number of huge pages that can be allocated
at a given point in time. All the "Movable" blocks should be allocatable
unless memory has been mlock()'d. Some of the Reclaimable blocks should
--
1.9.1
next reply other threads:[~2016-01-13 7:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 7:47 SeongJae Park [this message]
2016-01-13 21:41 ` Mike Kravetz
2016-01-14 20:28 ` Jonathan Corbet
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=1452671276-21284-1-git-send-email-sj38.park@gmail.com \
--to=sj38.park@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=hughd@google.com \
--cc=joern@logfs.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.kravetz@oracle.com \
/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
all inboxes | Powered by JetHome®