[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YXFM64mFLN8dagrY@infradead.org>
Date: Thu, 21 Oct 2021 04:20:11 -0700
From: Christoph Hellwig <hch@...radead.org>
To: Jane Chu <jane.chu@...cle.com>
Cc: david@...morbit.com, djwong@...nel.org, dan.j.williams@...el.com,
hch@...radead.org, vishal.l.verma@...el.com, dave.jiang@...el.com,
agk@...hat.com, snitzer@...hat.com, dm-devel@...hat.com,
ira.weiny@...el.com, willy@...radead.org, vgoyal@...hat.com,
linux-fsdevel@...r.kernel.org, nvdimm@...ts.linux.dev,
linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org
Subject: Re: [PATCH 2/6] dax: prepare dax_direct_access() API with
DAXDEV_F_RECOVERY flag
On Wed, Oct 20, 2021 at 06:10:55PM -0600, Jane Chu wrote:
> @@ -156,8 +156,8 @@ bool generic_fsdax_supported(struct dax_device *dax_dev,
> }
>
> id = dax_read_lock();
> - len = dax_direct_access(dax_dev, pgoff, 1, &kaddr, &pfn);
> - len2 = dax_direct_access(dax_dev, pgoff_end, 1, &end_kaddr, &end_pfn);
> + len = dax_direct_access(dax_dev, pgoff, 1, &kaddr, &pfn, 0);
> + len2 = dax_direct_access(dax_dev, pgoff_end, 1, &end_kaddr, &end_pfn, 0);
FYI, I have a series killing this code. But either way please avoid
these overly long lines.
> long dax_direct_access(struct dax_device *dax_dev, pgoff_t pgoff, long nr_pages,
> - void **kaddr, pfn_t *pfn)
> + void **kaddr, pfn_t *pfn, unsigned long flags)
API design: I'd usually expect flags before output paramters.
Powered by blists - more mailing lists