From: Fawad Lateef <fawad_lateef@yahoo.com>
To: joelja@darkwing.uoregon.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Re: Need help in creating 8GB RAMDISK
Date: Sun, 4 Jul 2004 20:18:12 -0700 (PDT) [thread overview]
Message-ID: <20040705031812.4571.qmail@web20809.mail.yahoo.com> (raw)
Dear Joel
Can you please tell me the way of using more than 4GB
of RAM in a single process or module ???? I tried to
solve that problem using threads, but it isn't working
tooo, there might be the problem in my thread
implementation but can it be done using threads ???
Please do tell me way of doing this .........
I also tried to make 2 different modules each for 4GB
and then made another module which is just receiving
the request changes its bh->b_rdev to the
corresponding drive and returns 1. So kernel will try
to call the request function of the module related to
bh->b_rdev. but this is also not working .!!!!
Please help me ..... I m working on Linux-2.4.23
Thanks and Regards,
Fawad Lateef
> On Sun, 4 Jul 2004, Fawad Lateef wrote:
>
> > Hello
> >
> > I am creating a RAMDISK of 7GB (from 1GB to 8GB).
> I
> > reserved the RAM by changing the code in
> > arch/i386/mm/init.c ..........
> >
> > But I am not able to access the RAM from 1GB to
> 8GB in
> > a kernel module ........ after crossing the 4GB
> RAM,
> > the system goes into standby state. But if I
> insert
> > the same module 2 times means one for 1GB to 4GB
> and
> > other for 4GB to 8GB. and mount them seprately
> both
> > works fine ............
>
> on a non-64bit intel architecture you can only grab
> 4GB of ram per
> process because that's how big the page table is.
> There are 16 4GB page
> tables for the 64GB ram that intel machines are
> capable of addressing.
>
> > Can any one tell me the reason behind this ??? I
> think
> > that in a single module we can't access more than
> 4GB
> > RAM ...... If this is the reason then what to do
> ??? I
> > need 7GB RAMDISK as a single drive ....
> >
> > Thanks and Regards,
> >
> > Fawad Lateef
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Mail - You care about security. So do we.
> > http://promotions.yahoo.com/new_mail
> > -
> > 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/
> >
>
> --
>
--------------------------------------------------------------------------
>
> Joel Jaeggli Unix Consulting
> joelja@darkwing.uoregon.edu
> GPG Key Fingerprint: 5C6E 0104 BAF0 40B0 5BD3
> C38B F000 35AB B67F 56B2
>
>
> -
> 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/
>
__________________________________
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
http://promotions.yahoo.com/new_mail
next reply other threads:[~2004-07-05 3:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 3:18 Fawad Lateef [this message]
2004-07-05 4:39 ` Re: Need help in creating 8GB RAMDISK Joel Jaeggli
-- strict thread matches above, loose matches on Subject: below --
2004-07-10 14:26 Fawad Lateef
2004-07-11 4:19 Fawad Lateef
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=20040705031812.4571.qmail@web20809.mail.yahoo.com \
--to=fawad_lateef@yahoo.com \
--cc=joelja@darkwing.uoregon.edu \
--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.