[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170706025621.GA15122@lst.de>
Date: Thu, 6 Jul 2017 04:56:21 +0200
From: "hch@....de" <hch@....de>
To: Oliver <oohall@...il.com>
Cc: "hch@....de" <hch@....de>, Dan Williams <dan.j.williams@...el.com>,
"jack@...e.cz" <jack@...e.cz>,
"mawilcox@...rosoft.com" <mawilcox@...rosoft.com>,
"x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile
ranges
On Thu, Jul 06, 2017 at 12:53:13PM +1000, Oliver wrote:
> The main use case is provisioning install media for bare metal
> servers. Traditionally that's been handled by having the BMC emulate a
> USB CD drive. Unfortunately, most BMCs have limited CPU, limited
> memory and a wet-string network connection so a host based alternative
> is nice to have.
If they are CD replacement they should be marked as read-only, which
would solve any concerns about them being volatile or not.
Powered by blists - more mailing lists