From: Greg KH <gregkh@linuxfoundation.org>
To: zhiyuan_zhu@htc.com
Cc: vinmenon@codeaurora.org, linux-mm@kvack.org,
skhiani@codeaurora.org, torvalds@linux-foundation.org,
Jet_Li@htc.com
Subject: Re: Low memory killer problem
Date: Tue, 16 May 2017 07:56:52 +0200 [thread overview]
Message-ID: <20170516055652.GA25379@kroah.com> (raw)
In-Reply-To: <AF7C0ADF1FEABA4DABABB97411952A2EDD0A52C9@CN-MBX03.HTC.COM.TW>
On Tue, May 16, 2017 at 03:41:31AM +0000, zhiyuan_zhu@htc.com wrote:
> Thanks for your remind,
> I found lowmemorykiller.c have been removed, and ION module still exist since v4.12-rc1.
> I will pay attention to ION module.
>
> But I still have 3 questions,
> Is there any substitute for low-memory-killer after kernel v4.12-rc1 ?
See the email thread when it was removed, there was some proposals on
how to do this "correctly". I know someone at Google is currently
working on this, hopefully they have something to post soon about it.
> Can I accounted the ION free to free memory?
> Is there any different from ION free and the normal system memory free?
No idea, try asking the ION developers :)
good luck!
greg k-h
--
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-05-16 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AF7C0ADF1FEABA4DABABB97411952A2EDD0A004D@CN-MBX05.HTC.COM.TW>
2017-05-15 3:58 ` Low memory killer problem zhiyuan_zhu
2017-05-15 7:25 ` zhiyuan_zhu
2017-05-15 8:05 ` Greg KH
2017-05-15 8:22 ` zhiyuan_zhu
2017-05-15 9:00 ` Greg KH
2017-05-16 3:41 ` zhiyuan_zhu
2017-05-16 5:56 ` Greg KH [this message]
2017-05-16 22:37 ` Laura Abbott
2017-05-17 2:47 ` zhiyuan_zhu
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=20170516055652.GA25379@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Jet_Li@htc.com \
--cc=linux-mm@kvack.org \
--cc=skhiani@codeaurora.org \
--cc=torvalds@linux-foundation.org \
--cc=vinmenon@codeaurora.org \
--cc=zhiyuan_zhu@htc.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 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.