From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH v7 11/12] zsmalloc: page migration support
Date: Thu, 2 Jun 2016 09:15:10 +0900 [thread overview]
Message-ID: <20160602001510.GA1736@bbox> (raw)
In-Reply-To: <20160601143936.a7ad8eec093514e3ee54cc62@linux-foundation.org>
On Wed, Jun 01, 2016 at 02:39:36PM -0700, Andrew Morton wrote:
> On Wed, 1 Jun 2016 08:21:20 +0900 Minchan Kim <minchan@kernel.org> wrote:
>
> > This patch introduces run-time migration feature for zspage.
> >
> > ...
> >
> > +static void kick_deferred_free(struct zs_pool *pool)
> > +{
> > + schedule_work(&pool->free_work);
> > +}
>
> When CONFIG_ZSMALLOC=m, what keeps all the data structures in place
> during a concurrent rmmod?
>
The most of data structure in zram start to work by user calling
zs_create_pool and user of zsmalloc should call zs_destroy_pool
before trying doing rmmod where zs_unregister_migration does
flush_work(&pool->free_work).
If I miss something, please let me know it.
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: [PATCH v7 11/12] zsmalloc: page migration support
Date: Thu, 2 Jun 2016 09:15:10 +0900 [thread overview]
Message-ID: <20160602001510.GA1736@bbox> (raw)
In-Reply-To: <20160601143936.a7ad8eec093514e3ee54cc62@linux-foundation.org>
On Wed, Jun 01, 2016 at 02:39:36PM -0700, Andrew Morton wrote:
> On Wed, 1 Jun 2016 08:21:20 +0900 Minchan Kim <minchan@kernel.org> wrote:
>
> > This patch introduces run-time migration feature for zspage.
> >
> > ...
> >
> > +static void kick_deferred_free(struct zs_pool *pool)
> > +{
> > + schedule_work(&pool->free_work);
> > +}
>
> When CONFIG_ZSMALLOC=m, what keeps all the data structures in place
> during a concurrent rmmod?
>
The most of data structure in zram start to work by user calling
zs_create_pool and user of zsmalloc should call zs_destroy_pool
before trying doing rmmod where zs_unregister_migration does
flush_work(&pool->free_work).
If I miss something, please let me know it.
next prev parent reply other threads:[~2016-06-02 0:14 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 23:21 [PATCH v7 00/12] Support non-lru page migration Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 01/12] mm: use put_page to free page instead of putback_lru_page Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 02/12] mm: migrate: support non-lru movable page migration Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 03/12] mm: balloon: use general non-lru movable page feature Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 04/12] zsmalloc: keep max_object in size_class Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 05/12] zsmalloc: use bit_spin_lock Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 06/12] zsmalloc: use accessor Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 07/12] zsmalloc: factor page chain functionality out Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 08/12] zsmalloc: introduce zspage structure Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 09/12] zsmalloc: separate free_zspage from putback_zspage Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 10/12] zsmalloc: use freeobj for index Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 11/12] zsmalloc: page migration support Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-06-01 14:09 ` Vlastimil Babka
2016-06-01 14:09 ` Vlastimil Babka
2016-06-02 0:25 ` Minchan Kim
2016-06-02 0:25 ` Minchan Kim
2016-06-02 11:44 ` Vlastimil Babka
2016-06-02 11:44 ` Vlastimil Babka
2016-06-01 21:39 ` Andrew Morton
2016-06-01 21:39 ` Andrew Morton
2016-06-02 0:15 ` Minchan Kim [this message]
2016-06-02 0:15 ` Minchan Kim
2017-01-19 0:13 ` Chulmin Kim
2017-01-19 2:44 ` Minchan Kim
2017-01-19 3:39 ` Chulmin Kim
2017-01-19 6:21 ` Minchan Kim
2017-01-19 8:16 ` Chulmin Kim
2017-01-23 5:22 ` Minchan Kim
2017-01-23 5:30 ` Sergey Senozhatsky
2017-01-23 5:40 ` Minchan Kim
2017-01-25 4:06 ` Chulmin Kim
2017-01-25 4:25 ` Sergey Senozhatsky
2017-01-25 5:26 ` Minchan Kim
2017-01-26 17:04 ` Dan Streetman
2017-01-31 0:10 ` Minchan Kim
2017-01-31 13:09 ` Dan Streetman
2017-02-01 6:51 ` Minchan Kim
2017-02-01 19:38 ` Dan Streetman
2017-02-02 8:48 ` Minchan Kim
2016-05-31 23:21 ` [PATCH v7 12/12] zram: use __GFP_MOVABLE for memory allocation Minchan Kim
2016-05-31 23:21 ` Minchan Kim
2016-06-01 21:41 ` [PATCH v7 00/12] Support non-lru page migration Andrew Morton
2016-06-01 21:41 ` Andrew Morton
2016-06-01 22:40 ` Daniel Vetter
2016-06-01 22:40 ` Daniel Vetter
2016-06-01 22:40 ` Daniel Vetter
2016-06-02 0:36 ` Minchan Kim
2016-06-02 0:36 ` Minchan Kim
2016-06-02 0:36 ` Minchan Kim
2016-06-01 21:41 ` Andrew Morton
2016-06-15 7:59 ` Sergey Senozhatsky
2016-06-15 7:59 ` Sergey Senozhatsky
2016-06-15 7:59 ` Sergey Senozhatsky
2016-06-15 23:12 ` Minchan Kim
2016-06-15 23:12 ` Minchan Kim
2016-06-16 2:48 ` Sergey Senozhatsky
2016-06-16 2:48 ` Sergey Senozhatsky
2016-06-16 2:48 ` Sergey Senozhatsky
2016-06-16 2:58 ` Minchan Kim
2016-06-16 2:58 ` Minchan Kim
2016-06-16 2:58 ` Minchan Kim
2016-06-16 4:23 ` Sergey Senozhatsky
2016-06-16 4:23 ` Sergey Senozhatsky
2016-06-16 4:47 ` Minchan Kim
2016-06-16 4:47 ` Minchan Kim
2016-06-16 5:22 ` Sergey Senozhatsky
2016-06-16 5:22 ` Sergey Senozhatsky
2016-06-16 6:47 ` Minchan Kim
2016-06-16 6:47 ` Minchan Kim
2016-06-16 6:47 ` Minchan Kim
2016-06-16 8:42 ` Sergey Senozhatsky
2016-06-16 8:42 ` Sergey Senozhatsky
2016-06-16 8:42 ` Sergey Senozhatsky
2016-06-16 10:09 ` Minchan Kim
2016-06-16 10:09 ` Minchan Kim
2016-06-17 7:28 ` Joonsoo Kim
2016-06-17 7:28 ` Joonsoo Kim
2016-06-17 7:28 ` Joonsoo Kim
2016-06-16 10:09 ` Minchan Kim
2016-06-16 5:22 ` Sergey Senozhatsky
2016-06-16 4:47 ` Minchan Kim
2016-06-16 4:23 ` Sergey Senozhatsky
2016-06-15 23:12 ` Minchan Kim
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=20160602001510.GA1736@bbox \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=sergey.senozhatsky@gmail.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 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.