From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 58A3D7F8D for ; Sun, 2 Feb 2014 09:16:29 -0600 (CST) Received: from cuda.sgi.com (cuda1.sgi.com [192.48.157.11]) by relay1.corp.sgi.com (Postfix) with ESMTP id 14AA98F8040 for ; Sun, 2 Feb 2014 07:16:28 -0800 (PST) Received: from mail.parisc-linux.org ([192.25.206.14]) by cuda.sgi.com with ESMTP id axQKMNWG8BNE6lxX (version=TLSv1 cipher=AES256-SHA bits=256 verify=NO) for ; Sun, 02 Feb 2014 07:16:26 -0800 (PST) Date: Sun, 2 Feb 2014 08:16:24 -0700 From: Matthew Wilcox Subject: Re: [PATCH RESEND 0/10] fs: Introduce new flag(FALLOC_FL_COLLAPSE_RANGE) for fallocate Message-ID: <20140202151624.GK20939@parisc-linux.org> References: <1391319694-3089-1-git-send-email-linkinjeon@gmail.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <1391319694-3089-1-git-send-email-linkinjeon@gmail.com> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Namjae Jeon Cc: tytso@mit.edu, Namjae Jeon , linux-kernel@vger.kernel.org, xfs@oss.sgi.com, bpm@sgi.com, adilger.kernel@dilger.ca, viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org, jack@suse.cz, linux-ext4@vger.kernel.org, mtk.manpages@gmail.com On Sun, Feb 02, 2014 at 02:41:34PM +0900, Namjae Jeon wrote: > The semantics of this flag are following: > 1) It collapses the range lying between offset and length by removing any data > blocks which are present in this range and than updates all the logical > offsets of extents beyond "offset + len" to nullify the hole created by > removing blocks. In short, it does not leave a hole. > 2) It should be used exclusively. No other fallocate flag in combination. > 3) Offset and length supplied to fallocate should be fs block size aligned > in case of xfs and ext4. > 4) Collaspe range does not work beyond i_size. What if the file is mmaped at the time somebody issues this command? Seems to me we should drop pagecache pages that overlap with the removed blocks. If the removed range is not a multiple of PAGE_SIZE, then we should also drop any pagecache pages after the removed range. -- Matthew Wilcox Intel Open Source Technology Centre "Bill, look, we understand that you're interested in selling us this operating system, but compare it to ours. We can't possibly take such a retrograde step." _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs