[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191112065507.GA15915@infradead.org>
Date: Mon, 11 Nov 2019 22:55:07 -0800
From: Christoph Hellwig <hch@...radead.org>
To: ira.weiny@...el.com
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Chris Mason <clm@...com>, Josef Bacik <josef@...icpanda.com>,
David Sterba <dsterba@...e.com>,
Jaegeuk Kim <jaegeuk@...nel.org>, Chao Yu <chao@...nel.org>,
linux-xfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Trond Myklebust <trond.myklebust@...merspace.com>,
Anna Schumaker <anna.schumaker@...app.com>,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net, linux-nfs@...r.kernel.org,
linux-mm@...ck.org, Dave Chinner <david@...morbit.com>,
Jan Kara <jack@...e.cz>
Subject: Re: [PATCH 2/2] fs: Move swap_[de]activate to file_operations
On Mon, Nov 11, 2019 at 04:34:52PM -0800, ira.weiny@...el.com wrote:
> From: Ira Weiny <ira.weiny@...el.com>
>
> swap_activate() and swap_deactivate() have nothing to do with
> address spaces. We want to eventually make the address space operations
> dynamic to switch inode flags on the fly. So to simplify this code as
> well as properly track these operations we move these functions to the
> file_operations vector.
What is the point? If we switch aops for DAX vs not we might as well
switch file operations as well, as they pretty much are entirely
different.
Powered by blists - more mailing lists