From: David Hildenbrand <david@redhat.com>
To: Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>,
linux-mm@kvack.org, target-devel@vger.kernel.org,
linux-scsi@vger.kernel.org
Cc: linux-block@vger.kernel.org, xuyu@linux.alibaba.com,
bostroesser@gmail.com
Subject: Re: [RFC 2/3] mm: export zap_page_range()
Date: Mon, 21 Mar 2022 13:01:44 +0100 [thread overview]
Message-ID: <a37e9ba2-354b-0b75-cb05-bc730cb30151@redhat.com> (raw)
In-Reply-To: <20220318095531.15479-3-xiaoguang.wang@linux.alibaba.com>
On 18.03.22 10:55, Xiaoguang Wang wrote:
> Module target_core_user will use it to implement zero copy feature.
>
> Signed-off-by: Xiaoguang Wang <xiaoguang.wang@linux.alibaba.com>
> ---
> mm/memory.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index 1f745e4d11c2..9974d0406dad 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -1664,6 +1664,7 @@ void zap_page_range(struct vm_area_struct *vma, unsigned long start,
> mmu_notifier_invalidate_range_end(&range);
> tlb_finish_mmu(&tlb);
> }
> +EXPORT_SYMBOL_GPL(zap_page_range);
>
> /**
> * zap_page_range_single - remove user pages in a given range
To which VMAs will you be applying zap_page_range? I assume only to some
special ones where you previously vm_insert_page(s)_mkspecial'ed pages,
not to some otherwise random VMAs, correct?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-03-21 12:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 9:55 [RFC 0/3] Add zero copy feature for tcmu Xiaoguang Wang
2022-03-18 9:55 ` [RFC 1/3] mm/memory.c: introduce vm_insert_page(s)_mkspecial Xiaoguang Wang
2022-03-23 16:45 ` Christoph Hellwig
2022-03-24 7:27 ` Xiaoguang Wang
2022-03-18 9:55 ` [RFC 2/3] mm: export zap_page_range() Xiaoguang Wang
2022-03-21 12:01 ` David Hildenbrand [this message]
2022-03-22 13:02 ` Xiaoguang Wang
2022-03-22 13:08 ` David Hildenbrand
2022-03-23 13:59 ` Xiaoguang Wang
2022-03-23 16:48 ` Christoph Hellwig
2022-03-23 16:47 ` Christoph Hellwig
2022-03-24 9:16 ` Ming Lei
2022-03-18 9:55 ` [RFC 3/3] scsi: target: tcmu: Support zero copy Xiaoguang Wang
2022-03-22 14:01 ` Bodo Stroesser
2022-03-23 14:33 ` Xiaoguang Wang
2022-03-25 9:06 ` Bodo Stroesser
2022-03-22 12:40 ` [RFC 0/3] Add zero copy feature for tcmu Bodo Stroesser
2022-03-22 13:17 ` Xiaoguang Wang
2022-03-22 14:05 ` Bodo Stroesser
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=a37e9ba2-354b-0b75-cb05-bc730cb30151@redhat.com \
--to=david@redhat.com \
--cc=bostroesser@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=target-devel@vger.kernel.org \
--cc=xiaoguang.wang@linux.alibaba.com \
--cc=xuyu@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).