From: Mike Galbraith <efault@gmx.de>
To: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
Cc: Ferry Toth <ftoth@telfort.nl>, linux-kernel@vger.kernel.org
Subject: Re: DOS by unprivileged user
Date: Wed, 25 Apr 2018 18:21:13 +0200 [thread overview]
Message-ID: <1524673273.8257.2.camel@gmx.de> (raw)
In-Reply-To: <20180425155459.5a4e40e0@alans-desktop>
On Wed, 2018-04-25 at 15:54 +0100, Alan Cox wrote:
> > > I think memory allocation and io waits can't be decoupled from
> > > scheduling as they are now.
> >
> > The scheduler is not decoupled from either, it is intimately involved
> > in both. However, none of the decision making smarts for either reside
> > in the scheduler, nor should they.
>
> It belongs in both.
If mm decision making belongs within the process scheduler, it follows
that IO requests, dirty page writeback etc. do as well. Nope, I don't
think we want to create a squid-uler, with tentacles extending all over
the dang kernel.
The thrashing problem could use some attention, but we'll have to agree
to disagree about the scheduler growing mm, io (etc) smarts.
-Mike
next prev parent reply other threads:[~2018-04-25 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 19:13 DOS by unprivileged user Ferry Toth
2018-04-20 4:46 ` Mike Galbraith
2018-04-20 8:39 ` Ferry Toth
2018-04-20 12:37 ` Mike Galbraith
2018-04-22 10:16 ` Pavel Machek
2018-04-22 17:43 ` vcaputo
2018-04-23 0:27 ` Michal Hocko
2018-04-23 7:13 ` Pavel Machek
[not found] ` <4285098.DEWjdbWF2X@delfion>
[not found] ` <1524325275.8078.2.camel@gmx.de>
[not found] ` <6057755.ozdVOybsI6@delfion>
2018-04-23 8:04 ` Mike Galbraith
2018-04-25 14:54 ` Alan Cox
2018-04-25 16:21 ` Mike Galbraith [this message]
2018-04-25 16:50 ` Mike Galbraith
2018-04-30 10:00 ` Ferry Toth
2018-04-30 10:35 ` Miguel Ojeda
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=1524673273.8257.2.camel@gmx.de \
--to=efault@gmx.de \
--cc=ftoth@telfort.nl \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.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 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.