From: Dan Magenheimer <dan.magenheimer@oracle.com>
To: Hugh Dickins <hughd@google.com>
Cc: Minchan Kim <minchan@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Nitin Gupta <ngupta@vflare.org>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Shaohua Li <shli@kernel.org>,
Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Bob Liu <bob.liu@oracle.com>
Subject: RE: [RFC] mm: remove swapcache page early
Date: Thu, 28 Mar 2013 10:35:52 -0700 (PDT) [thread overview]
Message-ID: <125abdf8-0af9-447b-8782-68acf1c9c229@default> (raw)
In-Reply-To: <alpine.LNX.2.00.1303271541200.30535@eggly.anvils>
> From: Hugh Dickins [mailto:hughd@google.com]
> Subject: RE: [RFC] mm: remove swapcache page early
>
> On Wed, 27 Mar 2013, Dan Magenheimer wrote:
> > > From: Hugh Dickins [mailto:hughd@google.com]
> > > Subject: Re: [RFC] mm: remove swapcache page early
> > >
> > The issue you are raising
> > here is (2). You may not know that (2) has recently been solved
> > in frontswap, at least for zcache. See frontswap_exclusive_gets_enabled.
> > If this is enabled (and it is for zcache but not yet for zswap),
> > what you suggest (SetPageDirty) is what happens.
>
> Ah, and I have a dim, perhaps mistaken, memory that I gave you
> input on that before, suggesting the SetPageDirty. Good, sounds
> like the solution is already in place, if not actually activated.
>
> Thanks, must dash,
> Hugh
Hi Hugh --
Credit where it is due... Yes, I do recall now that the idea
was originally yours. It went on a to-do list where I eventually
tried it and it worked... I'm sorry I had forgotten and neglected
to give you credit!
(BTW, it is activated for zcache in 3.9.)
Thanks,
Dan
--
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:[~2013-03-28 17:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 2:22 [RFC] mm: remove swapcache page early Minchan Kim
2013-03-27 5:03 ` Kyungmin Park
2013-03-27 5:15 ` Kamezawa Hiroyuki
2013-03-27 7:05 ` Minchan Kim
2013-03-27 17:19 ` Seth Jennings
2013-03-28 1:36 ` Minchan Kim
2013-03-27 21:41 ` Hugh Dickins
2013-03-27 22:24 ` Dan Magenheimer
2013-03-27 23:16 ` Hugh Dickins
2013-03-28 1:18 ` Minchan Kim
2013-03-28 1:54 ` Shaohua Li
2013-03-28 17:35 ` Dan Magenheimer [this message]
2013-03-28 1:07 ` Minchan Kim
2013-03-28 18:19 ` Dan Magenheimer
2013-03-29 1:18 ` Minchan Kim
2013-03-29 20:01 ` Hugh Dickins
2013-04-02 2:04 ` Minchan Kim
2013-04-02 5:13 ` Hugh Dickins
2013-04-02 5:56 ` Minchan Kim
2013-03-28 0:36 ` Minchan Kim
2013-04-02 13:40 ` Simon Jeons
2013-04-07 7:26 ` Simon Jeons
2013-04-08 1:48 ` Minchan Kim
2013-04-08 1:51 ` Simon Jeons
[not found] <<1364350932-12853-1-git-send-email-minchan@kernel.org>
2013-03-27 21:20 ` Dan Magenheimer
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=125abdf8-0af9-447b-8782-68acf1c9c229@default \
--to=dan.magenheimer@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=shli@kernel.org \
--cc=sjenning@linux.vnet.ibm.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).