From: Minchan Kim <minchan@kernel.org> To: Seth Jennings <sjennings@variantweb.net> Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Sergey Senozhatsky <sergey.senozhatsky@gmail.com>, Jerome Marchand <jmarchan@redhat.com>, juno.choi@lge.com, seungho1.park@lge.com, Luigi Semenzato <semenzato@google.com>, Nitin Gupta <ngupta@vflare.org> Subject: Re: [RFC 0/3] zram memory control enhance Date: Thu, 14 Aug 2014 08:32:54 +0900 [thread overview] Message-ID: <20140813233254.GF9227@bbox> (raw) In-Reply-To: <20140813153422.GD2768@cerebellum.variantweb.net> On Wed, Aug 13, 2014 at 10:34:22AM -0500, Seth Jennings wrote: > On Tue, Aug 05, 2014 at 05:02:00PM +0900, Minchan Kim wrote: > > Notice! It's RFC. I didn't test at all but wanted to hear opinion > > during merge window when it's really busy time for Andrew so we could > > use the slack time to discuss without hurting him. ;-) > > > > Patch 1 is to move pages_allocated in zsmalloc from size_class to zs_pool > > so zs_get_total_size_bytes of zsmalloc would be faster than old. > > zs_get_total_size_bytes could be used next patches frequently. > > > > Patch 2 adds new feature which exports how many of bytes zsmalloc consumes > > during testing workload. Normally, before fixing the zram's disksize > > we have tested various workload and wanted to how many of bytes zram > > consumed. > > For it, we could poll mem_used_total of zram in userspace but the problem is > > when memory pressure is severe and heavy swap out happens suddenly then > > heavy swapin or exist while polling interval of user space is a few second, > > it could miss max memory size zram had consumed easily. > > With lack of information, user can set wrong disksize of zram so the result > > is OOM. So this patch adds max_mem_used for zram and zsmalloc supports it > > > > Patch 3 is to limit zram memory consumption. Now, zram has no bound for > > memory usage so it could consume up all of system memory. It makes system > > memory control for platform hard so I have heard the feature several time. > > > > Feedback is welcome! > > One thing you might consider doing is moving zram to use the new zpool > API. That way, when making changes that effect the zsmalloc API, > consideration for zpool, and by extension, zpool users like zswap are > also taken into account. Now, it's rather overkill for zram. > > Seth > > > > > Minchan Kim (3): > > zsmalloc: move pages_allocated to zs_pool > > zsmalloc/zram: add zs_get_max_size_bytes and use it in zram > > zram: limit memory size for zram > > > > Documentation/blockdev/zram.txt | 2 ++ > > drivers/block/zram/zram_drv.c | 58 +++++++++++++++++++++++++++++++++++++++++ > > drivers/block/zram/zram_drv.h | 1 + > > include/linux/zsmalloc.h | 1 + > > mm/zsmalloc.c | 50 +++++++++++++++++++++++++---------- > > 5 files changed, 98 insertions(+), 14 deletions(-) > > > > -- > > 2.0.0 > > > > -- > > 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> -- Kind regards, Minchan Kim
WARNING: multiple messages have this Message-ID (diff)
From: Minchan Kim <minchan@kernel.org> To: Seth Jennings <sjennings@variantweb.net> Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, Sergey Senozhatsky <sergey.senozhatsky@gmail.com>, Jerome Marchand <jmarchan@redhat.com>, juno.choi@lge.com, seungho1.park@lge.com, Luigi Semenzato <semenzato@google.com>, Nitin Gupta <ngupta@vflare.org> Subject: Re: [RFC 0/3] zram memory control enhance Date: Thu, 14 Aug 2014 08:32:54 +0900 [thread overview] Message-ID: <20140813233254.GF9227@bbox> (raw) In-Reply-To: <20140813153422.GD2768@cerebellum.variantweb.net> On Wed, Aug 13, 2014 at 10:34:22AM -0500, Seth Jennings wrote: > On Tue, Aug 05, 2014 at 05:02:00PM +0900, Minchan Kim wrote: > > Notice! It's RFC. I didn't test at all but wanted to hear opinion > > during merge window when it's really busy time for Andrew so we could > > use the slack time to discuss without hurting him. ;-) > > > > Patch 1 is to move pages_allocated in zsmalloc from size_class to zs_pool > > so zs_get_total_size_bytes of zsmalloc would be faster than old. > > zs_get_total_size_bytes could be used next patches frequently. > > > > Patch 2 adds new feature which exports how many of bytes zsmalloc consumes > > during testing workload. Normally, before fixing the zram's disksize > > we have tested various workload and wanted to how many of bytes zram > > consumed. > > For it, we could poll mem_used_total of zram in userspace but the problem is > > when memory pressure is severe and heavy swap out happens suddenly then > > heavy swapin or exist while polling interval of user space is a few second, > > it could miss max memory size zram had consumed easily. > > With lack of information, user can set wrong disksize of zram so the result > > is OOM. So this patch adds max_mem_used for zram and zsmalloc supports it > > > > Patch 3 is to limit zram memory consumption. Now, zram has no bound for > > memory usage so it could consume up all of system memory. It makes system > > memory control for platform hard so I have heard the feature several time. > > > > Feedback is welcome! > > One thing you might consider doing is moving zram to use the new zpool > API. That way, when making changes that effect the zsmalloc API, > consideration for zpool, and by extension, zpool users like zswap are > also taken into account. Now, it's rather overkill for zram. > > Seth > > > > > Minchan Kim (3): > > zsmalloc: move pages_allocated to zs_pool > > zsmalloc/zram: add zs_get_max_size_bytes and use it in zram > > zram: limit memory size for zram > > > > Documentation/blockdev/zram.txt | 2 ++ > > drivers/block/zram/zram_drv.c | 58 +++++++++++++++++++++++++++++++++++++++++ > > drivers/block/zram/zram_drv.h | 1 + > > include/linux/zsmalloc.h | 1 + > > mm/zsmalloc.c | 50 +++++++++++++++++++++++++---------- > > 5 files changed, 98 insertions(+), 14 deletions(-) > > > > -- > > 2.0.0 > > > > -- > > 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> -- Kind regards, Minchan Kim -- 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>
next prev parent reply other threads:[~2014-08-13 23:32 UTC|newest] Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-05 8:02 [RFC 0/3] zram memory control enhance Minchan Kim 2014-08-05 8:02 ` Minchan Kim 2014-08-05 8:02 ` [RFC 1/3] zsmalloc: move pages_allocated to zs_pool Minchan Kim 2014-08-05 8:02 ` Minchan Kim 2014-08-13 13:59 ` Dan Streetman 2014-08-13 13:59 ` Dan Streetman 2014-08-13 14:14 ` Sergey Senozhatsky 2014-08-13 14:14 ` Sergey Senozhatsky 2014-08-13 14:51 ` Dan Streetman 2014-08-13 14:51 ` Dan Streetman 2014-08-13 15:13 ` Sergey Senozhatsky 2014-08-13 15:13 ` Sergey Senozhatsky 2014-08-13 15:25 ` Sergey Senozhatsky 2014-08-13 15:25 ` Sergey Senozhatsky 2014-08-13 16:11 ` Dan Streetman 2014-08-13 16:11 ` Dan Streetman 2014-08-14 13:03 ` Sergey Senozhatsky 2014-08-14 13:03 ` Sergey Senozhatsky 2014-08-14 0:09 ` Minchan Kim 2014-08-14 0:09 ` Minchan Kim 2014-08-13 15:21 ` Seth Jennings 2014-08-13 15:21 ` Seth Jennings 2014-08-05 8:02 ` [RFC 2/3] zsmalloc/zram: add zs_get_max_size_bytes and use it in zram Minchan Kim 2014-08-05 8:02 ` Minchan Kim 2014-08-13 15:25 ` Seth Jennings 2014-08-13 15:25 ` Seth Jennings 2014-08-05 8:02 ` [RFC 3/3] zram: limit memory size for zram Minchan Kim 2014-08-05 8:02 ` Minchan Kim 2014-08-05 9:48 ` Minchan Kim 2014-08-05 9:48 ` Minchan Kim 2014-08-05 13:16 ` Sergey Senozhatsky 2014-08-05 13:16 ` Sergey Senozhatsky 2014-08-06 6:52 ` Minchan Kim 2014-08-06 6:52 ` Minchan Kim 2014-08-13 15:30 ` Seth Jennings 2014-08-13 15:30 ` Seth Jennings 2014-08-13 23:31 ` Minchan Kim 2014-08-13 23:31 ` Minchan Kim 2014-08-13 23:27 ` Minchan Kim 2014-08-13 23:27 ` Minchan Kim 2014-08-14 13:29 ` Sergey Senozhatsky 2014-08-14 13:29 ` Sergey Senozhatsky 2014-08-17 23:32 ` Minchan Kim 2014-08-17 23:32 ` Minchan Kim 2014-08-14 14:45 ` Dan Streetman 2014-08-14 14:45 ` Dan Streetman 2014-08-06 12:54 ` [RFC 0/3] zram memory control enhance Jerome Marchand 2014-08-13 15:34 ` Seth Jennings 2014-08-13 15:34 ` Seth Jennings 2014-08-13 23:32 ` Minchan Kim [this message] 2014-08-13 23:32 ` 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=20140813233254.GF9227@bbox \ --to=minchan@kernel.org \ --cc=jmarchan@redhat.com \ --cc=juno.choi@lge.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=ngupta@vflare.org \ --cc=semenzato@google.com \ --cc=sergey.senozhatsky@gmail.com \ --cc=seungho1.park@lge.com \ --cc=sjennings@variantweb.net \ /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: linkBe 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.