linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Manfred Spraul" <masp0008@stud.uni-sb.de>
To: "Benjamin C.R. LaHaise" <blah@kvack.org>,
	"James E. King, III" <jking@ariessys.com>
Cc: linux-mm@kvack.org
Subject: Re: Hello
Date: Fri, 30 Apr 1999 18:12:21 +0200	[thread overview]
Message-ID: <001901be9324$66ddcbf0$c80c17ac@clmsdev.local> (raw)

Benjamin C.R. LaHaise <blah@kvack.org> wrote:
>I think someone created patches that make a ramdisk out of the really high
>memory.  Try doing a search of the linux-kernel archives -- I remember
>seeing it withing the past 3 or 4 months.  Hope this helps!
I wrote that patch, but I abandoned it because I think that the performance
would be inacceptable: the data is first cached in the buffer cache,
and later moved into high memory, and if you access the data it's
moved back. I think that the memmove() calls would slow down
the system considerably.

If you need the patch I can send it to you.

But I have a new idea: what about replacing the current 'shm' implementation
with a high memory aware implementation.
* use high memory if high memory is available. We only need a simple
   bitmap for the high-mem. max_mapnr remains 1 or 2 GB, page_map
   is not extended.
* if you have more than 2 Gb memory, then you don't want that the system
    starts to swap out. So there is no need to support swap for that memory.
    This means: no double buffering etc required.
* I haven't yet read the new Xeon page table extentions,
  but perhaps we could support up to 64 GB memory without changing the
  rest of the OS   (Intel could write such a driver for Windows NT,
  I'm sure this is possible for Linux, too).
* it's very easy for the user mode programmers, no new interfaces.

I think that this implementation would required only a few hundred lines.

What do you think about this?

Regards,
    Manfred


--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

             reply	other threads:[~1999-04-30 16:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-04-30 16:12 Manfred Spraul [this message]
1999-04-29 16:20 ` Hello Benjamin C.R. LaHaise
1999-04-30  0:55 ` Hello Stephen C. Tweedie
1997-01-01 15:29   ` Hello ak
1999-05-04 11:45     ` Hello Stephen C. Tweedie
  -- strict thread matches above, loose matches on Subject: below --
2012-10-16  0:16 Hello Freeman Xiong
2012-10-14  5:22 Hello Quincy Thompson
2012-08-02 12:06 hello Orlando Villegas
2012-07-31 17:06 Hello Lee Montoya
2012-07-31  4:56 Hello Erick Andrade
2012-07-28  9:01 hello Romeo Grimes
2012-07-25 20:38 Hello Melissa Culver
2012-07-25 13:29 Hello Eliza Burke
2012-07-23 12:45 hello Victoria Metz
2012-07-17  4:06 hello Brad Mcneill
2012-07-13 15:16 hello Olivia Gilmore
2001-09-04 20:53 Hello Brian Elias
1999-05-05 15:27 Hello Manfred Spraul, Stephen C. Tweedie
1999-05-04 23:20 ` Hello Stephen C. Tweedie
1999-05-01 15:25 Hello Manfred Spraul
1999-05-01 14:00 Hello Manfred Spraul, ak
1999-05-04 11:41 ` Hello Stephen C. Tweedie
1999-05-01 13:56 Hello Manfred Spraul
1999-05-04 11:44 ` Hello Stephen C. Tweedie
1999-04-28 15:28 Hello James E. King, III
1999-04-29 14:27 ` Hello Benjamin C.R. LaHaise
1999-04-30  0:54 ` Hello Stephen C. Tweedie
1999-04-30 14:20 ` Hello Manfred Spraul

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='001901be9324$66ddcbf0$c80c17ac@clmsdev.local' \
    --to=masp0008@stud.uni-sb.de \
    --cc=blah@kvack.org \
    --cc=jking@ariessys.com \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).