On Wed, 26 Feb 2014 15:27:58 +0300 Sergey Senozhatsky 
<[email protected]> 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;
> +}

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to