From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Satya <satyakiran@gmail.com>
Cc: kazutomo@mcs.anl.gov, linuxppc-dev@ozlabs.org,
edi@linux.vnet.ibm.com, david@gibson.dropbear.id.au
Subject: Re: hugetlbfs for ppc440 - kernel BUG
Date: Wed, 22 Oct 2008 09:53:13 +1100 [thread overview]
Message-ID: <1224629593.7654.279.camel@pasglop> (raw)
In-Reply-To: <acbcf3840810211546s1d72dac0kabcf1285358efbdf@mail.gmail.com>
On Tue, 2008-10-21 at 15:46 -0700, Satya wrote:
> Ben,
> Look here: http://www-unix.mcs.anl.gov/zeptoos/hugepages/
Thanks. What is the status ? Do they work fine ? Are they going to be
re-submitted for inclusion ?
Cheers,
Ben.
> thanks,
> ./satya
>
> On Tue, Oct 21, 2008 at 1:47 PM, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> On Tue, 2007-07-10 at 13:38 -0500, Satya wrote:
> > hello,
> > I am trying to implement hugetlbfs on the IBM Bluegene/L IO
> node
> > (ppc440) and I have a big problem as well as a few questions
> to ask
> > the group. I patched a 2.6.21.6 linux kernel (manually) with
> Edi
> > Shmueli's hugetlbfs implementation (found here:
> > http://patchwork.ozlabs.org/linuxppc/patch?id=8427) for
> this. I did
> > have to make slight changes (described at the end) to make
> it work.
> > My test program is a shortened version of a sys v shared
> memory
> > example described in Documentation/vm/hugetlbpage.txt
>
>
> Hi !
>
> The patchwork link unfortunately didn't survive the transition
> to
> patchwork 2.
>
> Do you know what's the status of Hugetlb support for 44x ? Is
> there any
> plan to release that for upstream inclusion ?
>
> Cheers,
> Ben.
>
>
>
next prev parent reply other threads:[~2008-10-21 22:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-10 18:38 hugetlbfs for ppc440 - kernel BUG Satya
2008-10-21 20:47 ` Benjamin Herrenschmidt
2008-10-21 22:46 ` Satya
2008-10-21 22:50 ` Satya
2008-10-23 2:42 ` David Gibson
2008-10-21 22:53 ` Benjamin Herrenschmidt [this message]
2008-10-22 0:12 ` David Gibson
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=1224629593.7654.279.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=edi@linux.vnet.ibm.com \
--cc=kazutomo@mcs.anl.gov \
--cc=linuxppc-dev@ozlabs.org \
--cc=satyakiran@gmail.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;
as well as URLs for NNTP newsgroup(s).