From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>
Subject: [PATCH 0/5] Parameter reduction in compression wrappers
Date: Fri, 17 Feb 2017 19:05:46 +0100 [thread overview]
Message-ID: <cover.1487354456.git.dsterba@suse.com> (raw)
I've noticed that some of the parameters passed to compress_pages are redundant
and that we can either reuse a parameter for both input and output value
(number of pages) or we can infer some value from the existing parameters (the
maximum output limit).
There's no functional change, the stack consumption is slightly smaller.
David Sterba (5):
btrfs: merge length input and output parameter in compress_pages
btrfs: merge nr_pages input and output parameter in compress_pages
btrfs: export compression buffer limits in a header
btrfs: use predefined limits for calculating maximum number of pages for compression
btrfs: derive maximum output size in the compression implementation
fs/btrfs/compression.c | 33 ++++++++++++++-------------------
fs/btrfs/compression.h | 28 +++++++++++++++++++---------
fs/btrfs/inode.c | 37 +++++++++++++------------------------
fs/btrfs/lzo.c | 10 +++++-----
fs/btrfs/zlib.c | 9 +++++----
5 files changed, 56 insertions(+), 61 deletions(-)
next reply other threads:[~2017-02-17 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 18:05 David Sterba [this message]
2017-02-17 18:05 ` [PATCH 1/5] btrfs: merge length input and output parameter in compress_pages David Sterba
2017-02-17 18:05 ` [PATCH 2/5] btrfs: merge nr_pages " David Sterba
2017-02-17 18:05 ` [PATCH 3/5] btrfs: export compression buffer limits in a header David Sterba
2017-02-20 8:07 ` Qu Wenruo
2017-02-17 18:05 ` [PATCH 4/5] btrfs: use predefined limits for calculating maximum number of pages for compression David Sterba
2017-02-17 18:06 ` [PATCH 5/5] btrfs: derive maximum output size in the compression implementation 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.1487354456.git.dsterba@suse.com \
--to=dsterba@suse.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).