linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: <zhiyuan_zhu@htc.com>
To: gregkh@linuxfoundation.org
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 03:41:31 +0000	[thread overview]
Message-ID: <AF7C0ADF1FEABA4DABABB97411952A2EDD0A52C9@CN-MBX03.HTC.COM.TW> (raw)
In-Reply-To: <20170515090027.GA18167@kroah.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1887 bytes --]

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 ?
Can I accounted the ION free to free memory?
Is there any different from ION free and the normal system memory free?

ION free means:   IonTotal - IonInUse  - ION reserved memory.
Thanks a lot.

-----Original Message-----
From: Greg KH [mailto:gregkh@linuxfoundation.org] 
Sent: Monday, May 15, 2017 5:00 PM
To: Zhiyuan Zhu(朱志遠)
Cc: vinmenon@codeaurora.org; linux-mm@kvack.org; skhiani@codeaurora.org; torvalds@linux-foundation.org; Jet Li(李發傑)
Subject: Re: Low memory killer problem

On Mon, May 15, 2017 at 08:22:38AM +0000, zhiyuan_zhu@htc.com wrote:
> Dear Greg,
> 
> Very sorry my mail history is lost.
> 
> I found a part of ION memory will be return to system in android 
> platform, But these memorys  can’t accounted in low-memory-killer strategy.
> …
> And I also found ION memory comes from,  kmalloc/vmalloc/alloc pages/reserved memory.
> I understand reserved memory shouldn't accounted to free memory.
> But the memory which alloced by kmalloc/vmalloc/alloc pages, can be reclaimed.
> 
> But the low-memory killer can't accounted this part, Many thanks.
> 
> Code location, 
>    ---> drivers/staging/android/lowmemorykiller.c   -> lowmem_scan

That file is gone from the latest kernel release, sorry.  So there's not much we can do about this code anymore.

See the mailing list archives for what should be used instead of this code, there is a plan for what to do.

Also note that the ION code has had a lot of reworks lately as well.

good luck!

greg k-h

N‹§²æìr¸›zǧu©ž²Æ {\b­†éì¹»\x1c®&Þ–)îÆi¢žØ^n‡r¶‰šŽŠÝ¢j$½§$¢¸\x05¢¹¨­è§~Š'.)îÄÃ,yèm¶ŸÿÃ\f%Š{±šj+ƒðèž×¦j)Z†·Ÿ

  reply	other threads:[~2017-05-16  3:41 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 ` 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 [this message]
2017-05-16  5:56           ` Greg KH
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=AF7C0ADF1FEABA4DABABB97411952A2EDD0A52C9@CN-MBX03.HTC.COM.TW \
    --to=zhiyuan_zhu@htc.com \
    --cc=Jet_Li@htc.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-mm@kvack.org \
    --cc=skhiani@codeaurora.org \
    --cc=torvalds@linux-foundation.org \
    --cc=vinmenon@codeaurora.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