[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150617113121.GC9246@lst.de>
Date: Wed, 17 Jun 2015 13:31:21 +0200
From: Christoph Hellwig <hch@....de>
To: Dan Williams <dan.j.williams@...el.com>
Cc: arnd@...db.de, mingo@...hat.com, bp@...en8.de, hpa@...or.com,
tglx@...utronix.de, ross.zwisler@...ux.intel.com,
akpm@...ux-foundation.org, jgross@...e.com, x86@...nel.org,
toshi.kani@...com, linux-nvdimm@...ts.01.org,
benh@...nel.crashing.org, mcgrof@...e.com, konrad.wilk@...cle.com,
linux-kernel@...r.kernel.org, stefan.bader@...onical.com,
luto@...capital.net, linux-mm@...ck.org, geert@...ux-m68k.org,
ralf@...ux-mips.org, hmh@....eng.br, mpe@...erman.id.au,
tj@...nel.org, paulus@...ba.org, hch@....de
Subject: Re: [PATCH v4 6/6] arch, x86: pmem api for ensuring durability of
persistent memory updates
This mess with arch_ methods and an ops vecor is almost unreadable.
What's the problem with having something like:
pmem_foo()
{
if (arch_has_pmem) // or sync_pmem
arch_pmem_foo();
generic_pmem_foo();
}
This adds a branch at runtime, but that shoudn't really be any slower
than an indirect call on architectures that matter.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists