From: Bill Irwin <bill.irwin@oracle.com>
To: Nishanth Aravamudan <nacc@us.ibm.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Badari Pulavarty <pbadari@us.ibm.com>,
Linux Memory Management <linux-mm@kvack.org>,
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 09:10:57 -0700 [thread overview]
Message-ID: <20070710161057.GW26380@holomorphy.com> (raw)
In-Reply-To: <20070710152846.GD27655@us.ibm.com>
On Tue, Jul 10, 2007 at 08:28:46AM -0700, Nishanth Aravamudan wrote:
> I agree and sounds like something to bring up at KS (again?) or the
> VM/FS summit. But, for now, hugetlbfs is the supported interface and
> libhugetlbfs has run into this issue supporting one of its features. So
> I would like to see this make it in.
> Just my $0.02 as a libhuge developer.
It should also be there to make it more like a normal filesystem,
though your use case is of vastly higher priority than such concerns.
As far as large pages for the generic VM/VFS, I cast my absentee
vote(s) in favor of such, not that anyone gives a damn what I think.
-- wli
--
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 16:10 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
2007-07-10 15:28 ` Nishanth Aravamudan
2007-07-10 16:10 ` Bill Irwin [this message]
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=20070710161057.GW26380@holomorphy.com \
--to=bill.irwin@oracle.com \
--cc=agl@us.ibm.com \
--cc=clameter@sgi.com \
--cc=hch@infradead.org \
--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