[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20171110090818.GE4895@lst.de>
Date: Fri, 10 Nov 2017 10:08:18 +0100
From: Christoph Hellwig <hch@....de>
To: Dan Williams <dan.j.williams@...el.com>
Cc: linux-nvdimm@...ts.01.org, Jan Kara <jack@...e.cz>,
Matthew Wilcox <mawilcox@...rosoft.com>,
linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org,
linux-mm@...ck.org, Jeff Moyer <jmoyer@...hat.com>,
Ross Zwisler <ross.zwisler@...ux.intel.com>,
linux-fsdevel@...r.kernel.org, akpm@...ux-foundation.org,
hch@....de
Subject: Re: [PATCH 14/15] dax: associate mappings with inodes, and warn if
dma collides with truncate
> + struct {
> + /*
> + * ZONE_DEVICE pages are never on an lru or handled by
> + * a slab allocator, this points to the hosting device
> + * page map.
> + */
> + struct dev_pagemap *pgmap;
> + /*
> + * inode association for MEMORY_DEVICE_FS_DAX page-idle
> + * callbacks. Note that we don't use ->mapping since
> + * that has hard coded page-cache assumptions in
> + * several paths.
> + */
What assumptions? I'd much rather fix those up than having two fields
that have the same functionality.
Powered by blists - more mailing lists