mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] RSS ulimit enforcement for 2.6.8
Date: Thu, 5 Aug 2004 17:53:34 -0700	[thread overview]
Message-ID: <20040805175334.47f3054b.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0408052048570.8229-100000@dhcp83-102.boston.redhat.com>

Rik van Riel <riel@redhat.com> wrote:
>
> On Thu, 5 Aug 2004, Andrew Morton wrote:
> 
> > >  If the current patch isn't effective enough, we may want
> > >  to add more code.  However, we may want to try the simplest
> > >  possible approach first.
> > 
> > How do we know whether it is effective enough?  How do we define this?
> 
> Good question.  I guess our usual answer is "throw it out there
> and wait for somebody to show up with a workload that needs more".
> 
> If you want I could add a bit more code proactively, but how do
> we find out whether it's really needed ?

Good question.  What I'm groping for here is some definition of what we
actually want the feature to _do_.  Once we have that, and have suitably
argued about it, we can then go off and see if the patch actually does it.


  reply	other threads:[~2004-08-06  0:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-05 17:05 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
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 [this message]
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=20040805175334.47f3054b.akpm@osdl.org \
    --to=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

all inboxes | Powered by JetHome®