From: Minchan Kim <email@example.com> To: Sergey Senozhatsky <firstname.lastname@example.org> Cc: Andrew Morton <email@example.com>, LKML <firstname.lastname@example.org>, Joey Pabalinas <email@example.com> Subject: Re: [PATCH v3 0/7] zram idle page writeback Date: Mon, 3 Dec 2018 08:20:23 +0900 [thread overview] Message-ID: <20181202232023.GB21560@google.com> (raw) In-Reply-To: <20181130043656.GC605@jagdpanzerIV> On Fri, Nov 30, 2018 at 01:36:56PM +0900, Sergey Senozhatsky wrote: > On (11/27/18 14:54), Minchan Kim wrote: > > Inherently, swap device has many idle pages which are rare touched since > > it was allocated. It is never problem if we use storage device as swap. > > However, it's just waste for zram-swap. > > > > This patchset supports zram idle page writeback feature. > > > > * Admin can define what is idle page "no access since X time ago" > > * Admin can define when zram should writeback them > > * Admin can define when zram should stop writeback to prevent wearout > > > > Detail is on each patch's description. > > > > Below first two patches are -stable material so it could go first > > separately with others in this series. > > I had some time to look at the patches > Reviewed-by: Sergey Senozhatsky <firstname.lastname@example.org> > > Will give it some testing later; next week maybe. Thanks Sergey!
next prev parent reply other threads:[~2018-12-02 23:20 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-27 5:54 Minchan Kim 2018-11-27 5:54 ` [PATCH v3 1/7] zram: fix lockdep warning of free block handling Minchan Kim 2018-11-29 2:43 ` Sergey Senozhatsky 2018-11-27 5:54 ` [PATCH v3 2/7] zram: fix double free backing device Minchan Kim 2018-11-29 2:32 ` Sergey Senozhatsky 2018-11-27 5:54 ` [PATCH v3 3/7] zram: refactoring flags and writeback stuff Minchan Kim 2018-11-27 5:54 ` [PATCH v3 4/7] zram: introduce ZRAM_IDLE flag Minchan Kim 2018-11-29 2:29 ` Sergey Senozhatsky 2018-11-27 5:54 ` [PATCH v3 5/7] zram: support idle/huge page writeback Minchan Kim 2018-11-28 23:35 ` Andrew Morton 2018-11-29 1:36 ` Minchan Kim 2018-11-27 5:54 ` [PATCH v3 6/7] zram: add bd_stat statistics Minchan Kim 2018-11-27 5:54 ` [PATCH v3 7/7] zram: writeback throttle Minchan Kim 2018-11-28 23:41 ` Andrew Morton 2018-11-29 1:55 ` Minchan Kim 2018-11-29 2:23 ` Sergey Senozhatsky 2018-12-02 23:18 ` Minchan Kim 2018-12-03 2:30 ` Sergey Senozhatsky 2018-12-03 2:41 ` Minchan Kim 2018-12-03 2:45 ` Sergey Senozhatsky 2018-11-30 4:36 ` [PATCH v3 0/7] zram idle page writeback Sergey Senozhatsky 2018-12-02 23:20 ` Minchan Kim [this message] 2018-12-02 23:28 ` Joey Pabalinas
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=20181202232023.GB21560@google.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [PATCH v3 0/7] zram idle page writeback' \ /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
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.