From: Timofey Titovets <nefelim4ag@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Timofey Titovets <nefelim4ag@gmail.com>
Subject: [PATCH 0/4] Just bunch of btrfs patches
Date: Tue, 3 Oct 2017 18:06:00 +0300 [thread overview]
Message-ID: <20171003150604.19596-1-nefelim4ag@gmail.com> (raw)
Some patches has review, some not, all compile tested and hand tested.
(i.e. boot into patched system and do some small tests).
All based on kDave for-next branch
Patches:
1. Just remove useless u64 num_bytes from compress_file_range()
No functional changes
2. For make compression on on mmap'd files safe,
while compression logic works, we switch page dirty page bit on whole
input range, but input range can be much bigger the 128KiB
So try optimize that by only switch bits on current compression range
3. Function:
extent_range_clear_dirty_for_io()
extent_range_redirty_for_io()
btrfs_set_range_writeback()
Used to switch some bits on pages,
but use not obvious while (index <= end_index) to cover
unaligned end to pages.
(I don't think that not obvious for me only, as on IRC no one can help me
understand that until i found answer)
So i change handling of unaligned end to more obvious way
4. btrfs_dedupe_file_range() on range bigger then 16MiB
instead of return error, silently set it to 16MiB.
So just add loop over input range, to get working bigger range
P.S. May be that make a sense to change loop iterator to some lower value
if one of deduped files are compressed?
Thanks.
Timofey Titovets (4):
Btrfs: compress_file_range() remove dead variable num_bytes
Btrfs: clear_dirty only on pages in compression range
Btrfs: handle unaligned tail of data ranges more efficient
Btrfs: btrfs_dedupe_file_range() ioctl, remove 16MiB restriction
fs/btrfs/extent_io.c | 12 ++++++++++--
fs/btrfs/inode.c | 43 ++++++++++++++++++++++++++++++-------------
fs/btrfs/ioctl.c | 22 ++++++++++++++++++----
3 files changed, 58 insertions(+), 19 deletions(-)
--
2.14.2
next reply other threads:[~2017-10-03 15:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-03 15:06 Timofey Titovets [this message]
2017-10-03 15:06 ` [PATCH 1/4] Btrfs: compress_file_range() remove dead variable num_bytes Timofey Titovets
2017-10-10 17:39 ` David Sterba
2017-10-03 15:06 ` [PATCH 2/4] Btrfs: clear_dirty only on pages only in compression range Timofey Titovets
2017-10-10 16:22 ` David Sterba
2017-10-13 22:31 ` Timofey Titovets
2017-10-03 15:06 ` [PATCH 3/4] Btrfs: handle unaligned tail of data ranges more efficient Timofey Titovets
2017-10-10 16:37 ` David Sterba
2017-10-15 22:09 ` Timofey Titovets
2017-10-17 15:52 ` David Sterba
2017-10-03 15:06 ` [PATCH 4/4] Btrfs: btrfs_dedupe_file_range() ioctl, remove 16MiB restriction Timofey Titovets
2017-10-10 17:36 ` David Sterba
2017-11-14 10:19 ` 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=20171003150604.19596-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 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.