public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Rik van Riel <riel@redhat.com>
Cc: Andrea Arcangeli <andrea@suse.de>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, robert_hentosh@dell.com
Subject: Re: [PATCH][2/2] do not OOM kill if we skip writing many pages
Date: Mon, 3 Jan 2005 10:22:41 -0200	[thread overview]
Message-ID: <20050103122241.GE29158@logos.cnet> (raw)
In-Reply-To: <Pine.LNX.4.61.0501022319180.10640@chimarrao.boston.redhat.com>

On Sun, Jan 02, 2005 at 11:20:28PM -0500, Rik van Riel wrote:
> On Sun, 2 Jan 2005, Andrea Arcangeli wrote:
> 
> >I don't like this one, it's much less obvious than 1/2. After your
> >obviously right 1/2 we're already guaranteed at least a percentage of
> >the ram will not be dirty. Is the below really needed even after 1/2 +
> >Andrew's fix? Are you sure this isn't a workaround for the lack of
> >Andrew's fix.
> 
> Agreed, Andrew's fix should in theory be enough and only my
> 1/2 should be needed.
> 
> However, in practice people are still generating OOM kills
> even with both Andrew's fix and my own patch applied, so I
> suspect there's another hole left open somewhere...

Hi Rik,

What are the details of the OOM kills (output, workload, configuration, etc)? 

Are these running 2.6.10-mm? 



  reply	other threads:[~2005-01-03 15:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-20 15:17 [PATCH][2/2] do not OOM kill if we skip writing many pages Rik van Riel
2005-01-02 17:29 ` Andrea Arcangeli
2005-01-03  4:20   ` Rik van Riel
2005-01-03 12:22     ` Marcelo Tosatti [this message]
2005-01-03 16:25       ` Andrea Arcangeli
2005-01-03 16:40         ` Rik van Riel
2005-01-03 17:10           ` Rik van Riel
2005-01-03 18:51           ` Marcelo Tosatti
2005-01-03 22:01             ` Rik van Riel

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=20050103122241.GE29158@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=robert_hentosh@dell.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