public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Hua Zhong" <hzhong@cisco.com>
To: <root@chaos.analogic.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: question about running program from a RAM disk
Date: Thu, 28 Feb 2002 14:24:07 -0800	[thread overview]
Message-ID: <01bc01c1c0a6$a3c315e0$bb3147ab@amer.cisco.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020228170705.2670A-100000@chaos.analogic.com>

In the final system we are going to turn off swap. I had dreamed that Linux
could directly use the page frame on the RAM disk instead of doing another
copy :-)

Thanks for the reply

Hua

----- Original Message -----
From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Hua Zhong" <hzhong@cisco.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Sent: Thursday, February 28, 2002 2:12 PM
Subject: Re: question about running program from a RAM disk


> On Thu, 28 Feb 2002, Hua Zhong wrote:
>
> > Hi all:
> >
> > If I run a program from a RAM disk, will Linux be able to run it
directly
> > from
> > the disk itself (as the image is already in memory), or do it the same
way
> > as running from a disk?
> >
> > Thanks.
> >
> > Hua
>
> It does it the same was as from a mechanical disk. If it uses
> dynamic linking, the default, the runtime libraries are
> memory-mapped and shared. In a perfect system, a very large
> program is not read into user's virtual address space all at
> once. Page-faults bring in, or discard, pages as required.
>
> Cheers,
> Dick Johnson
>
> Penguin : Linux version 2.4.1 on an i686 machine (797.90 BogoMips).
>
>         111,111,111 * 111,111,111 = 12,345,678,987,654,321
>


  reply	other threads:[~2002-02-28 22:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 19:51 question about running program from a RAM disk Hua Zhong
2002-02-28 22:12 ` Richard B. Johnson
2002-02-28 22:24   ` Hua Zhong [this message]
2002-02-28 22:55     ` Oliver Neukum
2002-02-28 23:48     ` H. Peter Anvin
2002-03-01  1:40     ` Scott Murray

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='01bc01c1c0a6$a3c315e0$bb3147ab@amer.cisco.com' \
    --to=hzhong@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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