From: David Gibson <dwg@au1.ibm.com>
To: Edi Shmueli <edi@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/1] PPC32 : Huge-page support for ppc440 - 2.6.19-rc4 - revised
Date: Wed, 13 Dec 2006 10:02:11 +1100 [thread overview]
Message-ID: <20061212230211.GC12707@localhost.localdomain> (raw)
In-Reply-To: <457ED2F7.9070406@linux.vnet.ibm.com>
On Tue, Dec 12, 2006 at 11:04:07AM -0500, Edi Shmueli wrote:
[snip]
> Thanks David,
> One step at a time, lets start with libhugetlbfs :-)
> I'm successfully able to run most of my tests using the library, backing my data,text and BSS with huge-pages.
> There is a major improvement in performance, similar to what I reported above.
> Good job with the library !!!
Ok.. how does the library's own testsuite go ("make check"). That
testsuite has tests for kernel bugs as well as library bugs.
> There is a problem though when a program calls "fopen".
> I see hugetlbfs does the unmapping/mapping , moves control to main(),
> and then a crash with the following error:
> "*** glibc detected *** free(): invalid pointer: 0x3002a008 ***"
> This happens inside fopen() (....which never returns).
Ok, do you get any similar problems with the minimal tests in the
testsuite?
`> Here is the detailed output.
>
> /bgd-public/edi/IS # ./is.A.linux_ser_hugetlbfs
> libhugetlbfs: Hugepage segment 0 (phdr 2): 0x10000000-0x10001b70 (filesz=0x1b70) (prot = 0x5)
> libhugetlbfs: Hugepage segment 1 (phdr 3): 0x11000000-0x170006e8 (filesz=0x274) (prot = 0x7)
> libhugetlbfs: HUGETLB_SHARE=0, sharing disabled
> libhugetlbfs: Got unshared fd as expected -- Preparing
> libhugetlbfs: Mapped hugeseg at 0x31000000. Copying 0x1b70 bytes from 0x10000000...
> done
> libhugetlbfs: Minimal copy was not performed
> libhugetlbfs: Prepare succeeded
> libhugetlbfs: HUGETLB_SHARE=0, sharing disabled
> libhugetlbfs: Got unshared fd as expected -- Preparing
> libhugetlbfs: Mapped hugeseg at 0x31000000. Copying 0x274 bytes from 0x11000000...
> done
> libhugetlbfs: Minimal copy was not performed
> libhugetlbfs: Prepare succeeded
> *** glibc detected *** free(): invalid pointer: 0x3002a008 ***
> Aborted
If you can send me a non-whitespace-mangled version of your patch, I
can try to replicate this here. If you made any hacks to libhugetlbfs
to get it working on ppc32, a patch for those would be handy too.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
prev parent reply other threads:[~2006-12-12 23:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 17:00 [PATCH 1/1] PPC32 : Huge-page support for ppc440 - 2.6.19-rc4 - revised Edi Shmueli
2006-12-04 7:01 ` David Gibson
2006-12-12 16:04 ` Edi Shmueli
2006-12-12 23:02 ` David Gibson [this message]
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=20061212230211.GC12707@localhost.localdomain \
--to=dwg@au1.ibm.com \
--cc=edi@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.