From: Jassi Brar <jassisinghbrar@gmail.com>
To: senozhatsky@chromium.org
Cc: axboe@kernel.dk, gost.dev@samsung.com, kernel@pankajraghav.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
minchan@kernel.org, p.raghav@samsung.com
Subject: Re: [PATCH 0/5] Improve zram writeback performance
Date: Wed, 25 Sep 2024 10:53:14 -0500 [thread overview]
Message-ID: <20240925155314.107632-1-jassisinghbrar@gmail.com> (raw)
In-Reply-To: <20230919003338.GA3748@google.com>
Hi Sergey, Hi Minchan,
>> Gentle ping Minchan and Sergey.
>
>Hello,
>
>zram writeback is currently under (heavy) rework, the series hasn't
>been published yet, but it's in the making for some time already.
>The biggest change is that zram will support compressed writeback,
>that is writeback of compressed objects, as opposed to current design
>when zram de-compresses pages before writeback.
>
>Minchan will have more details, but I guess we'll need to wait for
>that series to land.
May I please know where we are with the rework? Is there somewhere I
could look up the compressed-writeback work-in-progress code?
Regards,
Jassi
next prev parent reply other threads:[~2024-09-25 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230911133442eucas1p2f773a475e0a6dc1a448c63884d58c8d3@eucas1p2.samsung.com>
2023-09-11 13:34 ` Pankaj Raghav
2023-09-11 13:34 ` [PATCH 1/5] zram: move index preparation to a separate function in writeback_store Pankaj Raghav
2023-09-11 13:34 ` [PATCH 2/5] zram: encapsulate writeback to the backing bdev in a function Pankaj Raghav
2023-09-11 13:34 ` [PATCH 3/5] zram: add alloc_block_bdev_range() and free_block_bdev_range() Pankaj Raghav
2023-09-11 13:34 ` [PATCH 4/5] zram: batch IOs during writeback to improve performance Pankaj Raghav
2023-09-11 13:34 ` [PATCH 5/5] zram: don't overload blk_idx variable in writeback_store() Pankaj Raghav
2023-09-18 13:53 ` [PATCH 0/5] Improve zram writeback performance Pankaj Raghav
2023-09-19 0:33 ` Sergey Senozhatsky
2023-09-19 14:20 ` Pankaj Raghav
2024-09-25 15:53 ` Jassi Brar [this message]
2024-09-26 4:33 ` Sergey Senozhatsky
2024-09-29 22:21 ` Jassi Brar
2024-09-26 4:41 ` Sergey Senozhatsky
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=20240925155314.107632-1-jassisinghbrar@gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=axboe@kernel.dk \
--cc=gost.dev@samsung.com \
--cc=kernel@pankajraghav.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=p.raghav@samsung.com \
--cc=senozhatsky@chromium.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
all inboxes | Powered by JetHome®