From: Linus Torvalds <torvalds@linux-foundation.org>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: Peter Xu <peterx@redhat.com>, John Hubbard <jhubbard@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>,
Linux-MM <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"Maya B . Gokhale" <gokhale2@llnl.gov>,
Yang Shi <yang.shi@linux.alibaba.com>,
Marty Mcfadden <mcfadden8@llnl.gov>,
Kirill Shutemov <kirill@shutemov.name>,
Oleg Nesterov <oleg@redhat.com>, Jann Horn <jannh@google.com>,
Jan Kara <jack@suse.cz>, Kirill Tkhai <ktkhai@virtuozzo.com>,
Andrea Arcangeli <aarcange@redhat.com>,
Christoph Hellwig <hch@lst.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/4] mm: Trial do_wp_page() simplification
Date: Thu, 17 Sep 2020 13:35:56 -0700 [thread overview]
Message-ID: <CAHk-=wh+qz0oOjyiQFXR_73RYSDUmJwHC8xd=KG0RzELnbS5OA@mail.gmail.com> (raw)
In-Reply-To: <20200917200638.GM8409@ziepe.ca>
On Thu, Sep 17, 2020 at 1:06 PM Jason Gunthorpe <jgg@ziepe.ca> wrote:
>
> Given that this is a user visible regression, it is nearly rc6, what
> do you prefer for next steps?
Since I had to deal with the page lock performance regression too, and
I think we have a fairly simple way forward, I'd rather do an rc8 and
get this done with, than revert and know we have to deal with it
anyway.
Particularly since I think this would _finally_ make page pinning make
sense. In it's current state, it's just yet another broken GUP that
doesn't actually fix things. But if we have the semantics that page
pinning really fixes things in the page tables, I think we now have a
proper solution to this and a _much_ cleaner model for it.
If it means that page pinning can also stop worrying about
MADV_DONTFORK any more, that would be an added API bonus.
For that to happen, we'd need to have the vma flag so that we wouldn't
have any worry about non-pinners, but as you suggested, I think even
just a mm-wide counter - or flag - to deal with the fast-bup case is
likely perfectly sufficient.
Yes, you'd still take a hit on fork, but only the actual process that
did pinning would take that hit. And *if* that ends up being a big
deal, the MADV_DONTFORK can be used to avoid it, rather than be a
correctness issue.
It really feels like this should be just "tens of lines of fairly
simple code", and it would clarify our GUP/PIN/COW rules enormously.
Linus
next prev parent reply other threads:[~2020-09-17 20:36 UTC|newest]
Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 23:49 [PATCH 0/4] mm: Simplfy cow handling Peter Xu
2020-08-21 23:49 ` [PATCH 1/4] mm: Trial do_wp_page() simplification Peter Xu
2020-08-24 8:36 ` Kirill Tkhai
2020-08-24 14:30 ` Jan Kara
2020-08-24 15:37 ` Kirill Tkhai
2020-08-24 18:22 ` Linus Torvalds
2020-09-01 7:01 ` Hugh Dickins
2020-09-14 14:38 ` Jason Gunthorpe
2020-09-14 17:32 ` Linus Torvalds
2020-09-14 18:34 ` Peter Xu
2020-09-14 21:15 ` Peter Xu
2020-09-14 22:55 ` Jason Gunthorpe
2020-09-14 22:59 ` Linus Torvalds
2020-09-14 23:28 ` Jason Gunthorpe
2020-09-15 0:19 ` Linus Torvalds
2020-09-15 14:50 ` Peter Xu
2020-09-15 15:17 ` Peter Xu
2020-09-15 16:05 ` Jason Gunthorpe
2020-09-15 18:29 ` Jason Gunthorpe
2020-09-15 19:13 ` Peter Xu
2020-09-15 19:38 ` Jason Gunthorpe
2020-09-15 21:33 ` Peter Xu
2020-09-15 23:22 ` Jason Gunthorpe
2020-09-16 1:50 ` John Hubbard
2020-09-16 17:48 ` Jason Gunthorpe
2020-09-16 18:46 ` Peter Xu
2020-09-17 11:25 ` Jason Gunthorpe
2020-09-17 18:11 ` Linus Torvalds
2020-09-17 19:38 ` Jason Gunthorpe
2020-09-17 19:51 ` Linus Torvalds
2020-09-18 16:40 ` Peter Xu
2020-09-18 17:16 ` Linus Torvalds
2020-09-18 19:57 ` Peter Xu
2020-09-18 17:32 ` Jason Gunthorpe
2020-09-18 20:40 ` Peter Xu
2020-09-18 20:59 ` Linus Torvalds
2020-09-19 0:28 ` Jason Gunthorpe
2020-09-18 21:06 ` John Hubbard
2020-09-19 0:01 ` Jason Gunthorpe
2020-09-21 8:35 ` Jan Kara
2020-09-21 12:03 ` Jason Gunthorpe
2022-02-16 16:59 ` Oded Gabbay
2022-02-16 17:24 ` Oded Gabbay
2022-02-16 19:04 ` Linus Torvalds
2022-02-16 19:20 ` Oded Gabbay
2022-02-16 19:24 ` David Hildenbrand
2020-09-21 13:42 ` Michal Hocko
2020-09-21 14:18 ` Peter Xu
2020-09-21 14:28 ` Michal Hocko
2020-09-21 14:38 ` Tejun Heo
2020-09-21 14:43 ` Christian Brauner
2020-09-21 14:55 ` Michal Hocko
2020-09-21 15:04 ` Christian Brauner
2020-09-21 16:06 ` Michal Hocko
2020-09-23 7:53 ` Michal Hocko
2020-09-21 14:41 ` Christian Brauner
2020-09-21 14:57 ` Michal Hocko
2020-09-21 16:31 ` Peter Xu
2020-09-17 18:14 ` Peter Xu
2020-09-17 18:26 ` Linus Torvalds
2020-09-17 19:03 ` Peter Xu
2020-09-17 19:42 ` Linus Torvalds
2020-09-17 19:55 ` John Hubbard
2020-09-17 20:06 ` Jason Gunthorpe
2020-09-17 20:19 ` John Hubbard
2020-09-17 20:25 ` Jason Gunthorpe
2020-09-17 20:35 ` Linus Torvalds [this message]
2020-09-17 21:40 ` Peter Xu
2020-09-17 22:09 ` Jason Gunthorpe
2020-09-17 22:25 ` Linus Torvalds
2020-09-17 22:48 ` Ira Weiny
2020-09-18 9:36 ` Jan Kara
2020-09-18 9:44 ` Jan Kara
2020-09-18 16:19 ` Jason Gunthorpe
2020-09-15 10:23 ` Leon Romanovsky
2020-09-15 15:56 ` Jason Gunthorpe
2020-09-15 15:03 ` Oleg Nesterov
2020-09-15 16:18 ` Peter Xu
2020-08-21 23:49 ` [PATCH 2/4] mm/ksm: Remove reuse_ksm_page() Peter Xu
2020-08-21 23:49 ` [PATCH 3/4] mm/gup: Remove enfornced COW mechanism Peter Xu
2020-09-14 14:27 ` Oleg Nesterov
2020-09-14 17:59 ` Peter Xu
2020-09-14 19:03 ` Linus Torvalds
2020-08-21 23:49 ` [PATCH 4/4] mm: Add PGREUSE counter Peter Xu
2020-08-22 16:14 ` Linus Torvalds
2020-08-24 0:24 ` Peter Xu
2020-08-22 16:05 ` [PATCH 0/4] mm: Simplfy cow handling Linus Torvalds
2020-08-23 23:58 ` Peter Xu
2020-08-24 8:38 ` Kirill Tkhai
2020-08-27 14:15 ` Peter Xu
2021-02-02 14:40 [PATCH 1/4] mm: Trial do_wp_page() simplification Gal Pressman
2021-02-02 16:31 ` Peter Xu
2021-02-02 16:44 ` Jason Gunthorpe
2021-02-02 17:05 ` Peter Xu
2021-02-02 17:13 ` Jason Gunthorpe
2021-02-03 12:43 ` Gal Pressman
2021-02-03 14:00 ` Jason Gunthorpe
2021-02-03 14:47 ` Gal Pressman
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='CAHk-=wh+qz0oOjyiQFXR_73RYSDUmJwHC8xd=KG0RzELnbS5OA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=gokhale2@llnl.gov \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=kirill@shutemov.name \
--cc=ktkhai@virtuozzo.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mcfadden8@llnl.gov \
--cc=oleg@redhat.com \
--cc=peterx@redhat.com \
--cc=yang.shi@linux.alibaba.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).