From: dean gaudet <dean@arctic.org>
To: Bill Irwin <bill.irwin@oracle.com>
Cc: Nishanth Aravamudan <nacc@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Badari Pulavarty <pbadari@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [PATCH] hugetlbfs read() support
Date: Mon, 30 Jul 2007 22:57:03 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707302252080.8176@twinlark.arctic.org> (raw)
In-Reply-To: <20070719175207.GH26380@holomorphy.com>
On Thu, 19 Jul 2007, Bill Irwin wrote:
> On Thu, Jul 19, 2007 at 10:07:59AM -0700, Nishanth Aravamudan wrote:
> > But I do think a second reason to do this is to make hugetlbfs behave
> > like a normal fs -- that is read(), write(), etc. work on files in the
> > mountpoint. But that is simply my opinion.
>
> Mine as well.
ditto. here's a few other things i've run into recently:
it should be possible to use cp(1) to load large datasets into a
hugetlbfs.
it should be possible to use ftruncate() on hugetlbfs files. (on a tmpfs
it's req'd to extend the file before mmaping... on hugetlbfs it returns
EINVAL or somesuch and mmap just magically extends files.)
it should be possible to statfs() and get usage info... this works only if
you mount with size=N.
-dean
--
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-31 5:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 1:23 Badari Pulavarty
2007-07-19 5:19 ` Andrew Morton
2007-07-19 15:51 ` Badari Pulavarty
2007-07-19 16:58 ` Andrew Morton
2007-07-19 17:07 ` Nishanth Aravamudan
2007-07-19 17:52 ` Bill Irwin
2007-07-31 5:57 ` dean gaudet [this message]
2007-07-20 4:47 ` Nick Piggin
2007-07-23 14:02 ` Nishanth Aravamudan
2007-07-20 4:29 ` Nick Piggin
2007-07-20 21:15 ` Badari Pulavarty
2007-07-20 4:39 ` Nick Piggin
2007-07-20 6:13 ` Nick Piggin
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=Pine.LNX.4.64.0707302252080.8176@twinlark.arctic.org \
--to=dean@arctic.org \
--cc=akpm@linux-foundation.org \
--cc=bill.irwin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nacc@us.ibm.com \
--cc=nickpiggin@yahoo.com.au \
--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