All of lore.kernel.org
 help / color / mirror / Atom feed
From: vamsi krishna <vamsi.krishnak@gmail.com>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Increasing virtual address space of a process, by treating virtual address's as offsets in secondary memory.
Date: Mon, 18 Jul 2005 10:12:46 +0530	[thread overview]
Message-ID: <3faf056805071721422594dd20@mail.gmail.com> (raw)

Hello Alan, mm-hackers,

I have been working this idea of increasing virtual address space of a
process with the help of secondary memory. At first this may seem like
the same virtual memory concept but its not the case.

Imagine all the virtual address the compiler generates while creating
the binary as relocatable offsets on the disk, and the application
specific runtime mmaps and munmaps these dynamically.

I was searching a lot about work on this, and found your reply where
you say that we can increase the virtual address space by mmaping and
munmaping programatically ourself.

So is the bigmem kernel implement this? may be  you can give me some
insight into this.

Some inputs on this would be highly appreciated.

Sincerely,
Vamsi kundeti. 

PS: Please refer this kernel mailing list email.


<--------------------------------------------------SNIP--------------------------------------------------------------------------->
Re: BIGMEM kernel question
From: Alan Cox (alan@lxorguk.ukuu.org.uk)
Date: Fri Jul 06 2001 - 16:46:16 EST



> Ahh. That makes sense. So how can I change the chunk size from 64k to
> something higher (I assume I could set it to 128k to effectively double
> that 3GB to 6GB)?

I think you misunderstand. If you want more than 3Gb you will have to map and
unmap stuff yourself. You only have 3Gb of per process address space due to
x86 weaknesses (lack of seperate kernel/user spaces without tlb flush
overhead nightmares)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" 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.tux.org/lkml/

    * Next message: Donald Becker: "Re: why this 1ms delay in
mdio_read? (cont'd from "are ioctl calls supposed to take this
long?")"
    * Previous message: Rik van Riel: "Re: BIGMEM kernel question"
    * In reply to: Eric Anderson: "Re: BIGMEM kernel question"
    * Next in thread: Brian Gerst: "Re: BIGMEM kernel question"
    * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] 
<------------------------------------------------------SNIP----------------------------------------------------------------------------->

             reply	other threads:[~2005-07-18  4:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-18  4:42 vamsi krishna [this message]
2005-07-18 11:45 ` Increasing virtual address space of a process, by treating virtual address's as offsets in secondary memory Alan Cox

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=3faf056805071721422594dd20@mail.gmail.com \
    --to=vamsi.krishnak@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.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 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.