From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4E520C7EE2E for ; Fri, 9 Jun 2023 12:56:26 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 88F708E0002; Fri, 9 Jun 2023 08:56:25 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 83F568E0001; Fri, 9 Jun 2023 08:56:25 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 72DF28E0002; Fri, 9 Jun 2023 08:56:25 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 605908E0001 for ; Fri, 9 Jun 2023 08:56:25 -0400 (EDT) Received: from smtpin01.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 3A812160201 for ; Fri, 9 Jun 2023 12:56:25 +0000 (UTC) X-FDA: 80883207930.01.300B7CD Received: from out30-112.freemail.mail.aliyun.com (out30-112.freemail.mail.aliyun.com [115.124.30.112]) by imf18.hostedemail.com (Postfix) with ESMTP id 11A641C0014 for ; Fri, 9 Jun 2023 12:56:21 +0000 (UTC) Authentication-Results: imf18.hostedemail.com; dkim=none; spf=pass (imf18.hostedemail.com: domain of hsiangkao@linux.alibaba.com designates 115.124.30.112 as permitted sender) smtp.mailfrom=hsiangkao@linux.alibaba.com; dmarc=pass (policy=none) header.from=alibaba.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1686315383; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=QzB8yHatPD9vP+Sg9kBdhmS/CWEqNYFGUirzPQBRhnM=; b=1jiNEP/9MxGKIzFO+yf95LzicE0fHReLDDTnzRVnfH6aWU5s2RPB5oZ+ZZI1MTsJrnHiwL AHGOfUo06n2FoZ5iuBXUCPSxY+5QrlnHZY7re4I/MMZK95UNlXk4eUjY2GYxHFazzb+qGs Lu5zYgcWbn8MJB9aWurLgm7lDqCXdek= ARC-Authentication-Results: i=1; imf18.hostedemail.com; dkim=none; spf=pass (imf18.hostedemail.com: domain of hsiangkao@linux.alibaba.com designates 115.124.30.112 as permitted sender) smtp.mailfrom=hsiangkao@linux.alibaba.com; dmarc=pass (policy=none) header.from=alibaba.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1686315383; a=rsa-sha256; cv=none; b=OpESMxBu5CAAT0fLiBa1Kx1oDLygX1J35G4OwYIgh+n3UMqxMmV1Vqxnt2nvhmv+ILYIya dNKkEX8OurRHBG/QIloUzeb7eAbAaCYKK/h7KGSKicKHDNt89zjSkTZ3AH4flUWd0D+Lao qMmDb5xpGbHvIMeoV5OSbw/0dvTy73A= X-Alimail-AntiSpam:AC=PASS;BC=-1|-1;BR=01201311R691e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=ay29a033018045176;MF=hsiangkao@linux.alibaba.com;NM=1;PH=DS;RN=7;SR=0;TI=SMTPD_---0VkiB-Kj_1686315376; Received: from 192.168.3.7(mailfrom:hsiangkao@linux.alibaba.com fp:SMTPD_---0VkiB-Kj_1686315376) by smtp.aliyun-inc.com; Fri, 09 Jun 2023 20:56:17 +0800 Message-ID: Date: Fri, 9 Jun 2023 20:56:15 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: [RFC PATCH 00/80] Rust PuzzleFS filesystem driver To: "Ariel Miculas (amiculas)" , Christian Brauner Cc: "linux-fsdevel@vger.kernel.org" , "rust-for-linux@vger.kernel.org" , "linux-mm@kvack.org" , "Serge Hallyn (shallyn)" , Colin Walters References: <20230609063118.24852-1-amiculas@cisco.com> <20230609-feldversuch-fixieren-fa141a2d9694@brauner> <20230609-nachrangig-handwagen-375405d3b9f1@brauner> From: Gao Xiang In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 11A641C0014 X-Rspam-User: X-Stat-Signature: psx1y96k3jyqwacoyhcspo7pym5i75ar X-Rspamd-Server: rspam01 X-HE-Tag: 1686315381-54694 X-HE-Meta: U2FsdGVkX1/EqPqBcrXMdxJnyiCdY0Dy5yW/WksBOOgFGuCLQ0XlEQP3FBfNudFPCI5iVTaQamCLs3uK2eJCRKPnCYh5iQ0N9FJtnOZyrvlDoCGsu7h61/tvx050yKQjVE8XGN6VKXSlNNKpmQ64IoqAL/XfM99mgO+JCuJS4/cVXAdom7M5U2LDCXyN9wJQgavsT9nMLibDzkfd8j+jeqnmi0hEdxdzRzKwdyAlQOejLkIxotVLVY7zF3IXAZ1yIDyAnpOeT60PtHMrjZXUgbrBcRb5LN6/y8iIFXwfPs5c61ab6ihU/1Z8MdI/lOR9wKQAoJIN9kwOIS97/j2YUdGijMbz5XJfS70GdY7komA8QfSy+aPg+IOfDpxBVv8RsGD97GZBzQ8QRwzQiWxnUKWJM6mcKubnIcp81uXZEMT1DWHBZzhYRp+5tIMAyYfGsHo8wgZaIxJ+5ZdKL1G+LpDvlg9ROcYOfF18b8eZrUpyhdFa0ODV60eGrH0gFw1TE8LLxNJknm4q7tugJQHMhO6NMMI7KicvbeyOVPfA5cbdmdH/+e//um/R+Gms6A+QDt+hqv3SL7rfWVXyqHO8aOxyRCJcRQbopuSj67GzwVxQNkQyRhzyLRuQ9KgKqOXsrNTPlphzlsdbOZ319kvaj3XIivPryEZc2sgfE0dv/HtPJj77OQjHpM6lLYUIstPksOZv4EkWJ+3AiWyNoYuANpiSRYhHRjg9BPRFLpM+BsHf3d+bzHQc20qeJLW8OSnC5oqM+Ot3ay2nIelYsDV73ZqrAAD0R81MNZnUdV3haZS8JcfW57su6C9akZOX8KPcXjoDKOfGIL2x3vQdVhExl63GomX+Ak7MLj/8F+zu0HAOCFQiB2ZUZBG1b6TUD8PBpK9lKRuznZ5kI4aHgz3vqESa4uvacCKCQa0lwYXObZ/zJGbtOAFE/E6n8SSc1T0vTLA/jbMjTRUJd1FAjJZ isHeyaz6 OslSN3z6PiD0f2RDsPU+TILJFPlL7CPABG73scUO6y5YmZ8EemJY1S1jKTpSJrStDXIXYjw7qkiJClUXHsPUUG/1u2f0Jn/Cq5z2WSGUh4OtFxR4dHYsGt/60XBG9kYuaJDgS X-Bogosity: Ham, tests=bogofilter, spamicity=0.000083, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 2023/6/9 20:03, Ariel Miculas (amiculas) wrote: ... > > But aside from the infrastructure discussion: > > This is yet another filesystem for solving the container image problem > in the kernel with the addition of yet another filesystem. We just went > through this excercise with another filesystem. So I'd expect some > reluctance here. Tbh, the container world keeps sending us filesystems > at an alarming rate. That's two within a few months and that leaves a > rather disorganized impression. Just a head up. Since Rust kernel infrastructure is too premature, it's impossible to handle page cache / iomap and many useful stuffs. In the long term, at least (someday) after Rust infrastructure is mature, I will implement EROFS ino Rust as a try as well. As for chunk CDC, I don't see it's hard (since we already have some CDC approach since Linux v6.1) but as an effective disk filesystem for performance, EROFS on-disk data is all block-aligned to match storage and page cache alignment. If it's really needed, I could update a more complete (but ineffective and slow) index version to implement unaligned extents (both for decoded and encoded sides). Yet I really think the main purpose of a kernel filesystem is to make full use of kernel infrastructure for performance (like page cache handling) otherwise a FUSE approach is enough. Finally, as for OCI container image stuffs, I'd like to avoid saying this topic anymore on the list (too tired about this). I've seen _three_ in-kernel approaches already before this one and I tend to avoid listing the complete names (including FUSE alternatives) here. I really suggest if you guys could sit down and plan at least a complete OCI standard for the next image format (even you don't want to reuse any exist filesystem for whatever reasons). Thanks, Gao Xiang