From: riel@surriel.com (Rik van Riel)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Regarding Hugetlbfs
Date: Sun, 27 Mar 2011 09:56:13 -0400 [thread overview]
Message-ID: <4D8F41FD.3000702@surriel.com> (raw)
In-Reply-To: <AANLkTi=dN7QD8COA6pSw+K7QFJkVT9=qK2QqoH-yLPqE@mail.gmail.com>
On 03/24/2011 06:55 AM, solmac john wrote:
> I am having the following query regarding Huge pages and hugetlbfs.
> 1-> How Hugetlbfs is dependent on hardware ?
Hugetlbfs needs two things:
1) the hardware supports large pages, simultaneously running
with normal sized pages
2) someone wrote the hugetlbfs architecture dependent code
for that hardware
> 2-> Huge pages which is architecture dependent and ARM arm
> architecture supports Tiny, small and large pages will it support
> hugetlbfs if not then why ?
That I don't know. Does ARM support running with normal and
large pages simultaneously?
--
All rights reversed.
next prev parent reply other threads:[~2011-03-27 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 10:55 Regarding Hugetlbfs solmac john
2011-03-27 13:56 ` Rik van Riel [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-24 8:54 Regarding hugetlbfs solmac john
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=4D8F41FD.3000702@surriel.com \
--to=riel@surriel.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).