From: Hugh Dickins <hughd@google.com>
To: David Rientjes <rientjes@google.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Mel Gorman <mgorman@techsingularity.net>,
Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>,
Jonathan Corbet <corbet@lwn.net>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch] mm, thp: add new background defrag option
Date: Mon, 9 Jan 2017 19:38:31 -0800 (PST) [thread overview]
Message-ID: <alpine.LSU.2.11.1701091925170.2692@eggly.anvils> (raw)
In-Reply-To: <alpine.DEB.2.10.1701091818340.61862@chino.kir.corp.google.com>
On Mon, 9 Jan 2017, David Rientjes wrote:
> On Mon, 9 Jan 2017, Vlastimil Babka wrote:
>
> > > Any suggestions for a better name for "background" are more than welcome.
> >
> > Why not just "madvise+defer"?
> >
>
> Seeing no other activity regarding this issue (omg!), I'll wait a day or
> so to see if there are any objections to "madvise+defer" or suggestions
> that may be better and repost.
I get very confused by the /sys/kernel/mm/transparent_hugepage/defrag
versus enabled flags, and this may be a terrible, even more confusing,
idea: but I've been surprised and sad to see defrag with a "defer"
option, but poor enabled without one; and it has crossed my mind that
perhaps the peculiar "madvise+defer" syntax in defrag might rather be
handled by "madvise" in defrag with "defer" in enabled? Or something
like that: 4 x 4 possibilities instead of 5 x 3.
Please be gentle with me,
Hugh
--
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:[~2017-01-10 3:38 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 23:41 David Rientjes
2017-01-05 10:13 ` Mel Gorman
2017-01-05 10:33 ` Michal Hocko
2017-01-05 13:58 ` Vlastimil Babka
2017-01-05 15:50 ` Michal Hocko
2017-01-05 22:54 ` David Rientjes
2017-01-06 8:41 ` Vlastimil Babka
2017-01-06 14:01 ` Michal Hocko
2017-01-06 22:20 ` David Rientjes
2017-01-09 10:04 ` Vlastimil Babka
2017-01-09 12:06 ` Vlastimil Babka
2017-01-10 2:19 ` David Rientjes
2017-01-10 3:38 ` Hugh Dickins [this message]
2017-01-10 8:44 ` Vlastimil Babka
2017-01-10 23:52 ` David Rientjes
2017-01-10 13:01 ` Michal Hocko
2017-01-11 0:15 ` [patch v2] mm, thp: add new defer+madvise " David Rientjes
2017-01-11 7:35 ` Vlastimil Babka
2017-01-12 8:01 ` Michal Hocko
2017-01-11 8:56 ` Mel Gorman
2017-01-12 0:16 ` Andrew Morton
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=alpine.LSU.2.11.1701091925170.2692@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
/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