From: "Christian König" <christian.koenig@amd.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: "He, Roger" <Hongbo.He@amd.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] mm/swap: add function get_total_swap_pages to expose total_swap_pages
Date: Tue, 30 Jan 2018 13:52:16 +0100 [thread overview]
Message-ID: <5ac13913-783d-26aa-ea5f-ab375f450f4c@amd.com> (raw)
In-Reply-To: <20180130122853.GC21609@dhcp22.suse.cz>
Am 30.01.2018 um 13:28 schrieb Michal Hocko:
> I do think you should completely ignore the size of the swap space. IMHO
> you should forbid further allocations when your current buffer storage
> cannot be reclaimed. So you need some form of feedback mechanism that
> would tell you: "Your buffers have grown too much".
Yeah well, that is exactly what we are trying to do here.
> If you cannot do
> that then simply assume that you cannot swap at all rather than rely on
> having some portion of it for yourself. There are many other users of
> memory outside of your subsystem. Any scaling based on the 50% of resource
> belonging to me is simply broken.
Our intention is not reserve 50% of resources to TTM, but rather allow
TTM to abort when more than 50% of all resources are used up.
Rogers initial implementation didn't looked like that, but that is just
a minor mistake we can fix.
Regards,
Christian.
--
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:[~2018-01-30 12:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 8:29 Roger He
2018-01-29 16:31 ` Michal Hocko
2018-01-30 2:56 ` He, Roger
2018-01-30 5:13 ` He, Roger
2018-01-30 7:55 ` Michal Hocko
2018-01-30 9:00 ` Christian König
2018-01-30 10:18 ` Michal Hocko
2018-01-30 10:32 ` Christian König
2018-01-30 12:28 ` Michal Hocko
2018-01-30 12:52 ` Christian König [this message]
2018-01-31 5:52 ` He, Roger
2018-02-01 6:13 ` He, Roger
2018-02-01 8:15 ` Michal Hocko
2018-01-31 7:15 ` Chunming Zhou
2018-01-31 8:08 ` He, Roger
2018-01-31 8:12 ` Christian König
2018-01-31 8:52 ` Chunming Zhou
2018-02-01 5:48 ` He, Roger
2018-02-01 8:03 ` He, Roger
2018-02-02 6:57 ` He, Roger
2018-02-02 7:46 ` Christian König
2018-02-02 7:54 ` He, Roger
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=5ac13913-783d-26aa-ea5f-ab375f450f4c@amd.com \
--to=christian.koenig@amd.com \
--cc=Hongbo.He@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
/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