From: Fawad Lateef <fawad_lateef@yahoo.com>
To: wli@holomorphy.com
Cc: linux-mm@kvack.org
Subject: Re: Re: Plzz help me regarding HIGHMEM (PAE) confusion in Linux-2.4 ???
Date: Thu, 9 Dec 2004 19:48:48 -0800 (PST) [thread overview]
Message-ID: <20041210034848.4490.qmail@web53909.mail.yahoo.com> (raw)
--- William Lee Irwin III <wli@holomorphy.com> wrote:
> The pgd is not loaded into %cr3, only its address.
>
Ya, right, Actually I mis-understood that. Thanks for
clearing.
>
> There is only one kernel address space. You are
> probably actually
> trying to write blkdev-highmem, but it would be far
> easier to populate
> a ramfs at boot instead of using a ramdisk.
>
Is the kmap_atomic fails due to a single address space
of kernel ??? If not then y kmap is failing in my
case. I m actually writing a simple RAMDISK but the
RAM it is using is the HIGHMEM and I already reserved
all the HIGHMEM for me by changing in
arch/i386/mm/init.c in one_highpage_init function, I
wrote
if((unsigned long)(page-mem_map) >= 0x100000) (
SetPageReserved(page);
set_bit(PG_highmem, &page->flags);
atomic_set(&page->count, 1);
totalhigh_pages++;
return;
}
Is reserving mem through this way is wrong ??? And is
it creating problem ??
> The ramdisk block driver is crusty and probably
> qualifies as broken
> on 32-bit due to the resource scalability issues. It
> would be much
> easier (and you'd encounter much less negative
> feedback) using ramfs or
> a 64-bit architecture.
>
Ok, I will try that through ramfs. but using 64bit
machine is not feasible for me.
Thanks
Fawad Lateef
__________________________________
Do you Yahoo!?
Yahoo! Mail - You care about security. So do we.
http://promotions.yahoo.com/new_mail
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
reply other threads:[~2004-12-10 3:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041210034848.4490.qmail@web53909.mail.yahoo.com \
--to=fawad_lateef@yahoo.com \
--cc=linux-mm@kvack.org \
--cc=wli@holomorphy.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