From: Dave Hansen <haveblue@us.ibm.com>
To: Mark Rustad <mrustad@mac.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.6.15-rc5] hugetlb: make make_huge_pte global and fix coding style
Date: Fri, 09 Dec 2005 10:08:16 -0800 [thread overview]
Message-ID: <1134151696.3278.2.camel@localhost> (raw)
In-Reply-To: <E4ECF4F0-9442-4FFE-BE55-3EF7A1CC40F4@mac.com>
On Fri, 2005-12-09 at 11:55 -0600, Mark Rustad wrote:
> On Dec 9, 2005, at 11:16 AM, Dave Hansen wrote:
>
> > What driver needs to map huge pages? Is it in the kernel tree
> > now? If
> > not, can you post the source, please?
>
> It is a funky driver for an embedded system. I can't imagine it ever
> being in the kernel tree, because not many people want to share 768M
> of contiguous physical memory.
>
> I can post the source, but it really is a bunch of random stuff for
> am embedded application. We do make it available as part of our GPL
> source release to customers.
You'd be surprised. If we know what you're actually trying to do, we
might be able to suggest another option. As Adam said, having userspace
mmap a hugetlb area, then hand it to the driver would certainly keep
your kernel modifications to a minimum.
-- Dave
next prev parent reply other threads:[~2005-12-09 18:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-09 16:39 [PATCH 2.6.15-rc5] hugetlb: make make_huge_pte global and fix coding style Mark Rustad
2005-12-09 17:05 ` Adam Litke
2005-12-09 17:50 ` Mark Rustad
2005-12-09 17:16 ` Dave Hansen
2005-12-09 17:55 ` Mark Rustad
2005-12-09 18:08 ` Dave Hansen [this message]
2005-12-09 19:51 ` Mark Rustad
2005-12-09 20:37 ` Hugh Dickins
2005-12-09 21:18 ` Mark Rustad
2005-12-09 22:12 ` Hugh Dickins
2005-12-10 6:01 ` Mark Rustad
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=1134151696.3278.2.camel@localhost \
--to=haveblue@us.ibm.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 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.