From: Vitaly Wool <vitaly.wool@konsulko.com>
To: Shakeel Butt <shakeelb@google.com>
Cc: Minchan Kim <minchan@kernel.org>,
Tian Tao <tiantao6@hisilicon.com>,
Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
Andrew Morton <akpm@linux-foundation.org>,
Barry Song <song.bao.hua@hisilicon.com>,
Linux MM <linux-mm@kvack.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Subject: Re: [RFC mm/zswap 1/2] mm/zswap: add the flag can_sleep_mapped
Date: Thu, 14 Jan 2021 19:53:13 +0100 [thread overview]
Message-ID: <CAM4kBBKLw5LiTqcjjcGQF3mBysvFJFs2khRjw7VRVXHNM4Pryg@mail.gmail.com> (raw)
In-Reply-To: <CALvZod5E_00AL2+FDvty-JOg7+pAT3CBh_qizS6-9dpQoMtrRQ@mail.gmail.com>
On Thu, Jan 14, 2021 at 7:43 PM Shakeel Butt <shakeelb@google.com> wrote:
>
> On Thu, Jan 14, 2021 at 10:29 AM Minchan Kim <minchan@kernel.org> wrote:
> >
> > On Fri, Dec 25, 2020 at 07:02:50PM +0800, Tian Tao wrote:
> > > add a flag to zpool, named is "can_sleep_mapped", and have it set true
> > > for zbud/z3fold, set false for zsmalloc. Then zswap could go the current
> > > path if the flag is true; and if it's false, copy data from src to a
> > > temporary buffer, then unmap the handle, take the mutex, process the
> > > buffer instead of src to avoid sleeping function called from atomic
> > > context.
> > >
> > > Signed-off-by: Tian Tao <tiantao6@hisilicon.com>
> > > ---
> > > include/linux/zpool.h | 3 +++
> > > mm/zpool.c | 13 +++++++++++++
> > > mm/zswap.c | 50 +++++++++++++++++++++++++++++++++++++++++++++-----
> > > 3 files changed, 61 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/include/linux/zpool.h b/include/linux/zpool.h
> > > index 51bf430..e899701 100644
> > > --- a/include/linux/zpool.h
> > > +++ b/include/linux/zpool.h
> > > @@ -73,6 +73,7 @@ u64 zpool_get_total_size(struct zpool *pool);
> > > * @malloc: allocate mem from a pool.
> > > * @free: free mem from a pool.
> > > * @shrink: shrink the pool.
> > > + * @sleep_mapped: whether zpool driver can sleep during map.
> >
> > I don't think it's a good idea. It just breaks zpool abstraction
> > in that it exposes internal implementation to user to avoid issue
> > zswap recently introduced. It also conflicts zpool_map_handle's
> > semantic.
> >
> > Rather than introducing another break in zpool due to the new
> > zswap feature recenlty introduced, zswap could introduce
> > CONFIG_ZSWAP_HW_COMPRESSOR. Once it's configured, zsmalloc could
> > be disabled. And with disabling CONFIG_ZSWAP_HW_COMPRESSOR, zswap
> > doesn't need to make any bounce buffer copy so that no existing
> > zsmalloc user will see performance regression.
> >
>
> I agree with Minchan. There is no reason to add extra overhead for
> configurations where there is no hardware available.
I still don't get what the suggested alternative is. How would
disabling CONFIG_ZSWAP_HW_COMPRESSOR help if zswap is using acomp API?
Best regards,
Vitaly
next prev parent reply other threads:[~2021-01-14 18:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 11:02 [RFC mm/zswap 0/2] Fix the compatibility of zsmalloc and zswap Tian Tao
2020-12-25 11:02 ` [RFC mm/zswap 1/2] mm/zswap: add the flag can_sleep_mapped Tian Tao
2021-01-14 18:28 ` Minchan Kim
2021-01-14 18:40 ` Vitaly Wool
2021-01-14 18:56 ` Minchan Kim
2021-01-14 19:05 ` Vitaly Wool
2021-01-14 19:21 ` Shakeel Butt
2021-01-14 19:23 ` Minchan Kim
2021-01-14 19:53 ` Vitaly Wool
2021-01-14 21:09 ` Shakeel Butt
2021-01-14 22:41 ` Vitaly Wool
2021-01-19 1:28 ` tiantao (H)
2021-01-14 18:43 ` Shakeel Butt
2021-01-14 18:53 ` Vitaly Wool [this message]
2021-01-21 9:17 ` Vitaly Wool
2021-01-21 23:15 ` Song Bao Hua (Barry Song)
2020-12-25 11:02 ` [RFC mm/zswap 2/2] mm: set the sleep_mapped to true for zbud and z3fold Tian Tao
2021-01-14 18:46 ` [RFC mm/zswap 0/2] Fix the compatibility of zsmalloc and zswap Vitaly Wool
2021-01-15 1:17 ` tiantao (H)
2021-01-19 1:31 ` tiantao (H)
2021-01-19 2:39 ` Mike Galbraith
2021-01-18 13:44 ` Sebastian Andrzej Siewior
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=CAM4kBBKLw5LiTqcjjcGQF3mBysvFJFs2khRjw7VRVXHNM4Pryg@mail.gmail.com \
--to=vitaly.wool@konsulko.com \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=shakeelb@google.com \
--cc=sjenning@redhat.com \
--cc=song.bao.hua@hisilicon.com \
--cc=tiantao6@hisilicon.com \
/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).