From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mm-commits@vger.kernel.org, senozhatsky@chromium.org,
ngupta@vflare.org, minchan@kernel.org, ddrokosov@sberdevices.ru,
avromanov@sberdevices.ru
Subject: Re: + zram-remove-double-compression-logic.patch added to mm-unstable branch
Date: Mon, 9 May 2022 12:09:25 +0900 [thread overview]
Message-ID: <YniF5R+WksISXTN3@google.com> (raw)
In-Reply-To: <20220507185744.D14CBC385A6@smtp.kernel.org>
On (22/05/07 11:57), Andrew Morton wrote:
> The 2nd trial allocation under per-cpu presumption has been used to
> prevent regression of allocation failure. However, it makes trouble for
> maintenance without significant benefit. The slowpath branch is executed
> extremely rarely: getting there is problematic. Therefore, we delete this
> branch.
>
> Since b09ab054b69b ("zram: support BDI_CAP_STABLE_WRITES"), zram has used
> QUEUE_FLAG_STABLE_WRITES to prevent buffer change between 1st and 2nd
> memory allocations. Since we remove second trial memory allocation logic,
> we could remove the STABLE_WRITES flag because there is no change buffer
> to be modified under us.
>
> Link: https://lkml.kernel.org/r/20220505094443.11728-1-avromanov@sberdevices.ru
> Signed-off-by: Alexey Romanov <avromanov@sberdevices.ru>
> Signed-off-by: Dmitry Rokosov <ddrokosov@sberdevices.ru>
> Acked-by: Minchan Kim <minchan@kernel.org>
> Cc: Nitin Gupta <ngupta@vflare.org>
> Cc: Sergey Senozhatsky <senozhatsky@chromium.org>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Sergey Senozhatsky <senozhatsky@chromium.org>
prev parent reply other threads:[~2022-05-09 3:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-07 18:57 + zram-remove-double-compression-logic.patch added to mm-unstable branch Andrew Morton
2022-05-09 3:09 ` Sergey Senozhatsky [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=YniF5R+WksISXTN3@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=avromanov@sberdevices.ru \
--cc=ddrokosov@sberdevices.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=ngupta@vflare.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.