linux-kernel - Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <x49k2uvvbje.fsf@segfault.boston.devel.redhat.com>
Date:	Mon, 22 Jun 2015 14:32:53 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Christoph Hellwig <hch@....de>
Cc:	Dan Williams <dan.j.williams@...el.com>,
	Jens Axboe <axboe@...nel.dk>,
	"linux-nvdimm\@lists.01.org" <linux-nvdimm@...1.01.org>,
	Neil Brown <neilb@...e.de>,
	Greg KH <gregkh@...uxfoundation.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Linux ACPI <linux-acpi@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH 02/15] libnvdimm: infrastructure for btt devices

Christoph Hellwig <hch@....de> writes:

> On Mon, Jun 22, 2015 at 09:48:03AM -0700, Dan Williams wrote:
>> 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.
>
> If by partitions you mean block layer partitions: yes.  If by partitions
> you mean subdivision of nvdimms: no.

How will this subdivision be recorded?  Not all NVDIMMs support the
label specification.

Sysadmins are already familiar with partitions;  I'm not sure why we'd
deviate from that here.  What am I missing?

-Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/