All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ORMAP
Date: Wed, 15 Mar 2006 23:24:36 +1100	[thread overview]
Message-ID: <44180784.6020608@yahoo.com.au> (raw)
In-Reply-To: <44178429.90808@comcast.net>

John Richard Moser wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> And looking through the recent discussions I see in one thread...
> 
> Willy Tarreau wrote:
> 
> 
>>It depends a lot on what people do with it in fact. For instance, it
>>works better in memory-constrained systems, probably thanks to rmap.
>>I have one 2.6 running reliably on my web server (hppa) where 2.4
>>regularly oopsed because of low memory.
> 
> 
> 
> This reminds me, what the hell ever happened to ORMAP?  That object
> based rmap thingy I tried out in one of wli's patches made my system
> boot like 3 times faster.  There were other cool things going on that I
> never got to try too, never saw that all out to fruition.
> 
> Status on some of the elements in the old 2.6-wli series from around
> there would be nice.  I'm curious as to what has gone in.
> 

2.6 has an object based rmap system working nicely for quite
a while now (though it was probably not exactly what you saw
in the -wli tree, but a derivative).

It would be surprising if that made your system boot 3 times
faster though (unless it was on the edge of a swap storm or
something)

-- 
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com 

  reply	other threads:[~2006-03-15 12:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15  3:04 ORMAP John Richard Moser
2006-03-15 12:24 ` Nick Piggin [this message]
2006-03-15 16:19   ` ORMAP John Richard Moser
2006-03-15 23:31     ` ORMAP Nick Piggin
2006-03-15 23:47       ` ORMAP John Richard Moser

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=44180784.6020608@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    /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.