Re: [RFC 1/3] mm/memory.c: introduce vm_insert_page(s)_mkspecial

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Xiaoguang Wang <xiaoguang.wang@xxxxxxxxxxxxxxxxx>
Subject: Re: [RFC 1/3] mm/memory.c: introduce vm_insert_page(s)_mkspecial
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 23 Mar 2022 09:45:25 -0700
Cc: linux-mm@xxxxxxxxx, target-devel@xxxxxxxxxxxxxxx, linux-scsi@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, xuyu@xxxxxxxxxxxxxxxxx, bostroesser@xxxxxxxxx
In-reply-to: <20220318095531.15479-2-xiaoguang.wang@linux.alibaba.com>
References: <20220318095531.15479-1-xiaoguang.wang@linux.alibaba.com> <20220318095531.15479-2-xiaoguang.wang@linux.alibaba.com>

I relaly don't think we should add this amount of overhead to the
core VM for a (relatively) irrelevant driver.

Follow-Ups:
- Re: [RFC 1/3] mm/memory.c: introduce vm_insert_page(s)_mkspecial
  - From: Xiaoguang Wang

References:
- [RFC 0/3] Add zero copy feature for tcmu
  - From: Xiaoguang Wang
- [RFC 1/3] mm/memory.c: introduce vm_insert_page(s)_mkspecial
  - From: Xiaoguang Wang

Prev by Date: Re: blocking vs. non-blocking mmu notifiers
Next by Date: Re: False positive kmemleak report for dtb properties names on powerpc
Previous by thread: [RFC 1/3] mm/memory.c: introduce vm_insert_page(s)_mkspecial
Next by thread: Re: [RFC 1/3] mm/memory.c: introduce vm_insert_page(s)_mkspecial
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux