mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Song Liu <songliubraving@fb.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: Linux-MM <linux-mm@kvack.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"matthew.wilcox@oracle.com" <matthew.wilcox@oracle.com>,
	"kirill.shutemov@linux.intel.com"
	<kirill.shutemov@linux.intel.com>,
	"Kernel Team" <Kernel-team@fb.com>,
	"william.kucharski@oracle.com" <william.kucharski@oracle.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH v5 6/6] mm,thp: avoid writes to file with THP in pagecache
Date: Fri, 21 Jun 2019 13:43:42 +0000	[thread overview]
Message-ID: <FA332FEC-B64D-4E60-A591-AD04311F21FF@fb.com> (raw)
In-Reply-To: <20190621133948.2pvagzfwpwwk6rho@box>



> On Jun 21, 2019, at 6:39 AM, Kirill A. Shutemov <kirill@shutemov.name> wrote:
> 
> On Fri, Jun 21, 2019 at 01:10:54PM +0000, Song Liu wrote:
>> 
>> 
>>> On Jun 21, 2019, at 6:07 AM, Kirill A. Shutemov <kirill@shutemov.name> wrote:
>>> 
>>> On Thu, Jun 20, 2019 at 01:53:48PM -0700, Song Liu wrote:
>>>> In previous patch, an application could put part of its text section in
>>>> THP via madvise(). These THPs will be protected from writes when the
>>>> application is still running (TXTBSY). However, after the application
>>>> exits, the file is available for writes.
>>>> 
>>>> This patch avoids writes to file THP by dropping page cache for the file
>>>> when the file is open for write. A new counter nr_thps is added to struct
>>>> address_space. In do_last(), if the file is open for write and nr_thps
>>>> is non-zero, we drop page cache for the whole file.
>>>> 
>>>> Signed-off-by: Song Liu <songliubraving@fb.com>
>>>> ---
>>>> fs/inode.c         |  3 +++
>>>> fs/namei.c         | 22 +++++++++++++++++++++-
>>>> include/linux/fs.h | 31 +++++++++++++++++++++++++++++++
>>>> mm/filemap.c       |  1 +
>>>> mm/khugepaged.c    |  4 +++-
>>>> 5 files changed, 59 insertions(+), 2 deletions(-)
>>>> 
>>>> diff --git a/fs/inode.c b/fs/inode.c
>>>> index df6542ec3b88..518113a4e219 100644
>>>> --- a/fs/inode.c
>>>> +++ b/fs/inode.c
>>>> @@ -181,6 +181,9 @@ int inode_init_always(struct super_block *sb, struct inode *inode)
>>>> 	mapping->flags = 0;
>>>> 	mapping->wb_err = 0;
>>>> 	atomic_set(&mapping->i_mmap_writable, 0);
>>>> +#ifdef CONFIG_READ_ONLY_THP_FOR_FS
>>>> +	atomic_set(&mapping->nr_thps, 0);
>>>> +#endif
>>>> 	mapping_set_gfp_mask(mapping, GFP_HIGHUSER_MOVABLE);
>>>> 	mapping->private_data = NULL;
>>>> 	mapping->writeback_index = 0;
>>>> diff --git a/fs/namei.c b/fs/namei.c
>>>> index 20831c2fbb34..de64f24b58e9 100644
>>>> --- a/fs/namei.c
>>>> +++ b/fs/namei.c
>>>> @@ -3249,6 +3249,22 @@ static int lookup_open(struct nameidata *nd, struct path *path,
>>>> 	return error;
>>>> }
>>>> 
>>>> +/*
>>>> + * The file is open for write, so it is not mmapped with VM_DENYWRITE. If
>>>> + * it still has THP in page cache, drop the whole file from pagecache
>>>> + * before processing writes. This helps us avoid handling write back of
>>>> + * THP for now.
>>>> + */
>>>> +static inline void release_file_thp(struct file *file)
>>>> +{
>>>> +#ifdef CONFIG_READ_ONLY_THP_FOR_FS
>>>> +	struct inode *inode = file_inode(file);
>>>> +
>>>> +	if (inode_is_open_for_write(inode) && filemap_nr_thps(inode->i_mapping))
>>>> +		truncate_pagecache(inode, 0);
>>>> +#endif
>>>> +}
>>>> +
>>>> /*
>>>> * Handle the last step of open()
>>>> */
>>>> @@ -3418,7 +3434,11 @@ static int do_last(struct nameidata *nd,
>>>> 		goto out;
>>>> opened:
>>>> 	error = ima_file_check(file, op->acc_mode);
>>>> -	if (!error && will_truncate)
>>>> +	if (error)
>>>> +		goto out;
>>>> +
>>>> +	release_file_thp(file);
>>> 
>>> What protects against re-fill the file with THP in parallel?
>> 
>> khugepaged would only process vma with VM_DENYWRITE. So once the
>> file is open for write (i_write_count > 0), khugepage will not 
>> collapse the pages. 
> 
> I have not look at the patch very closely. Do you only create THP by
> khugepaged? Not in fault path?

Right. My set only creates THP in khugepaged. William Kucharski is
working on the fault path. 

Thanks,
Song


      reply	other threads:[~2019-06-21 13:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-20 20:53 [PATCH v5 0/6] Enable THP for text section of non-shmem files Song Liu
2019-06-20 20:53 ` [PATCH v5 1/6] filemap: check compound_head(page)->mapping in filemap_fault() Song Liu
2019-06-20 20:53 ` [PATCH v5 2/6] filemap: update offset check " Song Liu
2019-06-20 20:53 ` [PATCH v5 3/6] mm,thp: stats for file backed THP Song Liu
2019-06-20 20:53 ` [PATCH v5 4/6] khugepaged: rename collapse_shmem() and khugepaged_scan_shmem() Song Liu
2019-06-20 20:53 ` [PATCH v5 5/6] mm,thp: add read-only THP support for (non-shmem) FS Song Liu
2019-06-20 20:53 ` [PATCH v5 6/6] mm,thp: avoid writes to file with THP in pagecache Song Liu
2019-06-21  0:52   ` Rik van Riel
2019-06-21 13:07   ` Kirill A. Shutemov
2019-06-21 13:10     ` Song Liu
2019-06-21 13:39       ` Kirill A. Shutemov
2019-06-21 13:43         ` Song Liu [this message]

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=FA332FEC-B64D-4E60-A591-AD04311F21FF@fb.com \
    --to=songliubraving@fb.com \
    --cc=Kernel-team@fb.com \
    --cc=akpm@linux-foundation.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=kirill@shutemov.name \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=matthew.wilcox@oracle.com \
    --cc=william.kucharski@oracle.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

all inboxes | Powered by JetHome®