From: Timofey Titovets <nefelim4ag@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Timofey Titovets <nefelim4ag@gmail.com>
Subject: [PATCH 0/4] Btrfs: just bunch of patches to ioctl.c
Date: Tue, 19 Dec 2017 13:02:43 +0300 [thread overview]
Message-ID: <20171219100247.13880-1-nefelim4ag@gmail.com> (raw)
1st patch, remove 16MiB restriction from extent_same ioctl(),
by doing iterations over passed range.
I did not see much difference in performance, so it's just remove
logic restriction.
2-3 pathes, update defrag ioctl():
- Fix bad behaviour with full rewriting all compressed
extents in defrag range. (that also make autodefrag on compressed fs
not so expensive)
- Allow userspace specify NONE as target compression type,
that allow users to uncompress files by defragmentation with btrfs-progs
- Make defrag ioctl understood requested compression type and current
compression type of extents, to make btrfs fi def -rc<type>
idempotent operation.
i.e. now possible to say, make all extents compressed with lzo,
and btrfs will not recompress lzo compressed data.
Same for zlib, zstd, none.
(patch to btrfs-progs in PR on kdave GitHub).
4th patch, reduce size of struct btrfs_inode
- btrfs_inode store fields like: prop_compress, defrag_compress and
after 3rd patch, change_compress.
They use unsigned as a type, and use 12 bytes in sum.
But change_compress is a bitflag, and prop_compress/defrag_compress
only store compression type, that currently use 0-3 of 2^32-1.
So, set a bitfields on that vars, and reduce size of btrfs_inode:
1136 -> 1128.
Timofey Titovets (4):
Btrfs: btrfs_dedupe_file_range() ioctl, remove 16MiB restriction
Btrfs: make should_defrag_range() understood compressed extents
Btrfs: allow btrfs_defrag_file() uncompress files on defragmentation
Btrfs: reduce size of struct btrfs_inode
fs/btrfs/btrfs_inode.h | 5 +-
fs/btrfs/inode.c | 4 +-
fs/btrfs/ioctl.c | 203 +++++++++++++++++++++++++++++++------------------
3 files changed, 133 insertions(+), 79 deletions(-)
--
2.15.1
next reply other threads:[~2017-12-19 10:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-19 10:02 Timofey Titovets [this message]
2017-12-19 10:02 ` [PATCH 1/4] Btrfs: btrfs_dedupe_file_range() ioctl, remove 16MiB restriction Timofey Titovets
2017-12-19 21:23 ` Darrick J. Wong
2018-01-08 9:17 ` Timofey Titovets
2017-12-19 10:02 ` [PATCH 2/4] Btrfs: make should_defrag_range() understood compressed extents Timofey Titovets
2018-05-29 14:05 ` Timofey Titovets
2017-12-19 10:02 ` [PATCH 3/4] Btrfs: allow btrfs_defrag_file() uncompress files on defragmentation Timofey Titovets
2017-12-19 10:02 ` [PATCH 4/4] Btrfs: reduce size of struct btrfs_inode Timofey Titovets
2018-01-09 10:53 ` [PATCH 0/4] Btrfs: just bunch of patches to ioctl.c Timofey Titovets
2018-02-09 9:00 ` Timofey Titovets
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=20171219100247.13880-1-nefelim4ag@gmail.com \
--to=nefelim4ag@gmail.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;
as well as URLs for NNTP newsgroup(s).