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 1EF4CC47DA9 for ; Tue, 30 Jan 2024 08:05:47 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id A82846B0071; Tue, 30 Jan 2024 03:05:46 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id A32BF6B008A; Tue, 30 Jan 2024 03:05:46 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 8FB156B008C; Tue, 30 Jan 2024 03:05:46 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 7A2A16B0071 for ; Tue, 30 Jan 2024 03:05:46 -0500 (EST) Received: from smtpin06.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay04.hostedemail.com (Postfix) with ESMTP id 0FE021A0B41 for ; Tue, 30 Jan 2024 08:05:46 +0000 (UTC) X-FDA: 81735243492.06.92F4034 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by imf25.hostedemail.com (Postfix) with ESMTP id 569FFA0014 for ; Tue, 30 Jan 2024 08:05:44 +0000 (UTC) Authentication-Results: imf25.hostedemail.com; dkim=none; spf=pass (imf25.hostedemail.com: domain of hch@lst.de designates 213.95.11.211 as permitted sender) smtp.mailfrom=hch@lst.de; dmarc=none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1706601944; 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: in-reply-to:in-reply-to:references:references; bh=tvY+56Dyb0t9837XU0kJIDbv7odTCnM1DgRRAbxBVCU=; b=udmk9Xp03Kfa/akrbvh2KTUGRfjUm/ds15JhCTSrUk04myy5Bi2phFsq0Wt0SiPDlpHo1R L2Qqn+MQfwjwO0eNxyaa9RgDbEB/2nm3kf7j/m943yC6BI4EyouuO6d6pUVABjtS6QMU6P FkJj+E47n5IiI0Wh5wtIHksI2F7QlQI= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1706601944; a=rsa-sha256; cv=none; b=Q51ZMTDeljkeZO04GV9WswfKoEYo+5PKrcF0Op004OGZhjYN7wJ8BM+mB2K2Eay5l6IM+U AefoHuIbDPH319Hc8wUT9eisHOHByuK7Rja5hL6Tc/0/U9iCtYEzYGTyHJfPmi4Kur+KT4 pHYDi8D0l0rQAwQgZZc1eUXZTkSiGmU= ARC-Authentication-Results: i=1; imf25.hostedemail.com; dkim=none; spf=pass (imf25.hostedemail.com: domain of hch@lst.de designates 213.95.11.211 as permitted sender) smtp.mailfrom=hch@lst.de; dmarc=none Received: by verein.lst.de (Postfix, from userid 2407) id ACC2C68C4E; Tue, 30 Jan 2024 09:05:40 +0100 (CET) Date: Tue, 30 Jan 2024 09:05:40 +0100 From: Christoph Hellwig To: Matthew Wilcox Cc: Christoph Hellwig , Chandan Babu R , "Darrick J. Wong" , Hugh Dickins , Andrew Morton , linux-xfs@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH 07/20] shmem: document how to "persist" data when using shmem_*file_setup Message-ID: <20240130080540.GB22621@lst.de> References: <20240129143502.189370-1-hch@lst.de> <20240129143502.189370-8-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) X-Rspamd-Queue-Id: 569FFA0014 X-Rspam-User: X-Stat-Signature: ify1p3mst6mqo4os7jdcuxmp937d8yt1 X-Rspamd-Server: rspam03 X-HE-Tag: 1706601944-46860 X-HE-Meta: U2FsdGVkX19ROFxJ6XD9ocYwDtkE2vpkBVRkNbwa4IhWHeXgIC57c4/DM+L1i4xf6n+WeHZX+VSR4PgJM6NYbESHTVZHWF6YX/e2dWVBufT+eoHxb/IZP6NInIYGL+6/tA4TclPiY8AvIWnmmOjQdJ9/jJSXsbd07MyB39PoIsBrghpUiIEA5Oi3ugKoWmYBTtlW/3ugvPVAxHlCsTTFhxKlpLiGGVe9fnLWTeRdtah8BrqNlFXkE+Bf+zKNPSPsE/5VEU9L2K6bHRfPxsrfExi4siBhClsjEpNq8/GN1Ld9kC+9unGKZtKwU1YOJF3+yuabMmV5ZnQKs0k71cG2Up8+KnAmh9uyaJjBdI/gSWrb0U5+Ov1z6vJ4defZv7TOGKiXSww179O4Ho6FiWyf5SDSSIuGxP6mgwphuh9g/6pvdJ7spDT/efzR5+YoabM8bCOLCKfMU3lgmN6S6zaK+MP7axdwGiDzDpynf+NeqTOcp0B8mX/6LMN+5XgjQQSkCCzQYLaZhdRysttj+/MqyEFkbLpgiqowErqTFXeeEK9A8isS+Jcw8NELCBX/ml64Kr+M28HZdQUmIjA84lSOI9vT+lluZQrevC7BSZ9uMJnMrjHZbMuVramqTPyTnkj87JU8jL4lRxXIlDj+hYuMKPDD1ULjGnkOcm75mUB7LbzWxDCwTGbL+JCaSNgiIQMco3SVtus87FbVAQ6CYseCIpuwRBDiasJNm/d56D1rRTPYysNwG+H8ycR5hV5BYkzXdOrh9lLv1BGRHzLR+qB7CFPkrz36RMo7/lHkDVf1+gEkN7/ejBziU+hc7DoKFfkSpjKyo72RV6mTOSjKPE8YyDm6Pg78AHYwhBC2P3peMEAehTOoX448COBrM+ulTbLllXinikGalwk/LrCfQwKYQ+IRBvhax9CfUPewdj7/jsqYUfibjymVmF843kigOJ74lcfFdXlV+jpVmV8V+LQ hG/yZcAI hKf+5QroL9QRw2Xg8CD5/dJJBsAXK2h+/yP5ApcHXETOvDJNf1wV0m3TsOf8qQxNrFcI/eHnzGiOlmpI8FMteo+Bygw== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Tue, Jan 30, 2024 at 06:06:12AM +0000, Matthew Wilcox wrote: > take that out as part of the shmem conversion to buffered_write_ops. Oh, and I think shmem is actually a good candidate for iomap_file_buffered_write. I think it just needs to plug shmem_get_folio into iomap_folio_ops ->get_folio and provide an identify mapped iomap like the block device.