From: David Howells <dhowells@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: dhowells@redhat.com, Qu Wenruo <quwenruo.btrfs@gmx.com>,
Andreas Dilger <adilger@dilger.ca>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Chris Mason <clm@fb.com>, Josef Bacik <josef@toxicpanda.com>,
David Sterba <dsterba@suse.com>,
linux-ext4 <linux-ext4@vger.kernel.org>,
linux-xfs <linux-xfs@vger.kernel.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Problems with determining data presence by examining extents?
Date: Fri, 17 Jan 2020 16:43:38 +0000 [thread overview]
Message-ID: <469988.1579279418@warthog.procyon.org.uk> (raw)
In-Reply-To: <20200116101344.GA16435@lst.de>
Christoph Hellwig <hch@lst.de> 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
next prev parent reply other threads:[~2020-01-17 16:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 16:48 Problems with determining data presence by examining extents? David Howells
2020-01-14 22:49 ` Theodore Y. Ts'o
2020-01-15 3:54 ` Qu Wenruo
2020-01-15 12:46 ` Andreas Dilger
2020-01-15 13:10 ` Qu Wenruo
2020-01-15 13:31 ` Christoph Hellwig
2020-01-15 19:48 ` Andreas Dilger
2020-01-16 10:16 ` Christoph Hellwig
2020-01-15 20:55 ` David Howells
2020-01-15 22:11 ` Andreas Dilger
2020-01-15 23:09 ` David Howells
2020-01-26 18:19 ` Zygo Blaxell
2020-01-15 14:35 ` David Howells
2020-01-15 14:48 ` Christoph Hellwig
2020-01-15 14:59 ` David Howells
2020-01-16 10:13 ` Christoph Hellwig
2020-01-17 16:43 ` David Howells [this message]
2020-01-15 14:20 ` David Howells
2020-01-15 8:38 ` Christoph Hellwig
2020-01-15 13:50 ` David Howells
2020-01-15 14:05 ` David Howells
2020-01-15 14:24 ` Qu Wenruo
2020-01-15 14:50 ` David Howells
2020-01-15 14:15 ` David Howells
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=469988.1579279418@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=adilger@dilger.ca \
--cc=clm@fb.com \
--cc=darrick.wong@oracle.com \
--cc=dsterba@suse.com \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.