{"push_id":1213458978,"size":3,"distinct_size":3,"ref":"refs/heads/test","head":"45050e3c10288d2f70b1acddd94bc806e2c11a1e","before":"e4764abdb778a7c40538e836dc920c41f2b9e66b","commits":[{"sha":"7cb3674b8c63db6ee97034858f42cf00b36e298d","author":{"name":"Minchan Kim","email":"513909c15f9d22f3704dca2f86978b287731f351@kernel.org"},"message":"UPSTREAM: zram: zram memory size limitation\n\n(cherry-pick from commit 9ada9da9573f3460b156b7755c093e30b258eacb)\n\nSince zram has no control feature to limit memory usage, it makes hard to\nmanage system memrory.\n\nThis patch adds new knob \"mem_limit\" via sysfs to set up the a limit so\nthat zram could fail allocation once it reaches the limit.\n\nIn addition, user could change the limit in runtime so that he could\nmanage the memory more dynamically.\n\nInitial state is no limit so it doesn't break old behavior.\n\nBug: 25951511\n\nChange-Id: I306a9582a9273c521d90b607a3ba2b44860a6273\n[akpm@linux-foundation.org: fix typo, per Sergey]\nSigned-off-by: Minchan Kim <minchan@kernel.org>\nCc: Dan Streetman <ddstreet@ieee.org>\nCc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Jerome Marchand <jmarchan@redhat.com>\nCc: <juno.choi@lge.com>\nCc: <seungho1.park@lge.com>\nCc: Luigi Semenzato <semenzato@google.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: Seth Jennings <sjennings@variantweb.net>\nCc: David Horner <ds2horner@gmail.com>\nCc: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nCc: Minchan Kim <minchan@kernel.org>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/z3kernel/commits/7cb3674b8c63db6ee97034858f42cf00b36e298d"},{"sha":"1039364b0e871e5b5bf8bf93322105c3f9c70206","author":{"name":"Minchan Kim","email":"513909c15f9d22f3704dca2f86978b287731f351@kernel.org"},"message":"UPSTREAM: zram: report maximum used memory\n\n(cherry-pick from commit 461a8eee6af3b55745be64bea403ed0b743563cf)\n\nNormally, zram user could get maximum memory usage zram consumed via\npolling mem_used_total with sysfs in userspace.\n\nBut it has a critical problem because user can miss peak memory usage\nduring update inverval of polling.  For avoiding that, user should poll it\nwith shorter interval(ie, 0.0000000001s) with mlocking to avoid page fault\ndelay when memory pressure is heavy.  It would be troublesome.\n\nThis patch adds new knob \"mem_used_max\" so user could see the maximum\nmemory usage easily via reading the knob and reset it via \"echo 0 >\n/sys/block/zram0/mem_used_max\".\n\nBug: 25951511\n\nChange-Id: I117b162ce92f1601b2ad2af86ab205c6c9ca6769\nSigned-off-by: Minchan Kim <minchan@kernel.org>\nReviewed-by: Dan Streetman <ddstreet@ieee.org>\nCc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nCc: Jerome Marchand <jmarchan@redhat.com>\nCc: <juno.choi@lge.com>\nCc: <seungho1.park@lge.com>\nCc: Luigi Semenzato <semenzato@google.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: Seth Jennings <sjennings@variantweb.net>\nReviewed-by: David Horner <ds2horner@gmail.com>\nCc: Joonsoo Kim <iamjoonsoo.kim@lge.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/z3kernel/commits/1039364b0e871e5b5bf8bf93322105c3f9c70206"},{"sha":"45050e3c10288d2f70b1acddd94bc806e2c11a1e","author":{"name":"Sergey Senozhatsky","email":"9251ceca1068cc8334161fa91b1f6065a5ee8fa4@gmail.com"},"message":"UPSTREAM: zram: use notify_free to account all free notifications\n\n(cherry-pick from commit 015254daf1753003c19c46b90ee85a963260d270)\n\n`notify_free' device attribute accounts the number of slot free\nnotifications and internally represents the number of zram_free_page()\ncalls.  Slot free notifications are sent only when device is used as a\nswap device, hence `notify_free' is used only for swap devices.  Since\nf4659d8e620d08 (zram: support REQ_DISCARD) ZRAM handles yet another one\nfree notification (also via zram_free_page() call) -- REQ_DISCARD\nrequests, which are sent by a filesystem, whenever some data blocks are\ndiscarded.  However, there is no way to know the number of notifications\nin the latter case.\n\nUse `notify_free' to account the number of pages freed by\nzram_bio_discard() and zram_slot_free_notify().  Depending on usage\nscenario `notify_free' represents:\n\n a) the number of pages freed because of slot free notifications, which is\n   equal to the number of swap_slot_free_notify() calls, so there is no\n   behaviour change\n\n b) the number of pages freed because of REQ_DISCARD notifications\n\nBug: 25951511\n\nChange-Id: Ib0f93a89c388de1f23ffecf38fdf4e7218d4c6dc\nSigned-off-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nAcked-by: Minchan Kim <minchan@kernel.org>\nAcked-by: Jerome Marchand <jmarchan@redhat.com>\nCc: Nitin Gupta <ngupta@vflare.org>\nCc: Chao Yu <chao2.yu@samsung.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/tunturn/z3kernel/commits/45050e3c10288d2f70b1acddd94bc806e2c11a1e"}]}
{"actor":{"display_login":"tunturn"}}