From: Christoph Hellwig <hch@infradead.org>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Linux Memory Management <linux-mm@kvack.org>,
nacc@us.ibm.com, clameter@sgi.com,
Bill Irwin <bill.irwin@oracle.com>,
agl@us.ibm.com
Subject: Re: [RFC][PATCH] hugetlbfs read support
Date: Tue, 10 Jul 2007 10:17:20 +0100 [thread overview]
Message-ID: <20070710091720.GA28371@infradead.org> (raw)
In-Reply-To: <1184009291.31638.8.camel@dyn9047017100.beaverton.ibm.com>
On Mon, Jul 09, 2007 at 12:28:11PM -0700, Badari Pulavarty wrote:
> Comments/flames ?
>
> Thanks,
> Badari
>
> Support for reading from hugetlbfs files. libhugetlbfs lets application
> text/data to be placed in large pages. When we do that, oprofile doesn't
> work - since it tries to read from it.
>
> This code is very similar to what do_generic_mapping_read() does, but
> I can't use it since it has PAGE_CACHE_SIZE assumptions. Christoph
> Lamater's cleanup to pagecache would hopefully give me all of this.
The code looks fine, but I really hate that we need it all all. We really
should make the general VM/FS code large page aware and get rid of this
whole hack called hugetlbfs..
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-07-10 9:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 19:28 Badari Pulavarty
2007-07-10 9:17 ` Christoph Hellwig [this message]
2007-07-10 15:28 ` Nishanth Aravamudan
2007-07-10 16:10 ` Bill Irwin
2007-07-10 15:36 ` Bill Irwin
2007-07-10 18:38 ` Badari Pulavarty
2007-07-10 15:37 ` Bill Irwin
2007-07-10 15:43 ` Nishanth Aravamudan
2007-07-10 16:12 ` Bill Irwin
2007-07-10 18:34 ` Badari Pulavarty
2007-07-10 18:53 ` Christoph Lameter
2007-07-10 18:57 ` Bill Irwin
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=20070710091720.GA28371@infradead.org \
--to=hch@infradead.org \
--cc=agl@us.ibm.com \
--cc=bill.irwin@oracle.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=nacc@us.ibm.com \
--cc=pbadari@us.ibm.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