From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>, clm@fb.com
Subject: [PATCH 0/4] Size reduction of btrfs_path
Date: Fri, 27 Nov 2015 16:31:32 +0100 [thread overview]
Message-ID: <cover.1448637387.git.dsterba@suse.com> (raw)
We can reduce size of btrfs_path by 32 bytes, which will lead to more objects
packed into one slab page. Performance should not be worse and could even
improve in some cases due to less cachelines used.
Targetting 4.5. Thanks.
Can be pulled from
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git dev/path-diet
David Sterba (4):
btrfs: cleanup, use enum values for btrfs_path reada
btrfs: use smaller type for btrfs_path reada
btrfs: use smaller type for btrfs_path lowest_level
btrfs: use smaller type for btrfs_path locks
fs/btrfs/ctree.c | 9 ++++-----
fs/btrfs/ctree.h | 7 ++++---
fs/btrfs/extent-tree.c | 12 ++++++------
fs/btrfs/file-item.c | 4 ++--
fs/btrfs/inode-map.c | 2 +-
fs/btrfs/inode.c | 8 ++++----
fs/btrfs/ioctl.c | 2 +-
fs/btrfs/relocation.c | 12 ++++++------
fs/btrfs/scrub.c | 2 +-
fs/btrfs/volumes.c | 6 +++---
fs/btrfs/xattr.c | 2 +-
11 files changed, 33 insertions(+), 33 deletions(-)
--
2.6.2
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-
next reply other threads:[~2015-11-27 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 15:31 David Sterba [this message]
2015-11-27 15:31 ` [PATCH 1/4] btrfs: cleanup, use enum values for btrfs_path reada David Sterba
2015-11-27 15:31 ` [PATCH 2/4] btrfs: use smaller type " David Sterba
2015-11-27 15:31 ` [PATCH 3/4] btrfs: use smaller type for btrfs_path lowest_level David Sterba
2015-11-27 15:31 ` [PATCH 4/4] btrfs: use smaller type for btrfs_path locks 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=cover.1448637387.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=clm@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 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.