From: Michal Hocko <mhocko@kernel.org>
To: lsf-pc@lists.linux-foundation.org
Cc: linux-mm@kvack.org, Johannes Weiner <hannes@cmpxchg.org>,
Tim Chen <tim.c.chen@linux.intel.com>
Subject: [LSF/MM TOPIC] plans for future swap changes
Date: Wed, 28 Dec 2016 15:57:32 +0100 [thread overview]
Message-ID: <20161228145732.GE11470@dhcp22.suse.cz> (raw)
This is something I would be interested to discuss even though I am not
working on it directly. Sorry if I hijacked the topic from those who
planned to post them.
It seems that the time to reconsider our approach to the swap storage is
come already and there are multiple areas to discuss. I would be
interested at least in the following
1) anon/file balancing. Johannes has posted some work already and I am
really interested in the future plans for it.
2) swap trashing detection is something that we are lacking for a long
time and it would be great if we could do something to help
situations when the machine is effectively out of memory but still
hopelessly trying to swap in and out few pages while the machine is
basically unusable. I hope that 1) will give us some bases but I am
not sure how much we will need on top.
3) optimizations for the swap out paths - Tim Chen and other guys from
Intel are already working on this. I didn't get time to review this
closely - mostly because I am not closely familiar with the swapout
code and it takes quite some time to get into all subtle details.
I mainly interested in what are the plans in this area and how they
should be coordinated with other swap related changes
4) Do we want the native THP swap in/out support?
Other plans?
--
Michal Hocko
SUSE Labs
--
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 reply other threads:[~2016-12-28 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-28 14:57 Michal Hocko [this message]
2017-01-04 6:40 ` Johannes Weiner
2017-01-04 17:16 ` Tim Chen
2017-01-04 18:13 ` Shaohua Li
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=20161228145732.GE11470@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=tim.c.chen@linux.intel.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