From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from newverein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 1754C20958969 for ; Wed, 5 Jul 2017 19:54:44 -0700 (PDT) Date: Thu, 6 Jul 2017 04:56:21 +0200 From: "hch@lst.de" Subject: Re: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile ranges Message-ID: <20170706025621.GA15122@lst.de> References: <595589CF.5010605@hpe.com> <1499297819.2042.5.camel@hpe.com> <1499303324.2042.7.camel@hpe.com> <20170706021118.GA14468@lst.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Oliver Cc: "jack@suse.cz" , "mawilcox@microsoft.com" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "linux-nvdimm@lists.01.org" , "viro@zeniv.linux.org.uk" , "linux-fsdevel@vger.kernel.org" , "hch@lst.de" List-ID: 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. _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752807AbdGFC4Y (ORCPT ); Wed, 5 Jul 2017 22:56:24 -0400 Received: from verein.lst.de ([213.95.11.211]:57711 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752315AbdGFC4X (ORCPT ); Wed, 5 Jul 2017 22:56:23 -0400 Date: Thu, 6 Jul 2017 04:56:21 +0200 From: "hch@lst.de" To: Oliver Cc: "hch@lst.de" , Dan Williams , "jack@suse.cz" , "mawilcox@microsoft.com" , "x86@kernel.org" , "linux-kernel@vger.kernel.org" , "linux-nvdimm@lists.01.org" , "viro@zeniv.linux.org.uk" , "linux-fsdevel@vger.kernel.org" Subject: Re: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile ranges Message-ID: <20170706025621.GA15122@lst.de> References: <595589CF.5010605@hpe.com> <1499297819.2042.5.camel@hpe.com> <1499303324.2042.7.camel@hpe.com> <20170706021118.GA14468@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.