From: Andrew Morton <akpm@osdl.org>
To: Rik van Riel <riel@redhat.com>
Cc: davidsen@tmr.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RSS ulimit enforcement for 2.6.8
Date: Thu, 5 Aug 2004 14:20:19 -0700 [thread overview]
Message-ID: <20040805142019.712c678a.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0408051647440.8229-100000@dhcp83-102.boston.redhat.com>
Rik van Riel <riel@redhat.com> wrote:
>
> On Thu, 5 Aug 2004, Bill Davidsen wrote:
> > Rik van Riel wrote:
> > > The patch below implements RSS ulimit enforcement for 2.6.8-rc3-mm1.
>
> > Wish there was something like RSS for cache, so that one process reading
> > every inode on the planet, or doing an md5 on an 11GB file wouldn't push
> > every damn process out if it's waiting for me to finish typing a line...
>
> I guess that's beyond the scope of a simple patch
It might not be. We could come up with some dopey per-process flag,
inherited across fork which means "invalidate each file's pagecache when I
close it". get/set that flag with a new syscall, or sys_prctl(). That
way, people could do:
/bin/run-cache-friendly tar cf /dev/tape /huge-filesystem
and not have their pagecache trodden all over. Extra points for nuking
dentries and inodes too.
It's not particularly pretty, but it would be effective for the most
commonly complained about scenarios.
next prev parent reply other threads:[~2004-08-05 21:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 17:05 [PATCH] RSS ulimit enforcement for 2.6.8 Rik van Riel
2004-08-05 20:34 ` Bill Davidsen
2004-08-05 20:49 ` Rik van Riel
2004-08-05 21:20 ` Andrew Morton [this message]
2004-08-10 7:28 ` Kurt Garloff
2004-08-08 3:09 ` Bill Davidsen
2004-08-05 22:31 ` Andrew Morton
2004-08-06 0:19 ` Rik van Riel
2004-08-06 0:36 ` Andrew Morton
2004-08-06 0:51 ` Rik van Riel
2004-08-06 0:53 ` Andrew Morton
2004-08-06 0:59 ` Rik van Riel
2004-08-06 2:22 ` Nick Piggin
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=20040805142019.712c678a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.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