From: "hch@lst.de" <hch@lst.de>
To: Oliver <oohall@gmail.com>
Cc: "jack@suse.cz" <jack@suse.cz>,
"mawilcox@microsoft.com" <mawilcox@microsoft.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile ranges
Date: Thu, 6 Jul 2017 04:56:21 +0200 [thread overview]
Message-ID: <20170706025621.GA15122@lst.de> (raw)
In-Reply-To: <CAOSf1CHFsYFuTTKVQahbBoNrEq7Oo3=iigEzBaQviRgDrmEg3w@mail.gmail.com>
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
WARNING: multiple messages have this Message-ID (diff)
From: "hch@lst.de" <hch@lst.de>
To: Oliver <oohall@gmail.com>
Cc: "hch@lst.de" <hch@lst.de>,
Dan Williams <dan.j.williams@intel.com>,
"jack@suse.cz" <jack@suse.cz>,
"mawilcox@microsoft.com" <mawilcox@microsoft.com>,
"x86@kernel.org" <x86@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile ranges
Date: Thu, 6 Jul 2017 04:56:21 +0200 [thread overview]
Message-ID: <20170706025621.GA15122@lst.de> (raw)
In-Reply-To: <CAOSf1CHFsYFuTTKVQahbBoNrEq7Oo3=iigEzBaQviRgDrmEg3w@mail.gmail.com>
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.
next prev parent reply other threads:[~2017-07-06 2:54 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 17:52 [PATCH v4 00/16] pmem: stop abusing copy_user_nocache(), and other reworks Dan Williams
2017-06-29 17:52 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 01/16] x86, uaccess: introduce copy_from_iter_flushcache for pmem / cache-bypass operations Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 02/16] dm: add ->copy_from_iter() dax operation support Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 03/16] filesystem-dax: convert to dax_copy_from_iter() Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 04/16] dax, pmem: introduce an optional 'flush' dax_operation Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 05/16] dm: add ->flush() dax operation support Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 06/16] filesystem-dax: convert to dax_flush() Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 07/16] x86, dax: replace clear_pmem() with open coded memset + dax_ops->flush Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 08/16] x86, dax, libnvdimm: remove wb_cache_pmem() indirection Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 09/16] x86, libnvdimm, pmem: move arch_invalidate_pmem() to libnvdimm Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 10/16] x86, libnvdimm, pmem: remove global pmem api Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:53 ` [PATCH v4 11/16] libnvdimm, pmem: fix persistence warning Dan Williams
2017-06-29 17:53 ` Dan Williams
2017-06-29 17:54 ` [PATCH v4 12/16] libnvdimm, nfit: enable support for volatile ranges Dan Williams
2017-06-29 17:54 ` Dan Williams
2017-06-29 19:20 ` Linda Knippers
2017-06-29 19:20 ` Linda Knippers
2017-06-29 20:42 ` Dan Williams
2017-06-29 20:42 ` Dan Williams
2017-06-29 21:16 ` Linda Knippers
2017-06-29 21:16 ` Linda Knippers
2017-06-29 21:50 ` Dan Williams
2017-06-29 21:50 ` Dan Williams
2017-06-29 22:12 ` Linda Knippers
2017-06-29 22:12 ` Linda Knippers
2017-06-29 22:28 ` Dan Williams
2017-06-29 22:28 ` Dan Williams
2017-06-29 22:35 ` Linda Knippers
2017-06-29 22:35 ` Linda Knippers
2017-06-29 22:43 ` Dan Williams
2017-06-29 22:43 ` Dan Williams
2017-06-29 22:49 ` Linda Knippers
2017-06-29 22:49 ` Linda Knippers
2017-06-29 22:58 ` Dan Williams
2017-06-29 22:58 ` Dan Williams
2017-06-29 23:14 ` Linda Knippers
2017-06-29 23:14 ` Linda Knippers
2017-06-30 1:28 ` Dan Williams
2017-06-30 1:28 ` Dan Williams
2017-07-05 23:46 ` Kani, Toshimitsu
2017-07-05 23:46 ` Kani, Toshimitsu
2017-07-06 0:07 ` Dan Williams
2017-07-06 0:07 ` Dan Williams
2017-07-06 1:17 ` Kani, Toshimitsu
2017-07-06 1:17 ` Kani, Toshimitsu
2017-07-06 2:08 ` Dan Williams
2017-07-06 2:08 ` Dan Williams
2017-07-06 2:11 ` hch
2017-07-06 2:11 ` hch
2017-07-06 2:53 ` Oliver
2017-07-06 2:53 ` Oliver
2017-07-06 2:56 ` hch [this message]
2017-07-06 2:56 ` hch
2017-06-29 17:54 ` [PATCH v4 13/16] dax: remove default copy_from_iter fallback Dan Williams
2017-06-29 17:54 ` Dan Williams
2017-06-29 17:54 ` [PATCH v4 14/16] dax: convert to bitmask for flags Dan Williams
2017-06-29 17:54 ` Dan Williams
2017-06-29 17:54 ` [PATCH v4 15/16] libnvdimm, pmem, dax: export a cache control attribute Dan Williams
2017-06-29 17:54 ` Dan Williams
2017-06-29 17:54 ` [PATCH v4 16/16] libnvdimm, pmem: disable dax flushing when pmem is fronting a volatile region Dan Williams
2017-06-29 17:54 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170706025621.GA15122@lst.de \
--to=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mawilcox@microsoft.com \
--cc=oohall@gmail.com \
--cc=viro@zeniv.linux.org.uk \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.