From: Chris Murphy <lists@colorremedies.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Chris Murphy <lists@colorremedies.com>,
Matthew Wilcox <willy@infradead.org>,
lsf-pc@lists.linux-foundation.org,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
linux-mm@kvack.org, Mel Gorman <mgorman@suse.de>
Subject: Re: [Lsf-pc] [LSF/MM TOPIC] Congestion
Date: Tue, 7 Jan 2020 13:12:13 -0700 [thread overview]
Message-ID: <CAJCQCtRqswrUC=kmdL0rKi6802qAxxyxOAQm7JHkAVQgK0GmWg@mail.gmail.com> (raw)
In-Reply-To: <20200107115345.GG32178@dhcp22.suse.cz>
On Tue, Jan 7, 2020 at 4:53 AM Michal Hocko <mhocko@kernel.org> wrote:
>
> On Tue 07-01-20 01:23:38, Chris Murphy wrote:
> > More helpful
> > would be, what should distributions be doing better to avoid the
> > problem in the first place? User space oom daemons are now popular,
> > and there's talk about avoiding swap thrashing and oom by strict use
> > of cgroupsv2 and PSI. Some people say, oh yeah duh, just don't make a
> > swap device at all, what are you crazy? Then there's swap on ZRAM. And
> > alas zswap too. So what's actually recommended to help with this
> > problem?
>
> I believe this will be workload specific and it is always appreciated to
> report the behavior as mentioned above.
I'll do so in a separate email. But by what mechanism is workload
determined or categorized? And how is the system dynamically
reconfigured to better handle different workloads? These are general
purpose operating systems, of course a user has different workloads
from moment to moment.
--
Chris Murphy
next prev parent reply other threads:[~2020-01-07 20:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 12:59 [LSF/MM TOPIC] Congestion Matthew Wilcox
2020-01-04 9:09 ` Dave Chinner
2020-01-06 11:55 ` [Lsf-pc] " Michal Hocko
2020-01-06 23:21 ` Dave Chinner
2020-01-07 8:23 ` Chris Murphy
2020-01-07 11:53 ` Michal Hocko
2020-01-07 20:12 ` Chris Murphy [this message]
2020-01-07 11:53 ` Michal Hocko
2020-01-09 11:07 ` Jan Kara
2020-01-09 23:00 ` Dave Chinner
2020-02-05 16:05 ` Mel Gorman
2020-02-06 23:19 ` Dave Chinner
2020-02-07 0:08 ` Matthew Wilcox
2020-02-13 3:18 ` Andrew Morton
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='CAJCQCtRqswrUC=kmdL0rKi6802qAxxyxOAQm7JHkAVQgK0GmWg@mail.gmail.com' \
--to=lists@colorremedies.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).