From: Robin Holt <holt@sgi.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: Robin Holt <holt@sgi.com>, Christoph Hellwig <hch@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jack Steiner <steiner@sgi.com>,
linux-mm@kvack.org
Subject: Re: [RFP-V2 0/3] Make mmu_notifier_invalidate_range_start able to sleep.
Date: Tue, 2 Feb 2010 08:21:30 -0600 [thread overview]
Message-ID: <20100202142130.GI6616@sgi.com> (raw)
In-Reply-To: <20100202141036.GL4135@random.random>
On Tue, Feb 02, 2010 at 03:10:36PM +0100, Andrea Arcangeli wrote:
> On Tue, Feb 02, 2010 at 07:51:41AM -0600, Robin Holt wrote:
> > I don't see the change in API with this method either.
>
> The API change I'm referring to, is the reason that you had to patch
> virt/kvm/kvm_main.c and drivers/misc/sgi-gru/grutlbpurge.c to prevent
So the API is an mmu_notifier thing and not external. I think
adding reference counting to the VMA and converting the i_mmap_lock
to i_mmap_sem might have a slightly larger impact on users of kernel
headers than this proposal.
> compile failure. That isn't needed if we really make mmu notifier
> sleepable like my old patched did just fine. Except they slowed down
> the locking to achieve it... (the slowdown should be confined to
> config option) and you don't want that I guess. But if you didn't need
Your argument seems ridiculous. Take this larger series of patches which
touches many parts of the kernel and has a runtime downside for 99% of
the user community but only when configured on and then try and argue
with the distros that they should slow all users down for our 1%.
> to return -EINVAL I think your userland would also be safer. Only
I think you missed my correction to an earlier statement. This patcheset
does not have any data corruption or userland inconsistency. I had mistakenly
spoken of a patchset I am working up as a lesser alternative to this one.
> problem I can see is that you would then have trouble to convince
> distro to build with the slower locking and you basically are ok to
> break userland in truncate to be sure your module will work with
> default binary distro kernel. It's a tradeoff and I'm not against it
> but it has to be well documented that this is an hack to be practical
> on binary shipped kernels.
This is no more a hack than the other long list of compromises that have
been made in the past. Very similar to your huge page patchset which
invalidates a page by using the range callout. NIHS is not the same as
a hack.
Robin
--
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:[~2010-02-02 14:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100202040145.555474000@alcatraz.americas.sgi.com>
2010-02-02 4:01 ` [RFP-V2 1/3] Have mmu_notifiers use SRCU so they may safely schedule Robin Holt
2010-02-02 4:01 ` [RFP-V2 2/3] Fix unmap_vma() bug related to mmu_notifiers Robin Holt
2010-02-02 4:01 ` [RFP-V2 3/3] Make mmu_notifier_invalidate_range_start able to sleep Robin Holt
2010-02-02 8:09 ` [RFP-V2 0/3] " Christoph Hellwig
2010-02-02 12:59 ` Andrea Arcangeli
2010-02-02 13:13 ` Andrea Arcangeli
2010-02-02 13:29 ` Robin Holt
2010-02-02 13:40 ` Andrea Arcangeli
2010-02-02 13:51 ` Robin Holt
2010-02-02 14:10 ` Andrea Arcangeli
2010-02-02 14:21 ` Robin Holt [this message]
2010-02-02 14:59 ` Andrea Arcangeli
2010-02-02 15:21 ` Robin Holt
2010-02-02 16:01 ` Andrea Arcangeli
2010-02-02 16:39 ` Robin Holt
2010-02-02 16:52 ` Andrea Arcangeli
2010-02-02 16:59 ` Robin Holt
2010-02-02 17:31 ` Robin Holt
2010-02-02 20:27 ` Andrea Arcangeli
2010-02-02 20:17 ` Andrea Arcangeli
2010-02-03 0:48 ` Robin Holt
2010-02-03 17:14 ` Andrea Arcangeli
2010-02-03 17:18 ` Andrea Arcangeli
2010-02-03 19:54 ` Robin Holt
2010-02-02 13:23 ` Robin Holt
2010-02-02 13:35 ` Robin Holt
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=20100202142130.GI6616@sgi.com \
--to=holt@sgi.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=steiner@sgi.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).