public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RSS ulimit enforcement for 2.6.8
Date: Sat, 07 Aug 2004 23:09:41 -0400	[thread overview]
Message-ID: <41159975.2080308@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0408051647440.8229-100000@dhcp83-102.boston.redhat.com>

Rik van Riel 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, you may
> be interested in CKRM for something like that:
> 
> 	http://ckrm.sf.net/

Interesting stuff.
> 
> For now I'm just interested in filling out the holes in
> rlimit for the mainline kernel, as well as putting some
> simple resource enforcement things in place.
> 
> I'm not about to add something complex at this stage ;) 
> 
I really wasn't asking that you should, just mumbling and hoping that 
some VM-savvy person would say "I can do that!" and offer an elegant 
solution. Given how little more cache helps for most loads on a machine 
with adequate memory, it seems silly to have almost all the programs on 
a 2GB machine pushed out to make room for pages read exactly once by a 
program copying a 4GB file.


-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  parent reply	other threads:[~2004-08-12 12:45 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
2004-08-10  7:28       ` Kurt Garloff
2004-08-08  3:09     ` Bill Davidsen [this message]
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=41159975.2080308@tmr.com \
    --to=davidsen@tmr.com \
    --cc=akpm@osdl.org \
    --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