Kirill A. Shutemov wrote: > From: "Kirill A. Shutemov" <kirill.shute...@linux.intel.com> > > ramfs is the most simple fs from page cache point of view. Let's start > transparent huge page cache enabling here. > > For now we allocate only non-movable huge page. It's not yet clear if > movable page is safe here and what need to be done to make it safe. > > Signed-off-by: Kirill A. Shutemov <kirill.shute...@linux.intel.com> > --- > fs/ramfs/inode.c | 6 +++++- > 1 file changed, 5 insertions(+), 1 deletion(-) > > diff --git a/fs/ramfs/inode.c b/fs/ramfs/inode.c > index c24f1e1..da30b4f 100644 > --- a/fs/ramfs/inode.c > +++ b/fs/ramfs/inode.c > @@ -61,7 +61,11 @@ struct inode *ramfs_get_inode(struct super_block *sb, > inode_init_owner(inode, dir, mode); > inode->i_mapping->a_ops = &ramfs_aops; > inode->i_mapping->backing_dev_info = &ramfs_backing_dev_info; > - mapping_set_gfp_mask(inode->i_mapping, GFP_HIGHUSER); > + /* > + * TODO: what should be done to make movable safe? > + */ > + mapping_set_gfp_mask(inode->i_mapping, > + GFP_TRANSHUGE & ~__GFP_MOVABLE);
Hugh, I've found old thread with the reason why we have GFP_HIGHUSER here, not GFP_HIGHUSER_MOVABLE: http://lkml.org/lkml/2006/11/27/156 It seems the origin reason is not longer valid, correct? -- Kirill A. Shutemov -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
