From: Andrew Morton <akpm@linux-foundation.org>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Minchan Kim <minchan@kernel.org>,
Jerome Marchand <jmarchan@redhat.com>,
Nitin Gupta <ngupta@vflare.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv8 5/6] zram: add set_max_streams knob
Date: Thu, 27 Feb 2014 15:27:52 -0800 [thread overview]
Message-ID: <20140227152752.add72f47d6a90c1e208c9edd@linux-foundation.org> (raw)
In-Reply-To: <1393417679-13657-6-git-send-email-sergey.senozhatsky@gmail.com>
On Wed, 26 Feb 2014 15:27:58 +0300 Sergey Senozhatsky <sergey.senozhatsky@gmail.com> wrote:
> This patch allows to change max_comp_streams on initialised zcomp.
>
> Introduce zcomp set_max_streams() knob, zcomp_strm_multi_set_max_streams()
> and zcomp_strm_single_set_max_streams() callbacks to change streams limit
> for zcomp_strm_multi and zcomp_strm_single, accordingly. set_max_streams
> for single steam zcomp does nothing.
>
> If user has lowered the limit, then zcomp_strm_multi_set_max_streams()
> attempts to immediately free extra streams (as much as it can, depending
> on idle streams availability).
>
> Note, this patch does not allow to change stream 'policy' from single to
> multi stream (or vice versa) on already initialised compression backend.
>
> ...
>
> @@ -137,6 +137,28 @@ static void zcomp_strm_multi_put(struct zcomp *comp, struct zcomp_strm *zstrm)
> zcomp_strm_free(comp, zstrm);
> }
>
> +/* change max_strm limit */
> +static int zcomp_strm_multi_set_max_streams(struct zcomp *comp, int num_strm)
> +{
> + struct zcomp_strm_multi *zs = comp->stream;
> +
> + spin_lock(&zs->strm_lock);
> + zs->max_strm = num_strm;
> + /*
> + * if user has lowered the limit and there are idle streams,
> + * immediately free as much streams (and memory) as we can.
> + */
> + while (zs->avail_strm > num_strm && !list_empty(&zs->idle_strm)) {
> + struct zcomp_strm *zstrm = list_entry(zs->idle_strm.next,
> + struct zcomp_strm, list);
struct zcomp_strm *zstrm;
zstrm = list_entry(zs->idle_strm.next, struct zcomp_strm, list);
will avoid the coding-style mess.
> + list_del(&zstrm->list);
> + zcomp_strm_free(comp, zstrm);
> + zs->avail_strm--;
> + }
> + spin_unlock(&zs->strm_lock);
> + return 0;
> +}
next prev parent reply other threads:[~2014-02-27 23:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 12:27 [PATCHv8 0/6] add compressing abstraction and multi stream support Sergey Senozhatsky
2014-02-26 12:27 ` [PATCHv8 1/6] zram: introduce compressing backend abstraction Sergey Senozhatsky
2014-02-27 23:18 ` Andrew Morton
2014-02-28 17:40 ` Sergey Senozhatsky
2014-02-26 12:27 ` [PATCHv8 2/6] zram: use zcomp compressing backends Sergey Senozhatsky
2014-02-26 12:27 ` [PATCHv8 3/6] zram: factor out single stream compression Sergey Senozhatsky
2014-02-27 23:20 ` Andrew Morton
2014-02-26 12:27 ` [PATCHv8 4/6] zram: add multi stream functionality Sergey Senozhatsky
2014-02-27 23:22 ` Andrew Morton
2014-02-27 23:25 ` Andrew Morton
2014-02-26 12:27 ` [PATCHv8 5/6] zram: add set_max_streams knob Sergey Senozhatsky
2014-02-27 23:27 ` Andrew Morton [this message]
2014-02-26 12:27 ` [PATCHv8 6/6] zram: document max_comp_streams Sergey Senozhatsky
2014-02-27 23:28 ` Andrew Morton
2014-02-27 2:16 ` [PATCHv8 0/6] add compressing abstraction and multi stream support Minchan Kim
2014-02-27 8:08 ` Sergey Senozhatsky
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=20140227152752.add72f47d6a90c1e208c9edd@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=jmarchan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky@gmail.com \
/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
all inboxes | Powered by JetHome®