[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: hugepage patches
- To: Andrew Morton <akpm@digeo.com>
- Subject: Re: hugepage patches
- From: William Lee Irwin III <wli@holomorphy.com>
- Date: Sun, 2 Feb 2003 11:59:08 -0800
- Cc: davem@redhat.com, rohit.seth@intel.com, davidm@napali.hpl.hp.com,anton@samba.org, linux-mm@kvack.org
- Fake-Sender: owner-linux-mm@kvack.org
- In-Reply-To: <20030202025546.2a29db61.akpm@digeo.com>
- Mail-Followup-To: William Lee Irwin III <wli@holomorphy.com>,Andrew Morton <akpm@digeo.com>, davem@redhat.com,rohit.seth@intel.com, davidm@napali.hpl.hp.com, anton@samba.org,linux-mm@kvack.org
- Organization: The Domain of Holomorphy
- Original-Recipient: rfc822;linux-mm-archive@humbolt.geo.uu.nl
- References: <20030131151501.7273a9bf.akpm@digeo.com> <20030202025546.2a29db61.akpm@digeo.com>
- Sender: Rik van Riel <riel@nl.linux.org>
- User-Agent: Mutt/1.3.25i
On Sun, Feb 02, 2003 at 02:55:46AM -0800, Andrew Morton wrote:
> 6/4
> hugetlbfs: fix truncate
> - Opening a hugetlbfs file O_TRUNC calls the generic vmtruncate() functions
> and nukes the kernel.
> Give S_ISREG hugetlbfs files a inode_operations, and hence a setattr
> which know how to handle these files.
> - Don't permit the user to truncate hugetlbfs files to sizes which are not
> a multiple of HPAGE_SIZE.
> - We don't support expanding in ftruncate(), so remove that code.
erm, IIRC ftruncate() was the only way to expand the things; without
read() or write() showing up this creates a huge semantic deficit.
When I wake up the rest of the way I'll eventually remember which
debate I lost that introduced an alternative method.
Leaving .setattr out of the non-directory inode ops and/or not having
a non-directory i_ops is a relatively huge omission. Not sure how
anything actually survived that.
-- 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/