From: Minchan Kim <minchan@kernel.org>
To: Aleksey Romanov <AVRomanov@sberdevices.ru>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
"ngupta@vflare.org" <ngupta@vflare.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"axboe@chromium.org" <axboe@chromium.org>,
kernel <kernel@sberdevices.ru>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mnitenko@gmail.com" <mnitenko@gmail.com>,
Dmitry Rokosov <DDRokosov@sberdevices.ru>
Subject: Re: [PATCH v2] zram: remove double compression logic
Date: Mon, 2 May 2022 11:11:51 -0700 [thread overview]
Message-ID: <YnAe52Eg60tjeBNK@google.com> (raw)
In-Reply-To: <20220428200107.hz65qvxf2aoz27q2@cab-wsm-0029881>
Hi Aleksey,
On Thu, Apr 28, 2022 at 08:01:12PM +0000, Aleksey Romanov wrote:
> Thanks for the reply!
>
> On Wed, Apr 27, 2022 at 08:30:16PM +0900, Sergey Senozhatsky wrote:
> > On (22/04/27 13:03), Alexey Romanov wrote:
> > > diff --git a/drivers/block/zram/zram_drv.c b/drivers/block/zram/zram_drv.c
> > > index cb253d80d72b..4be6caf43b1d 100644
> > > --- a/drivers/block/zram/zram_drv.c
> > > +++ b/drivers/block/zram/zram_drv.c
> > > @@ -1153,9 +1153,8 @@ static ssize_t debug_stat_show(struct device *dev,
> > >
> > > down_read(&zram->init_lock);
> > > ret = scnprintf(buf, PAGE_SIZE,
> > > - "version: %d\n%8llu %8llu\n",
> > > + "version: %d\n%8llu\n",
> > > version,
> > > - (u64)atomic64_read(&zram->stats.writestall),
> > > (u64)atomic64_read(&zram->stats.miss_free));
> > > up_read(&zram->init_lock);
> >
> > I think this also has to bump `version` to 2, since format of the
> > file has changed.
>
> Yes, I'll do that in the next patch.
>
> Minchan, do you have any suggestions on this patch?
> I want to fix Sergey suggestion and sumbit next patch.
You need to remove zs_free in the path "Compression failed"
Since we don't have double compression, we don't need QUEUE_FLAG_STABLE_WRITES
so you could remove QUEUE_FLAG_STABLE_WRITES, too.
Thanks.
prev parent reply other threads:[~2022-05-02 18:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-27 10:03 [PATCH v2] zram: remove double compression logic Alexey Romanov
2022-04-27 11:30 ` Sergey Senozhatsky
2022-04-28 20:01 ` Aleksey Romanov
2022-05-02 18:11 ` Minchan Kim [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=YnAe52Eg60tjeBNK@google.com \
--to=minchan@kernel.org \
--cc=AVRomanov@sberdevices.ru \
--cc=DDRokosov@sberdevices.ru \
--cc=axboe@chromium.org \
--cc=kernel@sberdevices.ru \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mnitenko@gmail.com \
--cc=ngupta@vflare.org \
--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