From: Karel Zak <kzak@redhat.com>
To: kerolasa@gmail.com
Cc: util-linux <util-linux@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH 8/8] zramctl: allow use of --algorithm and --streams alone
Date: Wed, 6 Aug 2014 10:20:26 +0200 [thread overview]
Message-ID: <20140806082026.GH19820@x2.net.home> (raw)
In-Reply-To: <CAG27Bk29oWnsjQDHJJmvENsr9ghcnq0soOFCx3fzEJ1SYMmfFQ@mail.gmail.com>
On Tue, Aug 05, 2014 at 11:36:59PM +0100, Sami Kerola wrote:
> On 4 August 2014 12:55, Karel Zak <kzak@redhat.com> wrote:
> > On Mon, Aug 04, 2014 at 12:08:10AM +0100, Sami Kerola wrote:
> >> Earlier the --algorithm and --streams had to be combined with --size. To
> >> user requirement to combine with --size was indirectly told using
> >> following message.
> >
> > And is it really supported by kernel? I see in
> > Documentation/blockdev/zram.txt:
> >
> > In order to enable compression backend's multi stream support
> > max_comp_streams must be initially set to desired concurrency
> > level before ZRAM device initialisation.
> >
> > I guess that when you set disksize the zram device is "locked" for
> > setting changes. It means that modify already initialized (created)
> > zram devices is impossible. You have to reset the device to "unlock"
> > the device setting.
>
> After playing with zramctl I found out --algorithm must be set before
> --size. The --streams can be set after --size, but not if device is in use.
> When device is in use none of the settings are allowed.
I'd like to keep the command line semantic simple and stupid and
support --streams and --algorithm for device initialization (it means
with --size) only. We don't have to export to command line all the
crazy kernel implementation details.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-08-06 8:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 23:08 [PATCH 8/8] zramctl: allow use of --algorithm and --streams alone Sami Kerola
2014-08-03 23:24 ` Bernhard Voelker
2014-08-04 11:55 ` Karel Zak
2014-08-05 22:36 ` Sami Kerola
2014-08-06 8:20 ` Karel Zak [this message]
2014-08-06 12:19 ` Sergey Senozhatsky
2014-08-06 20:48 ` Sami Kerola
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=20140806082026.GH19820@x2.net.home \
--to=kzak@redhat.com \
--cc=kerolasa@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=util-linux@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