kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: pmkernel@gmail.com (piyush moghe)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Basic HighMeM Question
Date: Wed, 29 Jun 2011 12:00:30 +0530	[thread overview]
Message-ID: <BANLkTik8vRvSEajnrv=vnaHaJnkuh6eW4w@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=ixisCUHnmUvdir_Dfd6R9Uk29bw@mail.gmail.com>

Thanks Mulyadi and Prabhu for your enlightening description.

What a plight!!! memory has become soo cheap nowadays that I don't have less
than 1GB system and difficult to find someone in my knowledge having less
than 1 GB memory.

Although does this means that pages in FCOM will never have page fault? and
if this is true is this the reason why we assign NULL to memory descriptor (
mm_struct ) for kernel threads?


Regards,
Piyush

On Tue, Jun 28, 2011 at 8:56 PM, Mulyadi Santosa
<mulyadi.santosa@gmail.com>wrote:

> Hi :)
>
> On Tue, Jun 28, 2011 at 17:49, Prabhu nath <gprabhunath@gmail.com> wrote:
> > Dear Mulyadi,
> >
> > You are always an important character to jump in to any discussion and it
> > will be our great pleasure.
>
> Thanks :) Well, sometimes I just feel hesitate to break into someone's
> else discussion.
>
> > Please see inline for my views.
> >
> > On Tue, Jun 28, 2011 at 3:46 PM, Mulyadi Santosa <
> mulyadi.santosa at gmail.com>
> > wrote:
> >     In a 3G/1G partition. 1G of Kernel virtual address space is divided
> into
> > 896MB and 128 MB regions. I name them as
> >   Fixed Constant Offset mapped region (FCOM) - 0xC0000000 to 0xF8000000
> >   Dynamically Arbitrarily Mappable region (DAMR) - 0xF8000000 to
> 0xFFFFFFFF
>
> Great naming! You beat me on that aspect :)
>
> PS: Once there was a patch to create 4:4 VM split written by Ingo
> Molnar. It does maximize address space at the expense of full TLB
> flush on every context switch. AFAIK it once included in Fedora core 2
> or 3, but dropped afterward since it puts more negative impacts rather
> than positive enhancement (in virtual memory management point of view)
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com
> training: mulyaditraining.blogspot.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110629/c94e6a03/attachment-0001.html 

  reply	other threads:[~2011-06-29  6:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-27  9:12 Basic HighMeM Question piyush moghe
2011-06-27  9:28 ` Prabhu nath
     [not found]   ` <BANLkTinp6_n0z6OAzo1R6sq_nLynyo_3Xg@mail.gmail.com>
2011-06-27 11:15     ` Prabhu nath
2011-06-28  5:51       ` piyush moghe
2011-06-28 10:16         ` Mulyadi Santosa
2011-06-28 10:49           ` Prabhu nath
2011-06-28 15:26             ` Mulyadi Santosa
2011-06-29  6:30               ` piyush moghe [this message]
2011-06-29  6:38                 ` Mulyadi Santosa
2011-06-29  7:34                   ` Paraneetharan Chandrasekaran
2011-06-29  9:03                     ` Mulyadi Santosa

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='BANLkTik8vRvSEajnrv=vnaHaJnkuh6eW4w@mail.gmail.com' \
    --to=pmkernel@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).