public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Nelson <james4765@verizon.net>
To: chuck@gelm.net
Cc: Pratik Solanki <pratik.solanki.ml@gmail.com>,
	Ankit Jain <ankitjain1580@yahoo.com>,
	linux-newbie <linux-newbie@vger.kernel.org>
Subject: Re: VM Vs Swap space
Date: Thu, 07 Oct 2004 22:49:14 -0400	[thread overview]
Message-ID: <4166002A.6050308@verizon.net> (raw)
In-Reply-To: <4165BFA0.8010008@gelm.net>

chuck gelm wrote:

> Pratik Solanki wrote:
>
>> [CCing linux-newbie]
>>
>> On Thu, 7 Oct 2004 18:21:57 +0100 (BST), Ankit Jain
>> <ankitjain1580@yahoo.com> wrote:
>>  
>>
>>> well i dont know exactly but somewhat i feel that
>>> there must be some way to disable the virtual memory.
>>> yaa of course there should be some way. it is not that
>>> sys cant work without it
>>>   
>>
>>
>> Yes, you can have a system without virtual memory. Search for MMUless
>> linux kernel and you'll see patches/websites.
>>
>> My point was that disabling VM after its been enabled would tough (if
>> not impossible). Someone correct me if I am wrong here.
>>
>> Pratik.
>>
> I was thinking that an active swap partition was 'virtual memory'.
> Why are many folks using capital letters 'VM'.  Am I missing
> something?  Is 'VM' == virtual memory or is there a application
> or service called 'VM' ?
>
> Anywho, the only 'virtual memory' I know of is an active
> swap file or swap partition and either can be started
> or stopped in a running kernel.
> (I think.)
>
> Regards, Chuck



 From "Understanding the Linux Kernel":

"Virtual memory acts as a logical layer between the application memory 
requests and the hardware Memory Management Unit (MMU)."

It is an abstraction of system memory to provide an 
architecture-independent memory interface.  It allows for a great many 
things, including swap functionality, but its primary function is to 
make the details of memory management invisible to application 
programmers.  You just malloc() some memory, and you don't have to worry 
overmuch about far jumps, hardware cache alignment, or other annoying stuff.

It also allows large malloc() calls to succeed, even if physical memory 
is completely fragmented, by maintaining a set of page tables that allow 
virtual-to-physical mapping of memory addresses.

This is one of the most challenging areas of kernel development, and 
very hardware-specific.  I tried to understand how it worked recently, 
gave myself a splitting headache after 30 minutes, and decided to let it 
sit for another year or so until I understand kernel internals, computer 
architecture, and assembler much better than I do now :)

Jim
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2004-10-08  2:49 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-06  8:52 VM Vs Swap space Ankit Jain
2004-10-07  1:57 ` chuck gelm
2004-10-07  6:01   ` kernel kernel
2004-10-07  9:15   ` Ankit Jain
2004-10-07  9:25     ` kernel kernel
2004-10-07  9:37       ` Ankit Jain
2004-10-07 10:31         ` chuck gelm
2004-10-07 16:05         ` Pratik Solanki
2004-10-07 16:07         ` Pratik Solanki
2004-10-08  3:29           ` kernel kernel
2004-10-07 10:41     ` chuck gelm
2004-10-07 16:09       ` Pratik Solanki
     [not found]         ` <20041007172157.63553.qmail@web52908.mail.yahoo.com>
2004-10-07 18:49           ` Pratik Solanki
2004-10-07 22:13             ` chuck gelm
2004-10-08  2:49               ` Jim Nelson [this message]
2004-10-08 15:25               ` Pratik Solanki
     [not found] <9cb08bfa04100708182c097689@mail.gmail.com>
     [not found] ` <20041007160656.32450.qmail@web52904.mail.yahoo.com>
2004-10-07 16:13   ` Pratik Solanki

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=4166002A.6050308@verizon.net \
    --to=james4765@verizon.net \
    --cc=ankitjain1580@yahoo.com \
    --cc=chuck@gelm.net \
    --cc=linux-newbie@vger.kernel.org \
    --cc=pratik.solanki.ml@gmail.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