From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: "'Mark Rustad'" <mrustad@mac.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.16 hugetlbfs problem
Date: Wed, 22 Mar 2006 21:43:58 -0800 [thread overview]
Message-ID: <200603230543.k2N5hhg22185@unix-os.sc.intel.com> (raw)
In-Reply-To: <EE85F1AA-A258-4D4F-A46F-34253AEE280E@mac.com>
Mark Rustad wrote on Wednesday, March 22, 2006 3:33 PM
> >> I seem to be having trouble using hugetlbfs with kernel 2.6.16. I
> >> have a small test program that worked with 2.6.16-rc5, but fails with
> >> 2.6.16-rc6 or the release. The program is below. Given a path to a
> >> file on a hugetlbfs, it opens/creates the file, mmaps it and tries to
> >> access the first word. On 2.6.16-rc5, it works. On 2.6.16, it hangs
> >> page-faulting until it is killed.
> >
> > On what platform? Things like hugetlb and address space layout
> > (you're requesting a specific mmap() address I noticed) are very
> > platform specific.
>
> This is on a Xeon, without PAE with the 1GB no-highmem memory map, in
> all three cases. This is a 32-bit kernel running on a Nacona CPU. I
> also had an unmap call over the range to be mmap-ed, but the failure/
> success cases were the same, so I removed it to reduce the test
> program further.
It might be something else happening in your environment. I ran your test
code on a similar system. It ran just fine.
- Ken
next prev parent reply other threads:[~2006-03-23 5:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 22:10 Mark Rustad
2006-03-22 22:13 ` David S. Miller
2006-03-22 23:32 ` Mark Rustad
2006-03-23 5:43 ` Chen, Kenneth W [this message]
2006-03-23 15:36 ` Mark Rustad
2006-03-23 19:13 ` Mark Rustad
2006-03-24 17:52 ` 2.6.16 hugetlbfs problem - DEBUG_PAGEALLOC Mark Rustad
2006-03-25 1:24 ` Chen, Kenneth W
2006-03-25 1:47 ` David S. Miller
2006-03-25 2:53 ` Andrew Morton
2006-03-25 7:29 ` Chen, Kenneth W
2006-03-25 8:15 ` Andrew Morton
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=200603230543.k2N5hhg22185@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrustad@mac.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®