From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: Ning Qu <quning@google.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Wu Fengguang <fengguang.wu@intel.com>, Jan Kara <jack@suse.cz>,
Mel Gorman <mgorman@suse.de>,
linux-mm@kvack.org, Andi Kleen <ak@linux.intel.com>,
Matthew Wilcox <willy@linux.intel.com>,
Hillf Danton <dhillf@gmail.com>, Dave Hansen <dave@sr71.net>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 07/12] mm, thp, tmpfs: handle huge page in shmem_undo_range for truncate
Date: Wed, 16 Oct 2013 15:09:51 +0300 (EEST) [thread overview]
Message-ID: <20131016120951.B5012E0090@blue.fi.intel.com> (raw)
In-Reply-To: <CACz4_2fiF+vaAbFixgGF+Uxn0av4H8y-aMQdyi3yYs5pdS2WBA@mail.gmail.com>
Ning Qu wrote:
> > Again. Here and below ifdef is redundant: PageTransHugeCache() is zero
> > compile-time and thp case will be optimize out.
>
> The problem is actually from HPAGE_CACHE_INDEX_MASK, it is marked as
> build bug when CONFIG_TRANSPARENT_HUGEPAGE_PAGECACHE is false. So we
> either wrap some logic inside a inline function, or we have to be like
> this .. Or we don't treat the HPAGE_CACHE_INDEX_MASK as a build bug?
HPAGE_CACHE_INDEX_MASK shouldn't be a problem.
If it's wrapped into 'if PageTransHugeCache(page)' or similar it will be
eliminated by compiler if thp-pc disabled and build bug will not be
triggered.
>
> >
> > And do we really need a copy of truncate logic here? Is there a way to
> > share code?
> >
> The truncate between tmpfs and general one is similar but not exactly
> the same (no readahead), so share the whole function might not be a
> good choice from the perspective of tmpfs? Anyway, there are other
> similar functions in tmpfs, e.g. the one you mentioned for
> shmem_add_to_page_cache. It is possible to share the code, I am just
> worried it will make the logic more complicated?
I think introducing thp-pc is good opportunity to refactor all these code.
--
Kirill A. Shutemov
--
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>
next prev parent reply other threads:[~2013-10-16 12:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 0:13 [PATCH 07/12] mm, thp, tmpfs: handle huge page in shmem_undo_range for truncate Ning Qu
2013-10-15 11:01 ` Kirill A. Shutemov
2013-10-15 18:48 ` Ning Qu
2013-10-16 12:09 ` Kirill A. Shutemov [this message]
2013-10-16 18:48 ` Ning Qu
2013-10-17 20:58 ` Ning Qu
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=20131016120951.B5012E0090@blue.fi.intel.com \
--to=kirill.shutemov@linux.intel.com \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=dave@sr71.net \
--cc=dhillf@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=quning@google.com \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).