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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D7632C3F6B0 for ; Sun, 21 Aug 2022 08:53:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229920AbiHUIxi (ORCPT ); Sun, 21 Aug 2022 04:53:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53366 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229868AbiHUIxh (ORCPT ); Sun, 21 Aug 2022 04:53:37 -0400 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:3::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8AAB51C104; Sun, 21 Aug 2022 01:53:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=ZG4Es9fzRMT5wrH3Tq+h9KlclsxiCzHKQ6STwuA6oEY=; b=NPTUpR2TGbEGKev6MERMWxooFG ZiJJjPsPAHnqBUcO2CFAj6Vu6hAc3j5M6DeVz3k2hJd7xxalHutHctTFyvYAhRSiMuYQzdMYaAa9k WBNgoPSU6TF4upc7I+yWqXWo+afkfRMrrsiTEmeBXwGm9kKSvw1mY2HuqMGQj1ybZWFBcviB7t/Jx CNZtj16845VF1Evf0T8Auz57FsdmXm7IQcRaeQn96X3j+ZSDhD8Nyc4APtWOwsUqG0QARrCSLeVgb xIMkJ0036ubpmdQL4mSj6MNnxsleHp2IQ98hONYLivxszc2hcm0EoaksqSX32ZF8ehDAQbYS5mLFa jLqkzAsg==; Received: from hch by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1oPgi5-008Q9X-HL; Sun, 21 Aug 2022 08:53:33 +0000 Date: Sun, 21 Aug 2022 01:53:33 -0700 From: Christoph Hellwig To: Eric Biggers Cc: Jaegeuk Kim , linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, linux-xfs@vger.kernel.org, linux-api@vger.kernel.org, linux-fscrypt@vger.kernel.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org, Keith Busch Subject: Re: [PATCH v4 6/9] f2fs: don't allow DIO reads but not DIO writes Message-ID: References: <20220722071228.146690-1-ebiggers@kernel.org> <20220722071228.146690-7-ebiggers@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Precedence: bulk List-ID: X-Mailing-List: linux-api@vger.kernel.org On Mon, Aug 15, 2022 at 05:55:45PM -0700, Eric Biggers wrote: > So if the zoned device feature becomes widely adopted, then STATX_DIOALIGN will > be useless on all Android devices? That sounds undesirable. Are you sure that We just need to fix f2fs to support direct I/O on zone devices. There is not good reason not to support it, in fact the way how zoned devices requires appends with the Zone Append semantics makes direct I/O way safer than how f2fs does direct I/O currently on non-zoned devices. Until then just supporting direct I/O reads on zoned devices for f2fs seems like a really bad choice given that it will lead to nasty cache incoherency.