From: Minchan Kim <minchan@kernel.org>
To: Hui Zhu <teawater@gmail.com>
Cc: Hui Zhu <zhuhui@xiaomi.com>,
"ngupta@vflare.org" <ngupta@vflare.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Linux Memory Management List <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] zsmalloc: zs_page_migrate: schedule free_work if zspage is ZS_EMPTY
Date: Mon, 14 Aug 2017 18:20:17 +0900 [thread overview]
Message-ID: <20170814092017.GH26913@bbox> (raw)
In-Reply-To: <CANFwon0cB3xveRD+eqLaVXhPs9uWO+Ds+a4W8R8dPU0KH28Jfg@mail.gmail.com>
On Mon, Aug 14, 2017 at 05:11:50PM +0800, Hui Zhu wrote:
> 2017-08-14 16:31 GMT+08:00 Minchan Kim <minchan@kernel.org>:
> > Hi Hui,
> >
> > On Mon, Aug 14, 2017 at 02:34:46PM +0800, Hui Zhu wrote:
> >> After commit e2846124f9a2 ("zsmalloc: zs_page_migrate: skip unnecessary
> >> loops but not return -EBUSY if zspage is not inuse") zs_page_migrate
> >> can handle the ZS_EMPTY zspage.
> >>
> >> But it will affect the free_work free the zspage. That will make this
> >> ZS_EMPTY zspage stay in system until another zspage wake up free_work.
> >>
> >> Make this patch let zs_page_migrate wake up free_work if need.
> >>
> >> Fixes: e2846124f9a2 ("zsmalloc: zs_page_migrate: skip unnecessary loops but not return -EBUSY if zspage is not inuse")
> >> Signed-off-by: Hui Zhu <zhuhui@xiaomi.com>
> >
> > This patch makes me remind why I didn't try to migrate empty zspage
> > as you did e2846124f9a2. I have forgotten it toally.
> >
> > We cannot guarantee when the freeing of the page happens if we use
> > deferred freeing in zs_page_migrate. However, we returns
> > MIGRATEPAGE_SUCCESS which is totally lie.
> > Without instant freeing the page, it doesn't help the migration
> > situation. No?
> >
>
> Sorry I think the reason is I didn't introduce this clear.
> After I patch e2846124f9a2. I got some false in zs_page_isolate:
> if (get_zspage_inuse(zspage) == 0) {
> spin_unlock(&class->lock);
> return false;
> }
> The page of this zspage was migrated in before.
>
> So I think e2846124f9a2 is OK that MIGRATEPAGE_SUCCESS with the "page".
> But it keep the "newpage" with a empty zspage inside system.
> Root cause is zs_page_isolate remove it from ZS_EMPTY list but not
> call zs_page_putback "schedule_work(&pool->free_work);". Because
> zs_page_migrate done the job without
> "schedule_work(&pool->free_work);"
>
> That is why I made the new patch.
Thanks. Now I got it. Could you resend the patch with such detailed
information?
< snip >
> >> + if (!is_zspage_isolated(zspage)) {
> >> + /*
> >> + * The page and class is locked, we cannot free zspage
> >> + * immediately so let's defer.
Please put more words about that why we should calls schedule_work
in here.
Thanks!
> >> + */
> >> + if (putback_zspage(class, zspage) == ZS_EMPTY)
> >> + schedule_work(&pool->free_work);
> >> + }
> >>
> >> reset_page(page);
> >> put_page(page);
> >> --
> >> 1.9.1
> >>
> >> --
> >> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> >> the body to majordomo@kvack.org. For more info on Linux MM,
> >> see: http://www.linux-mm.org/ .
> >> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2017-08-14 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 6:34 [PATCH] zsmalloc: zs_page_migrate: schedule free_work if zspage is ZS_EMPTY Hui Zhu
2017-08-14 8:31 ` Minchan Kim
2017-08-14 9:11 ` Hui Zhu
2017-08-14 9:20 ` 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=20170814092017.GH26913@bbox \
--to=minchan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=teawater@gmail.com \
--cc=zhuhui@xiaomi.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).