Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp4405042pxv; Tue, 27 Jul 2021 06:39:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyW3yMSppwJRIFfomp7LtfQyoJcHuDRV/6m2XLBxY/wVTtWAcP8k5YP2UAL2ExdmHaZINcp X-Received: by 2002:a5d:8541:: with SMTP id b1mr7224791ios.105.1627393186665; Tue, 27 Jul 2021 06:39:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1627393186; cv=none; d=google.com; s=arc-20160816; b=x/LABvczmnqiKHovrK136r4bNdEBDLOO3mX/fkf1SHThVgqtq/XFGRpiHxV7DRR1P6 /R3Xbo9A4UGqMyWWMFrGgbsC4UBOtwIae3nQ/gApSlF6yys/msHs5QIkrI1i4QZEgnon 4yBAOCM0BrTg0lbOwsx7NAx96pcLIZMiZReYRiE59veppHuC/djf8dTyBo7orlNx2iDX JjoruUgj82ucN2m3c2MQTm4HhjOlZvF27H8Kug4SURgnB8wIE7neUYJRBDdn1UUJg0yT vB0F1FzDa179R5KuvEu1bgBn8tLrA5DC6u27q/BQ2som7kS5Pim8Py3IWiQbpnuLSK3o 9LXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:to:from:date:dkim-signature; bh=EpSbFrEHGAQA1xr1naEuF16MkP61b5G7e9AV8x/Ex4E=; b=ue1+fnipSEFA6BM9Oc9UT28Qa2lh8tD9dLNRjGPtVYCDWXVz/IikYA/D+m2PbYNnVH FXkjQCHnkM8swdTQyjBNYV6yGsE331wqg+NwRwRd2+r5/fT8xBtN99AxNonwrTfHad0+ y0L+KQNElKP79gsdYu/ea0uUm5beRFGoAhQWebceBcF4JR96hKwt5ds2WpG7lxKStDfR a8R3pmWc8dsyxX/eyHOhYi/DIdF/RENuXghU+cALoEab91PQutznubUKeLZGedzHZA1X zqy0iYJvbwDngfLD6/oW+rs01M+yPu6dRmZZ5WjhXaP3epgS5HLw02AeFnOAJvDXKcnd WSZA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=o3L8a9jE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id o22si3528346jat.98.2021.07.27.06.39.35; Tue, 27 Jul 2021 06:39:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=casper.20170209 header.b=o3L8a9jE; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236593AbhG0NiZ (ORCPT + 99 others); Tue, 27 Jul 2021 09:38:25 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36302 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236509AbhG0NiY (ORCPT ); Tue, 27 Jul 2021 09:38:24 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B7B04C061757; Tue, 27 Jul 2021 06:38:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:To:From:Date:Sender:Reply-To:Cc: Content-Transfer-Encoding:Content-ID:Content-Description; bh=EpSbFrEHGAQA1xr1naEuF16MkP61b5G7e9AV8x/Ex4E=; b=o3L8a9jEH3Ul9rQPCR8ay1CcPx wIvSa1TgAQ50cmZBTGLgdFt+6KKz9MeISZt2oLyJAD+VrxC8sVZkQDWVTFzAm7Iwxmpok/1Mp4p6l P3Nl2s2YEtHdeeEepN52ujuAy8ErrEuQsmZ0DzDilBtZpMXt8pbSZ387BLsESn7wQtqgtyy131Fgr V9tKJps9bOSaCDF4lQ4fPtAksGfWW7/qHx9sl878omOclcnrAte+06XMAscDe8xg0q4Zv3OxvS6QB 8i4Bw2KjwG4FkaEEwKm3MCpXkLEBkiiptKY01o0p92Uxi/IvCJJVRpyiIPCzrVvjXAgtyPhGczHr3 KaXHSOCg==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1m8NFL-00F2s7-Bz; Tue, 27 Jul 2021 13:36:29 +0000 Date: Tue, 27 Jul 2021 14:35:46 +0100 From: Matthew Wilcox To: dsterba@suse.cz, Christoph Hellwig , Andreas Gruenbacher , Gao Xiang , "Darrick J . Wong" , Huang Jianan , linux-erofs@lists.ozlabs.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Andreas Gruenbacher Subject: Re: [PATCH v7] iomap: make inline data support more flexible Message-ID: References: <20210723174131.180813-1-hsiangkao@linux.alibaba.com> <20210725221639.426565-1-agruenba@redhat.com> <20210726110611.459173-1-agruenba@redhat.com> <20210726121702.GA528@lst.de> <20210727082042.GI5047@twin.jikos.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210727082042.GI5047@twin.jikos.cz> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jul 27, 2021 at 10:20:42AM +0200, David Sterba wrote: > On Mon, Jul 26, 2021 at 02:17:02PM +0200, Christoph Hellwig wrote: > > > Subject: iomap: Support tail packing > > > > I can't say I like this "tail packing" language here when we have the > > perfectly fine inline wording. Same for various comments in the actual > > code. > > Yes please, don't call it tail-packing when it's an inline extent, we'll > use that for btrfs eventually and conflating the two terms has been > cofusing users. Except reiserfs, no linux filesystem does tail-packing. Hmm ... I see what reiserfs does as packing tails of multiple files into one block. What gfs2 (and ext4) do is inline data. Erofs packs the tail of a single file into the same block as the inode. If I understand what btrfs does correctly, it stores data in the btree. But (like gfs2/ext4), it's only for the entire-file-is-small case, not for its-just-ten-bytes-into-the-last-block case. So what would you call what erofs is doing if not tail-packing? Wikipedia calls it https://en.wikipedia.org/wiki/Block_suballocation which doesn't quite fit. We need a phrase which means "this isn't just for small files but for small tails of large files".