From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752618AbcLKGcg (ORCPT ); Sun, 11 Dec 2016 01:32:36 -0500 Received: from mga05.intel.com ([192.55.52.43]:31490 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751681AbcLKGce (ORCPT ); Sun, 11 Dec 2016 01:32:34 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,331,1477983600"; d="scan'208";a="1080299163" Subject: [PATCH 0/8] device-dax: sub-division support From: Dan Williams To: linux-nvdimm@ml01.01.org Cc: linux-kernel@vger.kernel.org Date: Sat, 10 Dec 2016 22:28:25 -0800 Message-ID: <148143770485.10950.13227732273892953675.stgit@dwillia2-desk3.amr.corp.intel.com> User-Agent: StGit/0.17.1-9-g687f MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >>From [PATCH 6/8] dax: sub-division support: Device-DAX is a mechanism to establish mappings of performance / feature differentiated memory with strict fault behavior guarantees. With sub-division support a platform owner can provision sub-allocations of a dax-region into separate devices. The provisioning mechanism follows the same scheme as the libnvdimm sub-system in that a 'seed' device is created at initialization time that can be resized from zero to become enabled. Unlike the nvdimm sub-system there is no on media labelling scheme associated with this partitioning. Provisioning decisions are ephemeral / not automatically restored after reboot. While the initial use case of device-dax is persistent memory other uses case may be volatile, so the device-dax core is unable to assume the underlying memory is pmem. The task of recalling a partitioning scheme or permissions on the device(s) is left to userspace. For persistent allocations, naming, and permissions automatically recalled by the kernel, use filesystem-DAX. For a userspace helper library and utility for manipulating device-dax instances see libdaxctl and the daxctl utility here: https://github.com/pmem/ndctl --- Dan Williams (8): dax: add region-available-size attribute dax: add region 'id', 'size', and 'align' attributes dax: register seed device dax: use multi-order radix for resource lookup dax: refactor locking out of size calculation routines dax: sub-division support dax: add / remove dax devices after provisioning dax: add debug for region available_size drivers/dax/Kconfig | 1 drivers/dax/dax.c | 747 ++++++++++++++++++++++++++++++++++++++++++++++++--- 2 files changed, 698 insertions(+), 50 deletions(-)