From: Martin Dalecki <dalecki@evision-ventures.com>
To: Jonathan Morton <chromi@cyberspace.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] OOM handling
Date: Tue, 27 Mar 2001 18:29:31 +0200 [thread overview]
Message-ID: <3AC0BFEB.5E81FAB1@evision-ventures.com> (raw)
In-Reply-To: <l03130337b6e65e809070@[192.168.239.101]>
Jonathan Morton wrote:
>
> Oh and BTW, I think Bit/sqr(seconds) is a perfectly acceptable unit for
> "badness". Think about it - it increases with pigginess and decreases with
> longevity. I really don't see a problem with it per se.
Right it's not a problem pre se, but as you already explained
the problem is in the weightinig of different factors.
It's a matter of principle.
next prev parent reply other threads:[~2001-03-27 16:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-27 15:13 [PATCH] OOM handling Jonathan Morton
2001-03-27 16:03 ` Michel Wilson
2001-03-27 16:30 ` Martin Dalecki
2001-03-27 18:15 ` Rik van Riel
2001-03-27 16:29 ` Martin Dalecki [this message]
2001-03-27 17:07 ` Jonathan Morton
-- strict thread matches above, loose matches on Subject: below --
2001-03-23 17:32 [PATCH] Prevent OOM from killing init Alan Cox
2001-03-23 18:58 ` Martin Dalecki
2001-03-25 13:54 ` [PATCH] OOM handling Martin Dalecki
2001-03-25 13:54 ` Martin Dalecki
2001-03-25 15:06 ` Rik van Riel
2001-03-25 15:06 ` Rik van Riel
2001-03-25 15:20 ` Martin Dalecki
2001-03-25 15:20 ` Martin Dalecki
2001-03-25 15:50 ` Jeff Garzik
2001-03-25 17:08 ` Rik van Riel
2001-03-25 17:08 ` Rik van Riel
2001-03-25 15:44 ` Jonathan Morton
2001-03-25 15:44 ` Jonathan Morton
2001-03-25 15:47 ` Martin Dalecki
2001-03-25 15:47 ` Martin Dalecki
2001-03-25 16:36 ` Jonathan Morton
2001-03-25 16:36 ` Jonathan Morton
2001-03-26 21:34 ` Kevin Buhr
2001-03-26 21:34 ` Kevin Buhr
2001-03-26 22:00 ` Jonathan Morton
2001-03-26 22:00 ` Jonathan Morton
2001-03-26 2:13 ` Matthew Chappee
2001-03-26 11:33 ` Ingo Oeser
2001-03-26 11:49 ` Jasper Spaans
2001-03-26 16:11 ` Michael Peddemors
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=3AC0BFEB.5E81FAB1@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=chromi@cyberspace.org \
--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.