why inode creation with GFP_HIGHUSER?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[hello world. my first mail  kernelnewbies]

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.

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux