[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPcyv4jAA0=aSUDazG5hS1FS0o+qg4SyMXicqF_0M0s7_cXBGw@mail.gmail.com>
Date: Mon, 22 Jun 2015 09:48:03 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Christoph Hellwig <hch@....de>
Cc: Jens Axboe <axboe@...nel.dk>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
Boaz Harrosh <boaz@...xistor.com>,
"Kani, Toshimitsu" <toshi.kani@...com>, Neil Brown <neilb@...e.de>,
Greg KH <gregkh@...uxfoundation.org>,
"linux-kernel@...r.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
On Mon, Jun 22, 2015 at 9:34 AM, Christoph Hellwig <hch@....de> 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/
Powered by blists - more mailing lists