Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp9250053ybl; Fri, 17 Jan 2020 08:44:11 -0800 (PST) X-Google-Smtp-Source: APXvYqxcnr7ovSZhO6ILyQfPRGZV24J3Jj5ui1SzYCWKFvngOYuENeHfU1zQWnn9VXyjNjEXLMEL X-Received: by 2002:a9d:6183:: with SMTP id g3mr6695073otk.304.1579279450790; Fri, 17 Jan 2020 08:44:10 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579279450; cv=none; d=google.com; s=arc-20160816; b=tht03pSCYvE0PEpmx3EZZec5iksx6CyO9rEjFo22K2kA167zGM/txfCEfaF6qMfNu6 z0jMXbJAMHjBn4eeJ6SSdlBC7yul1VZUBUOXJw6KciVFtDgDLDQG++dQXe9QnLNExeLg OeO3lT6PqV9ZrzlTi0ceLlyCrR25bCpeK3QCEfyOOdl55MVQT2/ZeJPQyEvh+gJEGECk hbmMyLZclDkniX9VZBg4Gwx1xtjy72Ud6xRyNW5QwMXONDXxVvS+Nr6AhTLOQ8qVaB5T /dme7NsHH3JNEhlhAINAypcoHwi7lFkllUAx2gdobg5WbncvXpTwJ9YTUoZ7IMhRHMKq tTFg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:content-id:mime-version :subject:cc:to:references:in-reply-to:from:organization :dkim-signature; bh=7ywZah/acU88OdI0elxdfP2wlFAEGYbYZ2X9Wl0Y+ps=; b=rGVl1sHCOeCoicGYsurejEg6+bBUrK4bvNVew8CKeedMX3F0dA3VZWNDBCU6TnVAVZ QsNudosn4cTCq9KjgPZntkE4j9P3l1+oMvXwEbpW2JHRtzhxX+zW+s3BhvJok17Aa237 I0UcF3QC1LxYOCRqc5dD5bwB5pOIw5zHEycOxgGJGgo67VUODjFU5KA8c8upkTUBUbZr oZn7ib0DYN55VChb6aTDNWceN02438z4s5Sprhtjx8nfHRI2rAlDRDNkHa00EQpr96YF r1AOpzpcqklvJlQBRSImRtot68gPJ6t4aMLVkiwQX0jLjh3SHCE771BviGnxBtG/bfeS zvPA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aPONDv90; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id a12si13331261oie.87.2020.01.17.08.43.59; Fri, 17 Jan 2020 08:44:10 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=aPONDv90; spf=pass (google.com: best guess record for domain of linux-ext4-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-ext4-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727665AbgAQQn5 (ORCPT + 99 others); Fri, 17 Jan 2020 11:43:57 -0500 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:23025 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726901AbgAQQn4 (ORCPT ); Fri, 17 Jan 2020 11:43:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1579279435; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=7ywZah/acU88OdI0elxdfP2wlFAEGYbYZ2X9Wl0Y+ps=; b=aPONDv90XNmbxI3XjQCdAGwZTtIDrtRA9Q0T72fYp+mdaEnn8imbL7tTgheeHPMfkJt2OT s77r75OsSZkYkLphG+JFZ9Az5m3JWc/KcMMVMyxyJjYy8hriYMTh8802fxzF64aZ/u/dpS aCfw7gMeKiYcC7nNmoJZoneHrxc/d3c= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-363-LeC-d3cZMfmN1hLN6_W0bg-1; Fri, 17 Jan 2020 11:43:49 -0500 X-MC-Unique: LeC-d3cZMfmN1hLN6_W0bg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5DDF66125B; Fri, 17 Jan 2020 16:43:42 +0000 (UTC) Received: from warthog.procyon.org.uk (ovpn-120-49.rdu2.redhat.com [10.10.120.49]) by smtp.corp.redhat.com (Postfix) with ESMTP id BDA115C54A; Fri, 17 Jan 2020 16:43:39 +0000 (UTC) Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903 From: David Howells In-Reply-To: <20200116101344.GA16435@lst.de> References: <20200116101344.GA16435@lst.de> <20200115144839.GA30301@lst.de> <20200115133101.GA28583@lst.de> <4467.1579020509@warthog.procyon.org.uk> <00fc7691-77d5-5947-5493-5c97f262da81@gmx.com> <27181AE2-C63F-4932-A022-8B0563C72539@dilger.ca> <26093.1579098922@warthog.procyon.org.uk> <28755.1579100378@warthog.procyon.org.uk> To: Christoph Hellwig Cc: dhowells@redhat.com, Qu Wenruo , Andreas Dilger , linux-fsdevel , Al Viro , "Theodore Y. Ts'o" , "Darrick J. Wong" , Chris Mason , Josef Bacik , David Sterba , linux-ext4 , linux-xfs , linux-btrfs , Linux Kernel Mailing List Subject: Re: Problems with determining data presence by examining extents? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <469987.1579279418.1@warthog.procyon.org.uk> Date: Fri, 17 Jan 2020 16:43:38 +0000 Message-ID: <469988.1579279418@warthog.procyon.org.uk> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 Sender: linux-ext4-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org Christoph Hellwig wrote: > File systems usually pad zeroes where they have to, typically for > sub-blocksize writes. Disabling this would break data integrity. I understand that. I can, however, round up the netfs I/O granule size and alignment to a multiple of the cachefile I/O block size. Also, I'm doing DIO, so I have to use block size multiples. But if the filesystem can avoid bridging large, appropriately sized and aligned blocks, then I can use it. David