From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] zram01.sh: Rewrite to run by single filesystem
Date: Mon, 9 Nov 2026 20:39:19 +0100 [thread overview]
Message-ID: <20261109193919.GA665818@pevik> (raw)
In-Reply-To: <20261109131211.GB631538@pevik>
> > Hi!
Anyway, I've sent a patch which rewrites test zram_fill_fs() to use write file
with single 'dd' instead of many 'dd' while loop for 1kb.
https://lore.kernel.org/ltp/20261109193344.669217-1-pvorel@suse.cz/T/#u
https://patchwork.kernel.org/project/ltp/patch/20261109193344.669217-1-pvorel@suse.cz/
...
> What is the exact problem you are trying to fix?
I owe you an explanation. zram01.sh is very slow on btrfs.
More info is in thread of that patch.
https://lore.kernel.org/ltp/20261109193809.GA669592@pevik/
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-11-09 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 16:41 [LTP] [PATCH 1/1] zram01.sh: Rewrite to run by single filesystem Petr Vorel
2026-11-06 18:35 ` [LTP] " linuxtestproject.agent
2026-11-09 12:09 ` [LTP] [PATCH 1/1] " Cyril Hrubis
2026-11-09 13:12 ` Petr Vorel
2026-11-09 19:39 ` Petr Vorel [this message]
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=20261109193919.GA665818@pevik \
--to=pvorel@suse.cz \
--cc=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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