linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Daniel Phillips <phillips@arcor.de>
Cc: lkml <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.34-mm2
Date: Sat, 14 Sep 2002 21:12:25 -0700	[thread overview]
Message-ID: <3D8408A9.7B34483D@digeo.com> (raw)
In-Reply-To: <E17qQMq-0001JV-00@starship>

Daniel Phillips wrote:
> 
> On Thursday 12 September 2002 08:29, Andrew Morton wrote:
> > url: http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.34/2.5.34-mm2/
> >
> > -sleeping-release_page.patch
> 
> What's this one?  Couldn't find it as a broken-out patch.

The `-' means it was removed from the patchset.  Linus merged it.
See  2.5.34/2.5.34-mm1/broken-out/sleeping-release_page.patch

> On the nonblocking vm front, does it rule or suck?

It rules, until someone finds something at which it sucks.

>  I heard you
> mention, on the one hand, huge speedups on some load (dbench I think)
> but your in-patch comments mention slowdown by 1.7X on kernel
> compile.

You misread.  Relative times for running `make -j6 bzImage' with mem=512m:

Unloaded system:		                     1.0
2.5.34-mm4, while running 4 x `dbench 100'           1.7
Any other kernel while running 4 x `dbench 100'      basically infinity
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-09-15  3:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12  6:29 2.5.34-mm2 Andrew Morton
2002-09-15  3:46 ` 2.5.34-mm2 Daniel Phillips
2002-09-15  4:12   ` Andrew Morton [this message]
2002-09-15  4:23     ` 2.5.34-mm2 Daniel Phillips
2002-09-15  5:37       ` 2.5.34-mm2 Andrew Morton
2002-09-15 14:58         ` 2.5.34-mm2 Rik van Riel
2002-09-15 17:13           ` 2.5.34-mm2 Andrew Morton
2002-09-15 17:08             ` 2.5.34-mm2 Daniel Phillips

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=3D8408A9.7B34483D@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=phillips@arcor.de \
    /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