From: Andrea Arcangeli <andrea@suse.de>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Rik van Riel <riel@redhat.com>, 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 17:25:00 +0100 [thread overview]
Message-ID: <20050103162500.GX5164@dualathlon.random> (raw)
In-Reply-To: <20050103122241.GE29158@logos.cnet>
On Mon, Jan 03, 2005 at 10:22:41AM -0200, Marcelo Tosatti wrote:
> What are the details of the OOM kills (output, workload, configuration, etc)?
>
> Are these running 2.6.10-mm?
And did they apply Con's patch? (i.e. my 3/4 I posted few days ago)
next prev parent reply other threads:[~2005-01-03 16:24 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
2005-01-03 16:25 ` Andrea Arcangeli [this message]
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=20050103162500.GX5164@dualathlon.random \
--to=andrea@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--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