From: Sonny Rao <sonnyrao@google.com>
To: linux-mm@kvack.org
Cc: lsf-pc@lists.linuxfoundation.org,
Jesse Barnes <jsbarnes@google.com>,
Brian Geffon <bgeffon@google.com>, Vovo Yang <vovoy@google.com>,
Yu Zhao <yuzhao@google.com>, Joel Fernandes <joelaf@google.com>,
Minchan Kim <minchan@google.com>
Subject: [LFS/MM/BPF Topic] User space OOM management on Chrome OS
Date: Thu, 13 Feb 2020 17:06:17 -0800 [thread overview]
Message-ID: <CAPz6YkUci9=d-nkoN9e8pb1eO3Wgchh1GTNSNdWc3kYuvoQdBg@mail.gmail.com> (raw)
Memory management on Chrome OS - focus on userspace OOM handling
I can discuss how we try to avoid invoking the kernel OOM-killer and
share ~8 years of experience with that. I can also discuss our usage
of Zram and per-process reclaim as well.
Let me know if you guys think this would be a useful presentation, thanks.
reply other threads:[~2020-02-14 1:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAPz6YkUci9=d-nkoN9e8pb1eO3Wgchh1GTNSNdWc3kYuvoQdBg@mail.gmail.com' \
--to=sonnyrao@google.com \
--cc=bgeffon@google.com \
--cc=joelaf@google.com \
--cc=jsbarnes@google.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linuxfoundation.org \
--cc=minchan@google.com \
--cc=vovoy@google.com \
--cc=yuzhao@google.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;
as well as URLs for NNTP newsgroup(s).