From: Andrea Arcangeli <aarcange@redhat.com>
To: Robin Holt <holt@sgi.com>
Cc: 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 15:59:11 +0100 [thread overview]
Message-ID: <20100202145911.GM4135@random.random> (raw)
In-Reply-To: <20100202142130.GI6616@sgi.com>
On Tue, Feb 02, 2010 at 08:21:30AM -0600, Robin Holt wrote:
> 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%.
I wasn't suggesting to ask to apply such a patch to a kernel distro!
If that's you understood... That would have been the only ridiculous
thing about it.
If you want to send patches to distro your hack is probably the max as
it alters kABI but not so much.
> > 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.
If there is never data corruption or userland inconsistency when I do
mmap(MAP_SHARED) truncate(0) then I've to wonder why at all you need
any modification if you already can handle remote spte invalidation
through atomic sections. That is ridiculous that you can handle it
through atomic-section truncate without sleepability, and you still
ask sleepability for mmu notifier in the first place...
> 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.
My hack is just to avoid having to modify mmu notifier API to reduce
the amount of mangling I have to ask people to digest at once, I
simply can't do too many things at once, not right example of
compromise as it's going to get fixed without any downside... no
tradeoff at all.
--
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:59 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
2010-02-02 14:59 ` Andrea Arcangeli [this message]
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=20100202145911.GM4135@random.random \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=holt@sgi.com \
--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).