linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: girish <girishvg@gmail.com>
To: Linux-MM@kvack.org
Subject: why inode creation with GFP_HIGHUSER?
Date: Wed, 13 Sep 2006 23:54:19 +0900	[thread overview]
Message-ID: <34a75100609130754t24b8bde6xcebda4f0684c51cb@mail.gmail.com> (raw)
In-Reply-To: <34a75100609130734m68729bdaj30258c10edfa7947@mail.gmail.com>

[hello world. my first mail  linux-mm]

i am following a trail of high-memory initialization on a MIPS32 based
system. i came across inode initialization.

i'd like to know why page(s) for inodes are allocated with
GFP_HIGHUSER & not with GFP_USER mask? is there any particular need
that the address_space be set with GFP_HIGHUSER flag?

(ref: http://lxr.free-electrons.com/source/fs/inode.c#150)
(ref: http://lxr.free-electrons.com/source/include/linux/pagemap.h#031)

i intend to allocate highmem pages strictly to user processes. my idea
is to completely avoid kernel mapping for these pages. so, as a dirty
hack - i changed mapping_set_gfp_mask function not to honor
__GFP_HIGHMEM zone selector if __GFP_IO | __GFP_FS are set. in short i
replace  GFP_HIGHUSER with GFP_USER mask. with this change the kernel
comes to life. but i am still confused about the effect of this change
on system, that i am yet to see?

any help in this regards will be greatly appreciated.

thanks in advance.
girish.

--
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:"dont@kvack.org"> email@kvack.org </a>

       reply	other threads:[~2006-09-13 14:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <34a75100609130734m68729bdaj30258c10edfa7947@mail.gmail.com>
2006-09-13 14:54 ` girish [this message]
2006-09-13 17:32   ` Christoph Lameter
2006-09-13 22:27     ` girish
2006-09-13 22:30       ` Christoph Lameter

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=34a75100609130754t24b8bde6xcebda4f0684c51cb@mail.gmail.com \
    --to=girishvg@gmail.com \
    --cc=Linux-MM@kvack.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