From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [patch 2/2] only allow nonlinear vmas for ram backed filesystems
Date: Thu, 05 Apr 2007 11:36:00 +0200 [thread overview]
Message-ID: <1175765760.6483.93.camel@twins> (raw)
In-Reply-To: <E1HZOIr-0000Rv-00@dorka.pomaz.szeredi.hu>
On Thu, 2007-04-05 at 11:30 +0200, Miklos Szeredi wrote:
> From: Miklos Szeredi <mszeredi@suse.cz>
>
> page_mkclean() doesn't re-protect ptes for non-linear mappings, so a
> later re-dirty through such a mapping will not generate a fault,
> PG_dirty will not reflect the dirty state and the dirty count will be
> skewed. This implies that msync() is also currently broken for
> nonlinear mappings.
>
> Peter Zijlstra writes:
> > In order to make page_mkclean() work for nonlinear vmas we need to do a
> > full pte scan for each invocation (we could perhaps only scan 1 in n
> > times to try and limit the damage) and that hurts. This will basically
> > render it useless.
> >
> > The other solution is adding rmap information to nonlinear vmas but
> > doubling the memory overhead for nonlinear mappings was not deemed a
> > good idea.
>
> The easiest solution is to emulate remap_file_pages on non-linear
> mappings with simple mmap() for non ram-backed filesystems.
> Applications continue to work (albeit slower), as long as the number
> of remappings remain below the maximum vma count.
>
> However all currently known real uses of non-linear mappings are for
> ram backed filesystems, which this patch doesn't affect.
>
> William Lee Irwin III writes:
> > It's used for > 3GB files on tmpfs and also ramfs, sometimes
> > substantially larger than 3GB.
> >
> > It's not used for the database proper. It's used for the buffer pool,
> > which is the in-core destination and source of direct I/O, the on-disk
> > source and destination of the I/O being the database.
>
> Signed-off-by: Miklos Szeredi <mszeredi@suse.cz>
> Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> ---
>
> Index: linux/mm/fremap.c
> ===================================================================
> --- linux.orig/mm/fremap.c 2007-04-05 11:18:21.000000000 +0200
> +++ linux/mm/fremap.c 2007-04-05 11:18:25.000000000 +0200
> @@ -181,6 +181,24 @@ asmlinkage long sys_remap_file_pages(uns
> goto retry;
> }
> mapping = vma->vm_file->f_mapping;
> + /*
> + * page_mkclean doesn't work on nonlinear vmas, so if dirty
> + * pages need to be accounted, emulate with linear vmas.
> + */
> + if (mapping_cap_account_dirty(mapping)) {
Perhaps this should read:
if (vma_wants_writenotify(vma)) {
That way we would even allow read only non-linear mappings of 'real'
filesystem files.
> + unsigned long addr;
> +
> + flags &= MAP_NONBLOCK;
> + addr = mmap_region(vma->vm_file, start, size, flags,
> + vma->vm_flags, pgoff, 1);
> + if (IS_ERR_VALUE(addr))
> + err = addr;
> + else {
> + BUG_ON(addr != start);
> + err = 0;
> + }
> + goto out;
> + }
> spin_lock(&mapping->i_mmap_lock);
> flush_dcache_mmap_lock(mapping);
> vma->vm_flags |= VM_NONLINEAR;
--
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:[~2007-04-05 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-05 9:29 [patch 1/2] split mmap Miklos Szeredi
2007-04-05 9:30 ` [patch 2/2] only allow nonlinear vmas for ram backed filesystems Miklos Szeredi, Miklos Szeredi
2007-04-05 9:36 ` Peter Zijlstra [this message]
2007-04-05 9:39 ` Miklos Szeredi
2007-04-05 9:50 ` Peter Zijlstra
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=1175765760.6483.93.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
/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