From: David Sterba <dsterba@suse.cz>
To: dsterba@suse.cz, Josef Bacik <josef@toxicpanda.com>,
linux-btrfs@vger.kernel.org, kernel-team@fb.com
Subject: Re: [PATCH 11/13] btrfs: keep track of the root owner for relocation reads
Date: Thu, 14 Jan 2021 19:03:37 +0100 [thread overview]
Message-ID: <20210114180337.GZ6430@twin.jikos.cz> (raw)
In-Reply-To: <20210111222315.GN6430@twin.jikos.cz>
On Mon, Jan 11, 2021 at 11:23:15PM +0100, David Sterba wrote:
> On Wed, Dec 16, 2020 at 11:22:15AM -0500, Josef Bacik wrote:
> > --- a/fs/btrfs/relocation.c
> > +++ b/fs/btrfs/relocation.c
> > @@ -98,6 +98,7 @@ struct tree_block {
> > u64 bytenr;
> > }; /* Use rb_simple_node for search/insert */
> > struct btrfs_key key;
> > + u64 owner;
> > unsigned int level:8;
> > unsigned int key_ready:1;
>
> This would probably lead to bad packing, key is 17 bytes and placing
> u64 after that adds 7 bytes for proper alignment. The bitfield members
> following the key are aligned to a byte so it would work if owner is
> before key.
Easy fix and size 64 is also more cache friendly.
@@ -12256,22 +12256,18 @@ struct tree_block {
struct rb_node rb_node __attribute__((__aligned__(8))); /* 0 24 */
u64 bytenr; /* 24 8 */
} __attribute__((__aligned__(8))) __attribute__((__aligned__(8))); /* 0 32 */
- struct btrfs_key key; /* 32 17 */
+ u64 owner; /* 32 8 */
+ struct btrfs_key key; /* 40 17 */
- /* XXX 7 bytes hole, try to pack */
+ /* Bitfield combined with next fields */
- u64 owner; /* 56 8 */
- /* --- cacheline 1 boundary (64 bytes) --- */
- unsigned int level:8; /* 64: 0 4 */
- unsigned int key_ready:1; /* 64: 8 4 */
+ unsigned int level:8; /* 56: 8 4 */
+ unsigned int key_ready:1; /* 56:16 4 */
- /* size: 72, cachelines: 2, members: 5 */
- /* sum members: 57, holes: 1, sum holes: 7 */
- /* sum bitfield members: 9 bits (1 bytes) */
+ /* size: 64, cachelines: 1, members: 5 */
/* padding: 4 */
- /* bit_padding: 23 bits */
+ /* bit_padding: 15 bits */
/* forced alignments: 1 */
- /* last cacheline: 8 bytes */
} __attribute__((__aligned__(8)));
next prev parent reply other threads:[~2021-01-14 18:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 16:22 [PATCH 00/13] Serious fixes for different error paths Josef Bacik
2020-12-16 16:22 ` [PATCH 01/13] btrfs: don't get an EINTR during drop_snapshot for reloc Josef Bacik
2021-01-11 21:56 ` David Sterba
2020-12-16 16:22 ` [PATCH 02/13] btrfs: initialize test inodes location Josef Bacik
2020-12-18 10:30 ` Nikolay Borisov
2020-12-21 16:58 ` David Sterba
2020-12-16 16:22 ` [PATCH 03/13] btrfs: fix reloc root leak with 0 ref reloc roots on recovery Josef Bacik
2020-12-16 16:22 ` [PATCH 04/13] btrfs: splice remaining dirty_bg's onto the transaction dirty bg list Josef Bacik
2021-01-11 22:09 ` David Sterba
2020-12-16 16:22 ` [PATCH 05/13] btrfs: do not WARN_ON() if we can't find the reloc root Josef Bacik
2021-01-11 22:14 ` David Sterba
2020-12-16 16:22 ` [PATCH 06/13] btrfs: add ASSERT()'s for deleting backref cache nodes Josef Bacik
2021-01-11 22:18 ` David Sterba
2020-12-16 16:22 ` [PATCH 07/13] btrfs: do not double free backref nodes on error Josef Bacik
2020-12-16 16:22 ` [PATCH 08/13] btrfs: abort the transaction if we fail to inc ref in btrfs_copy_root Josef Bacik
2021-01-11 22:20 ` David Sterba
2020-12-16 16:22 ` [PATCH 09/13] btrfs: modify the new_root highest_objectid under a ref count Josef Bacik
2020-12-18 11:18 ` Nikolay Borisov
2020-12-16 16:22 ` [PATCH 10/13] btrfs: fix lockdep splat in btrfs_recover_relocation Josef Bacik
2020-12-16 16:22 ` [PATCH 11/13] btrfs: keep track of the root owner for relocation reads Josef Bacik
2021-01-11 22:23 ` David Sterba
2021-01-14 18:03 ` David Sterba [this message]
2020-12-16 16:22 ` [PATCH 12/13] btrfs: do not cleanup upper nodes in btrfs_backref_cleanup_node Josef Bacik
2020-12-16 16:22 ` [PATCH 13/13] btrfs: don't clear ret in btrfs_start_dirty_block_groups Josef Bacik
2021-01-08 16:44 ` [PATCH 00/13] Serious fixes for different error paths David Sterba
2021-01-14 18:20 ` David Sterba
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=20210114180337.GZ6430@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
/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