[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YXFNqI/+nbdVEoif@infradead.org>
Date: Thu, 21 Oct 2021 04:23:20 -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 3/6] pmem: pmem_dax_direct_access() to honor the
DAXDEV_F_RECOVERY flag
On Wed, Oct 20, 2021 at 06:10:56PM -0600, Jane Chu wrote:
> - if (unlikely(is_bad_pmem(&pmem->bb, PFN_PHYS(pgoff) / 512,
> - PFN_PHYS(nr_pages))))
> + if (unlikely(!(flags & DAXDEV_F_RECOVERY) &&
> + is_bad_pmem(&pmem->bb, PFN_PHYS(pgoff) / 512,
> + PFN_PHYS(nr_pages))))
The indentation here is pretty messed up. Something like this would
be move normal:
if (unlikely(!(flags & DAXDEV_F_RECOVERY) &&
is_bad_pmem(&pmem->bb, PFN_PHYS(pgoff) / 512,
PFN_PHYS(nr_pages)))) {
but if we don't really need the unlikely we could do an actually
readable variant:
if (!(flags & DAXDEV_F_RECOVERY) &&
is_bad_pmem(&pmem->bb, PFN_PHYS(pgoff) / 512, PFN_PHYS(nr_pages)))
Powered by blists - more mailing lists