Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754185AbbFVQsO (ORCPT ); Mon, 22 Jun 2015 12:48:14 -0400 Received: from mail-wi0-f174.google.com ([209.85.212.174]:35530 "EHLO mail-wi0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751633AbbFVQsF (ORCPT ); Mon, 22 Jun 2015 12:48:05 -0400 MIME-Version: 1.0 In-Reply-To: <20150622163453.GA9187@lst.de> References: <20150617235209.12943.24419.stgit@dwillia2-desk3.amr.corp.intel.com> <20150617235458.12943.23425.stgit@dwillia2-desk3.amr.corp.intel.com> <20150622163453.GA9187@lst.de> Date: Mon, 22 Jun 2015 09:48:03 -0700 Message-ID: Subject: Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices From: Dan Williams To: Christoph Hellwig Cc: Jens Axboe , "linux-nvdimm@lists.01.org" , Boaz Harrosh , "Kani, Toshimitsu" , Neil Brown , Greg KH , "linux-kernel@vger.kernel.org" , Ingo Molnar , Linux ACPI , linux-fsdevel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 612 Lines: 11 On Mon, Jun 22, 2015 at 9:34 AM, Christoph Hellwig wrote: > FYI, the mess calls into libnvdimm for each register pmem or blk device > which then walks partitions to find your btt metadata is an absolutely > no go and suggest that the layering is completely fucked up. Only if you abandon BTT on partitions, which at this point it seems you're boldly committed to doing. It's unacceptable to drop BTT on the floor so I'll take a look at making BTT per-disk only for 4.2. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in Please read the FAQ at http://www.tux.org/lkml/