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: Wed, 1 Jun 2011 09:54:09 +0530	[thread overview]
Message-ID: <BANLkTikN5fq5g=gp97mA6eMJVi1oQZnbBw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTiktzP4PmYdbSyKY8F_a0hhEfUzZZQ@mail.gmail.com>

Yes peter you r right..
But my main concern(which i dint convey properly in subject) is whether
virtual memory allocation has a limit or not.
I got it answered.

Thank you ..

On Tue, May 31, 2011 at 8:57 PM, Peter Teoh <htmldeveloper@gmail.com> wrote:

> To answer your subject:   I think the straight answer is "no".   Many
> reason, among them:
>
> ARM is still 32-bit, at least at the present moment:
>
> http://www.google.com/search?q=does+arm+have+64bit&num=100
>
> so with hardware 32-bit based, doing MMU at the 64-bit level is still
> not possible (without the MMU 64-bit hardware architecture, I don't
> think it is possible to do any >4GB memory translation stuff.   Am I
> not wrong?
>
> On Tue, May 31, 2011 at 1:54 PM, sandeep kumar
> <coolsandyforyou@gmail.com> wrote:
> > 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,
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
> >
>
>
>
> --
> Regards,
> Peter Teoh
>



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

      reply	other threads:[~2011-06-01  4:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-31  5:54 Can i allocate 4GB virtual addresses (more than a certain limit) using vmalloc? sandeep kumar
2011-05-31  7:02 ` 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 [this message]

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='BANLkTikN5fq5g=gp97mA6eMJVi1oQZnbBw@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).