[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <yq1mvpr7kuk.fsf@sermon.lab.mkp.net>
Date: Mon, 21 Mar 2016 14:21:39 -0400
From: "Martin K. Petersen" <martin.petersen@...cle.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: "Darrick J. Wong" <darrick.wong@...cle.com>, axboe@...nel.dk,
torvalds@...ux-foundation.org, bfields@...ldses.org, tytso@....edu,
martin.petersen@...cle.com, linux-api@...r.kernel.org,
david@...morbit.com, linux-kernel@...r.kernel.org,
shane.seymour@....com, linux-fsdevel@...r.kernel.org,
jlayton@...chiereds.net, akpm@...ux-foundation.org
Subject: Re: [PATCH 3/3] block: implement (some of) fallocate for block devices
>>>>> "Christoph" == Christoph Hellwig <hch@...radead.org> writes:
Christoph> On Mon, Mar 21, 2016 at 10:52:35AM -0700, Darrick J. Wong wrote:
>> > I don't really understand the comment. But I think you'd be much
>>
>> I don't know of a block device primitive that corresponds to the
>> "default" mode of fallocate, as documented in the manpage (i.e. mode
>> == 0). I agree that the whole thing could be simplified in the
>> manner you point out below.
Christoph> SCSI allows 'anchoring' blocks, which is pretty similar to a
Christoph> normal fallocate, but we don't support anchoring blocks in
Christoph> Linux yet.
Chicken and egg problem. I actually did tinker with this for a different
project a while back and can easily revive it.
--
Martin K. Petersen Oracle Linux Engineering
Powered by blists - more mailing lists