From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: dsterba@suse.cz
Subject: [PATCH 0/3 v2] compression ops args clean up and trace point
Date: Fri, 26 May 2017 15:44:57 +0800 [thread overview]
Message-ID: <20170526074500.20342-1-anand.jain@oracle.com> (raw)
Patch 1 and 2 are preparatory and clean up patches, and patch 3 adds
the trace point for the compression.
I have used same trace function for both compress and decompress
as I wanted to maintain compress and decompress debug data aligned
v2: added patch #2
Anand Jain (3):
btrfs: btrfs_decompress_bio() could accept compressed_bio instead
btrfs: reduce arguments for decompress_bio ops
btrfs: add compression trace points
fs/btrfs/compression.c | 70 +++++++++++---------------------------------
fs/btrfs/compression.h | 44 +++++++++++++++++++++++++---
fs/btrfs/lzo.c | 10 +++----
fs/btrfs/zlib.c | 9 +++---
include/trace/events/btrfs.h | 36 +++++++++++++++++++++++
5 files changed, 103 insertions(+), 66 deletions(-)
--
2.10.0
next reply other threads:[~2017-05-26 7:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 7:44 Anand Jain [this message]
2017-05-26 7:44 ` [PATCH 1/3 v2] btrfs: btrfs_decompress_bio() could accept compressed_bio instead Anand Jain
2017-05-26 7:42 ` Nikolay Borisov
2017-05-26 17:54 ` David Sterba
2017-05-26 7:44 ` [PATCH 2/3 v2] btrfs: reduce arguments for decompress_bio ops Anand Jain
2017-05-26 7:43 ` Nikolay Borisov
2017-05-26 8:34 ` Anand Jain
2017-05-26 14:07 ` kbuild test robot
2017-05-26 22:39 ` Anand Jain
2017-05-26 22:36 ` [PATCH] fixup: " Anand Jain
2017-05-29 13:52 ` David Sterba
2017-05-26 7:45 ` [PATCH 3/3 v2] btrfs: add compression trace points Anand Jain
2017-05-26 18:08 ` David Sterba
2017-05-26 23:37 ` Anand Jain
2017-05-26 18:09 ` [PATCH 0/3 v2] compression ops args clean up and trace point 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=20170526074500.20342-1-anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--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).