On Tue, Jun 09, 2020 at 02:18:06PM -0700, Samuel Sieb wrote:
On 6/9/20 1:57 PM, Dridi Boukelmoune wrote:
> On Tue, Jun 9, 2020 at 5:43 PM Samuel Sieb <samuel(a)sieb.net> wrote:
> > On 6/9/20 6:49 AM, Dridi Boukelmoune wrote:
> > > > Well, that's really the point. The one you're using is one of
the (4? 5?)
> > > > other zram implementations. It seems a bit more straightforward than
> > > > systemd one for sure.
> > >
> > > The zram-generator is probably more straightforward (with literally
> > > less layers of indirection) than what the zram package provides. I
> > > would assume that a generator is also the more idiomatic (and
> > > efficient) solution as far as systemd is concerned and I wouldn't
> > > migrating to that if it looked feature-complete and had decent
> > > documentation. There is no manual page, only a slightly confusing
> > > README that hints at simplicity and incompleteness.
> > There's also an example conf file included that has a lot of explanation
> > in it.
> I'm aware, but the explanation doesn't tell me anything I couldn't
> infer from the README.
Ok, but I don't understand what other documentation there could possibly be.
There are only two options to configure and they're both well explained.
That's the problem right here. There are more options.
compression-algorithm, max-zram-size. You need to read source to know
Description of general mechanism is also lacking. The generator
creates a service: swap-create@.service, which calls modprobe and
mkswap. There is also a .swap unit created and enabled. Have you found
those details in documentation?
And there's also this:
This program requires 1 or 3 arguments
Can you guess what the arguments are, without checking source?
Documenting this is not much work, I guess couple of hours. It will
have to be done before shipping (if Change is accepted) but it's lacking
Tomasz Torcz “God, root, what's the difference?”
tomek(a)pipebreaker.pl “God is more forgiving.”