From: Jan Kara <jack@suse.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Jan Kara <jack@suse.cz>,
linux-ext4@vger.kernel.org, Zheng Liu <gnehzuil.liu@gmail.com>,
Zheng Liu <wenqing.lz@taobao.com>,
Andreas Dilger <adilger.kernel@dilger.ca>
Subject: Re: [PATCH 1/6] ext4: cache extent hole in extent status tree for ext4_da_map_blocks()
Date: Mon, 24 Nov 2014 10:34:34 +0100 [thread overview]
Message-ID: <20141124093434.GC1888@quack.suse.cz> (raw)
In-Reply-To: <20141123054335.GA4102@thunk.org>
On Sun 23-11-14 00:43:35, Ted Tso wrote:
> On Fri, Nov 14, 2014 at 11:45:52AM +0100, Jan Kara wrote:
> > From: Zheng Liu <wenqing.lz@taobao.com>
> >
> > Currently extent status tree doesn't cache extent hole when a write
> > looks up in extent tree to make sure whether a block has been allocated
> > or not. In this case, we don't put extent hole in extent cache because
> > later this extent might be removed and a new delayed extent might be
> > added back. But it will cause a defect when we do a lot of writes. If
> > we don't put extent hole in extent cache, the following writes also need
> > to access extent tree to look at whether or not a block has been
> > allocated. It brings a cache miss. This commit fixes this defect.
> > Also if the inode doesn't have any extent, this extent hole will be
> > cached as well.
> >
> > Cc: "Theodore Ts'o" <tytso@mit.edu>
> > Cc: Andreas Dilger <adilger.kernel@dilger.ca>
> > Signed-off-by: Zheng Liu <wenqing.lz@taobao.com>
> > Signed-off-by: Jan Kara <jack@suse.cz>
>
> This patch (either when applied alone, or as part of the entire patch
> series) is causing an xfstests regression test failure:
I saw this in my testing as well but when investigating I somehow decided
it wasn't my bug and then forgot about it. Anyway, I'll check again and
resolve it either way.
Honza
> FSTYP -- ext4
> PLATFORM -- Linux/i686 kvm-xfstests 3.18.0-rc3-00537-g932e3f9
> MKFS_OPTIONS -- -q /dev/vdc
> MOUNT_OPTIONS -- -o acl,user_xattr -o block_validity /dev/vdc /vdc
>
> ext4/003 4s ... [00:14:39] [00:14:48] - output mismatch (see /results/results-4k/ext4/003.out.bad)
> --- tests/ext4/003.out 2014-10-31 10:13:03.000000000 -0400
> +++ /results/results-4k/ext4/003.out.bad 2014-11-23 00:14:48.935587897 -0500
> @@ -1,3 +1,3 @@
> QA output created by 003
> -wrote 268435456/268435456 bytes at offset 0
> +wrote 241762304/268435456 bytes at offset 0
> XXX Bytes, X ops; XX:XX:XX.X (XXX YYY/sec and XXX ops/sec)
> ...
> (Run 'diff -u tests/ext4/003.out /results/results-4k/ext4/003.out.bad' to see the entire diff)
>
> - Ted
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
next prev parent reply other threads:[~2014-11-25 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 10:45 [PATCH 0/6 v3] ext4: Extent status tree shrinker improvements Jan Kara
2014-11-14 10:45 ` [PATCH 1/6] ext4: cache extent hole in extent status tree for ext4_da_map_blocks() Jan Kara
2014-11-23 5:43 ` Theodore Ts'o
2014-11-24 9:34 ` Jan Kara [this message]
2014-11-25 14:57 ` Jan Kara
2014-11-25 16:58 ` Theodore Ts'o
2014-11-14 10:45 ` [PATCH 2/6] ext4: Move LRU list handling into extent status code Jan Kara
2014-11-23 5:48 ` Theodore Ts'o
2014-11-24 9:32 ` Jan Kara
2014-11-14 10:45 ` [PATCH 3/6] ext4: change lrm to round-robin in extent status tree shrinker Jan Kara
2014-11-14 10:45 ` [PATCH 4/6] ext4: Limit number of scanned extents in " Jan Kara
2014-11-14 10:45 ` [PATCH 5/6] ext4: Cleanup flag definitions for extent status tree Jan Kara
2014-11-14 10:45 ` [PATCH 6/6] ext4: Introduce aging to " Jan Kara
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=20141124093434.GC1888@quack.suse.cz \
--to=jack@suse.cz \
--cc=adilger.kernel@dilger.ca \
--cc=gnehzuil.liu@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=wenqing.lz@taobao.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).