From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
minchan@kernel.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, Dusty Mabe <dusty@dustymabe.com>
Subject: Re: [PATCH] zram: take device and not only bvec offset into account
Date: Sun, 6 Aug 2023 16:16:01 +0900 [thread overview]
Message-ID: <20230806071601.GB907732@google.com> (raw)
In-Reply-To: <20230805081306.GA29615@lst.de>
On (23/08/05 10:13), Christoph Hellwig wrote:
> On Sat, Aug 05, 2023 at 04:46:45PM +0900, Sergey Senozhatsky wrote:
> > > Fixes: af8b04c63708 ("zram: simplify bvec iteration in __zram_make_request")
> > > Reported-by: Dusty Mabe <dusty@dustymabe.com>
> > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> >
> > Acked-by: Sergey Senozhatsky <senozhatsky@chromium.org>
>
> Btw, are there any interesting test suites you want me to run on
> a > 4K page size system now that I do have this setup available?
I don't really have any special tests. I used to run fio, but switched
to a shell script that:
1) configures zram0 and adds zram1 as writeback
2) mkfs.ext4 on zram0, cp linux tar.gz, compile (in parallel)
3) deferred recompress (idle and size based)
4) idle writeback
5) re-reads all writtenback pages
I test on a system with 4K pages, tho, I probably need to get an image
with larger PAGE_SIZE.
next prev parent reply other threads:[~2023-08-06 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-05 5:55 [PATCH] zram: take device and not only bvec offset into account Christoph Hellwig
2023-08-05 7:46 ` Sergey Senozhatsky
2023-08-05 8:13 ` Christoph Hellwig
2023-08-05 21:47 ` Dusty Mabe
2023-08-06 7:16 ` Sergey Senozhatsky [this message]
2023-08-05 22:13 ` Jens Axboe
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=20230806071601.GB907732@google.com \
--to=senozhatsky@chromium.org \
--cc=dusty@dustymabe.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@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;
as well as URLs for NNTP newsgroup(s).