linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: David Sterba <dsterba@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 1/2] btrfs: define compression levels statically
Date: Mon, 12 Aug 2019 11:30:42 +0300	[thread overview]
Message-ID: <ae30ae87-0e4a-af31-5a58-b32e7364588e@suse.com> (raw)
In-Reply-To: <78207f6784c457dad6583f7bc7eecc495c7d5d54.1565362438.git.dsterba@suse.com>



On 9.08.19 г. 17:55 ч., David Sterba wrote:
> The maximum and default levels do not change and can be defined
> directly. The set_level callback was a temporary solution and will be
> removed.
> 
> Signed-off-by: David Sterba <dsterba@suse.com>
> ---
>  fs/btrfs/compression.h | 4 ++++
>  fs/btrfs/lzo.c         | 2 ++
>  fs/btrfs/zlib.c        | 2 ++
>  fs/btrfs/zstd.c        | 2 ++
>  4 files changed, 10 insertions(+)
> 
> diff --git a/fs/btrfs/compression.h b/fs/btrfs/compression.h
> index 2035b8eb1290..07b2009dc63f 100644
> --- a/fs/btrfs/compression.h
> +++ b/fs/btrfs/compression.h
> @@ -162,6 +162,10 @@ struct btrfs_compress_op {
>  	 * if the level is out of bounds or the default if 0 is passed in.
>  	 */
>  	unsigned int (*set_level)(unsigned int level);
> +
> +	/* Maximum level supported by the compression algorithm */
> +	int max_level;
> +	int default_level;

can levels be negative? If not just define those as unsigned ints and in
the next patch it won't be necessary to use min_t but plain min.

>  };
>  
>  /* The heuristic workspaces are managed via the 0th workspace manager */
> diff --git a/fs/btrfs/lzo.c b/fs/btrfs/lzo.c
> index 579d53ae256f..adac6cb30d65 100644
> --- a/fs/btrfs/lzo.c
> +++ b/fs/btrfs/lzo.c
> @@ -523,4 +523,6 @@ const struct btrfs_compress_op btrfs_lzo_compress = {
>  	.decompress_bio		= lzo_decompress_bio,
>  	.decompress		= lzo_decompress,
>  	.set_level		= lzo_set_level,
> +	.max_level		= 1,
> +	.default_level		= 1,
>  };
> diff --git a/fs/btrfs/zlib.c b/fs/btrfs/zlib.c
> index b86b7ad6b900..03d6c3683bd9 100644
> --- a/fs/btrfs/zlib.c
> +++ b/fs/btrfs/zlib.c
> @@ -437,4 +437,6 @@ const struct btrfs_compress_op btrfs_zlib_compress = {
>  	.decompress_bio		= zlib_decompress_bio,
>  	.decompress		= zlib_decompress,
>  	.set_level              = zlib_set_level,
> +	.max_level		= 9,
> +	.default_level		= BTRFS_ZLIB_DEFAULT_LEVEL,
>  };
> diff --git a/fs/btrfs/zstd.c b/fs/btrfs/zstd.c
> index 3837ca180d52..b2b23a6a497d 100644
> --- a/fs/btrfs/zstd.c
> +++ b/fs/btrfs/zstd.c
> @@ -729,4 +729,6 @@ const struct btrfs_compress_op btrfs_zstd_compress = {
>  	.decompress_bio = zstd_decompress_bio,
>  	.decompress = zstd_decompress,
>  	.set_level = zstd_set_level,
> +	.max_level	= ZSTD_BTRFS_MAX_LEVEL,
> +	.default_level	= ZSTD_BTRFS_DEFAULT_LEVEL,
>  };
> 

  reply	other threads:[~2019-08-12  8:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-09 14:55 [PATCH 0/2] Compression level API cleanups David Sterba
2019-08-09 14:55 ` [PATCH 1/2] btrfs: define compression levels statically David Sterba
2019-08-12  8:30   ` Nikolay Borisov [this message]
2019-08-20 14:35     ` David Sterba
2019-08-09 14:55 ` [PATCH 2/2] btrfs: compression: replace set_level callbacks by a common helper David Sterba
2019-08-11 13:05   ` kbuild test robot
2019-08-11 13:08   ` kbuild test robot

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=ae30ae87-0e4a-af31-5a58-b32e7364588e@suse.com \
    --to=nborisov@suse.com \
    --cc=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).