linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@ziepe.ca>
To: Peter Xu <peterx@redhat.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Matthew Wilcox <willy@infradead.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Kirill Tkhai <ktkhai@virtuozzo.com>,
	Mike Rapoport <rppt@linux.vnet.ibm.com>,
	David Gibson <david@gibson.dropbear.id.au>,
	Kirill Shutemov <kirill@shutemov.name>,
	Christoph Hellwig <hch@lst.de>, Miaohe Lin <linmiaohe@huawei.com>,
	Gal Pressman <galpress@amazon.com>, Jann Horn <jannh@google.com>,
	Jan Kara <jack@suse.cz>, Wei Zhang <wzam@amazon.com>,
	Mike Kravetz <mike.kravetz@oracle.com>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v4 3/5] mm: Introduce page_needs_cow_for_dma() for deciding whether cow
Date: Tue, 9 Feb 2021 13:40:23 -0400	[thread overview]
Message-ID: <20210209174023.GI4718@ziepe.ca> (raw)
In-Reply-To: <20210209030229.84991-4-peterx@redhat.com>

On Mon, Feb 08, 2021 at 10:02:27PM -0500, Peter Xu wrote:
> We've got quite a few places (pte, pmd, pud) that explicitly checked against
> whether we should break the cow right now during fork().  It's easier to
> provide a helper, especially before we work the same thing on hugetlbfs.
> 
> Since we'll reference is_cow_mapping() in mm.h, move it there too.  Actually it
> suites mm.h more since internal.h is mm/ only, but mm.h is exported to the
> whole kernel.  With that we should expect another patch to use is_cow_mapping()
> whenever we can across the kernel since we do use it quite a lot but it's
> always done with raw code against VM_* flags.
> 
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
>  include/linux/mm.h | 21 +++++++++++++++++++++
>  mm/huge_memory.c   |  8 ++------
>  mm/internal.h      |  5 -----
>  mm/memory.c        |  8 +-------
>  4 files changed, 24 insertions(+), 18 deletions(-)

Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>

Jason


  reply	other threads:[~2021-02-09 17:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  3:02 [PATCH v4 0/5] mm/hugetlb: Early cow on fork, and a few cleanups Peter Xu
2021-02-09  3:02 ` [PATCH v4 1/5] hugetlb: Dedup the code to add a new file_region Peter Xu
2021-02-09  3:02 ` [PATCH v4 2/5] hugetlg: Break earlier in add_reservation_in_range() when we can Peter Xu
2021-02-09  3:02 ` [PATCH v4 3/5] mm: Introduce page_needs_cow_for_dma() for deciding whether cow Peter Xu
2021-02-09 17:40   ` Jason Gunthorpe [this message]
2021-02-09  3:02 ` [PATCH v4 4/5] mm: Use is_cow_mapping() across tree where proper Peter Xu
2021-02-09 17:46   ` Jason Gunthorpe
2021-02-09  3:02 ` [PATCH v4 5/5] hugetlb: Do early cow when page pinned on src mm Peter Xu
2021-02-09 17:54   ` Jason Gunthorpe

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=20210209174023.GI4718@ziepe.ca \
    --to=jgg@ziepe.ca \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@gibson.dropbear.id.au \
    --cc=galpress@amazon.com \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=jannh@google.com \
    --cc=kirill@shutemov.name \
    --cc=ktkhai@virtuozzo.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=peterx@redhat.com \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=torvalds@linux-foundation.org \
    --cc=willy@infradead.org \
    --cc=wzam@amazon.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).