[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.00.1111211405121.1879@sister.anvils>
Date: Mon, 21 Nov 2011 14:13:22 -0800 (PST)
From: Hugh Dickins <hughd@...gle.com>
To: Christoph Hellwig <hch@...radead.org>
cc: Josef Bacik <josef@...hat.com>, Kay Sievers <kay.sievers@...y.org>,
Cong Wang <amwang@...hat.com>, linux-kernel@...r.kernel.org,
akpm@...ux-foundation.org, Pekka Enberg <penberg@...nel.org>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
Lennart Poettering <lennart@...ttering.net>,
KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
linux-mm@...ck.org
Subject: Re: [V2 PATCH] tmpfs: add fallocate support
On Mon, 21 Nov 2011, Christoph Hellwig wrote:
> On Sun, Nov 20, 2011 at 01:39:12PM -0800, Hugh Dickins wrote:
>
> > But since the present situation is that tmpfs has one interface to
> > punching holes, madvise(MADV_REMOVE), that IBM were pushing 5 years ago;
> > but ext4 (and others) now a fallocate(FALLOC_FL_PUNCH_HOLE) interface
> > which IBM have been pushing this year: we do want to normalize that
> > situation and make them all behave the same way.
>
> FALLOC_FL_PUNCH_HOLE was added by Josef Bacik, who happens to work for
> Red Hat, but I doubt he was pushing any corporate agenda there, he was
> mostly making btrfs catch up with the 15 year old XFS hole punching
> ioctl.
Yeah, my apologies to Josef and to IBM and to XFS
for my regrettable little outburst of snarkiness :(
>
>
> > And if tmpfs is going to support fallocate(FALLOC_FL_PUNCH_HOLE),
> > looking at Amerigo's much more attractive V2 patch, it would seem
> > to me perverse to permit the deallocation but fail the allocation.
>
> Agreed.
Thanks a lot for useful info, and saving me looking up the ENOSPC issue.
Hugh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists