From: "dada1" <dada1@cosmosbay.com>
To: "Linus Torvalds" <torvalds@transmeta.com>,
"Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Fw: Linux v2.5.54
Date: Fri, 3 Jan 2003 09:40:26 +0100 [thread overview]
Message-ID: <00fe01c2b303$c3e67790$760010ac@edumazet> (raw)
> o remove hugetlb syscalls
So finally they did it ...
But mmap(NULL, ...) is not yet supported, this is really sad.
And arch/i386/Kconfig and Documentation/vm/hugetlbpage.txt still document
the sys_alloc_hugepages()/sys_free_hugepages() syscalls.
A simple program that doesnt know at all how the memory is layed out by
kernel/glibc can not easily get some 4Mo pages in a single syscall.
sys_alloc_hugepage() was very convenient for that.
Another problem :
if you mount hugetlbfs in /huge, then create a file /huge/BIG of size 4Mo,
then use :
dd if=/huge/BIG of=/dev/null
the dd process hangs on 'D' state : the read() syscall just hang forever.
Thanks
next reply other threads:[~2003-01-03 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 8:40 dada1 [this message]
2003-01-03 9:26 ` Fw: Linux v2.5.54 Andrew Morton
2003-01-03 9:55 ` William Lee Irwin III
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='00fe01c2b303$c3e67790$760010ac@edumazet' \
--to=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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