Re: [RFC v2 01/13] mm: export zap_page_range() for driver use

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

To: Xie Yongji <xieyongji@xxxxxxxxxxxxx>
Subject: Re: [RFC v2 01/13] mm: export zap_page_range() for driver use
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 22 Dec 2020 15:44:29 +0000
Cc: mst@xxxxxxxxxx, jasowang@xxxxxxxxxx, stefanha@xxxxxxxxxx, sgarzare@xxxxxxxxxx, parav@xxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, rdunlap@xxxxxxxxxxxxx, willy@xxxxxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, axboe@xxxxxxxxx, bcrl@xxxxxxxxx, corbet@xxxxxxx, virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx, netdev@xxxxxxxxxxxxxxx, kvm@xxxxxxxxxxxxxxx, linux-aio@xxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx
In-reply-to: <20201222145221.711-2-xieyongji@bytedance.com>
References: <20201222145221.711-1-xieyongji@bytedance.com> <20201222145221.711-2-xieyongji@bytedance.com>

On Tue, Dec 22, 2020 at 10:52:09PM +0800, Xie Yongji wrote:
> Export zap_page_range() for use in VDUSE.

Err, no.  This has absolutely no business being used by drivers.

References:
- [RFC v2 00/13] Introduce VDUSE - vDPA Device in Userspace
  - From: Xie Yongji
- [RFC v2 01/13] mm: export zap_page_range() for driver use
  - From: Xie Yongji

Prev by Date: Re: [PATCH 1/1] mm:improve the performance during fork
Next by Date: [linux-next:master] BUILD REGRESSION 6c3eb1b174c07bcaa927003e8bc91e81ab1d5a9e
Previous by thread: [RFC v2 01/13] mm: export zap_page_range() for driver use
Next by thread: [RFC v2 02/13] eventfd: track eventfd_signal() recursion depth separately in different cases
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