kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: coolsandyforyou@gmail.com (sandeep kumar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Can i allocate 4GB virtual addresses (more than a certain limit) using vmalloc?
Date: Tue, 31 May 2011 11:24:30 +0530	[thread overview]
Message-ID: <BANLkTikCwSmk5SuCVmhCzyKM9dQeWY8MVw@mail.gmail.com> (raw)

Hi all,
The following link gives the memory map for the arm architecture.
http://www.arm.linux.org.uk/developer/memory.txt

I have the following doubts..
1) Any chipset(based on arm) manufacturer(qualcom,samsung..) should follow
the same memory map.
Is it hardly constrained or can be changed?
Where are this constraints are implemented in the kernel source tree?

2) while i was student, i read in OS concepts that, "Virtual memory gives an
illusion to a process,
that it has always a larger continuous address space (even more than RAM)
available to it."
So i thought i could allocate howmuch ever memory i want.
But seeing the above link,i observed there is some limitation in the address
space created by the vmalloc().
So i m now thinking that vmalloc has some limit.

Please make me clear these things....


With regards,
Sandeep Kumar Anantapalli,
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110531/fbf69350/attachment.html 

             reply	other threads:[~2011-05-31  5:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31  5:54 sandeep kumar [this message]
2011-05-31  7:02 ` Can i allocate 4GB virtual addresses (more than a certain limit) using vmalloc? Mulyadi Santosa
2011-05-31  8:09   ` sandeep kumar
2011-05-31 15:19 ` Dave Hylands
2011-08-22 21:43   ` subin gangadharan
2011-08-22 22:27     ` Jonathan Neuschäfer
2011-05-31 15:27 ` Peter Teoh
2011-06-01  4:24   ` sandeep kumar

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=BANLkTikCwSmk5SuCVmhCzyKM9dQeWY8MVw@mail.gmail.com \
    --to=coolsandyforyou@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).