On Thu, May 17, 2018 at 7:52 AM, George Dunlap wrote:
> On 05/15/2018 07:06 PM, Dan Williams wrote:
>> On Tue, May 15, 2018 at 7:19 AM, George Dunlap
>> wrote:
>>> So, who decides what this SPA range and interleave set is? Can the
>>> operating system change these interleave sets and mappings,
On 05/15/2018 07:06 PM, Dan Williams wrote:
> On Tue, May 15, 2018 at 7:19 AM, George Dunlap
> wrote:
>> So, who decides what this SPA range and interleave set is? Can the
>> operating system change these interleave sets and mappings, or change
>> data from PMEM to BLK, and is so, how?
>
> The
On 15/05/18 19:06, Dan Williams wrote:
> On Tue, May 15, 2018 at 7:19 AM, George Dunlap
> wrote:
>> On 05/11/2018 05:33 PM, Dan Williams wrote:
>>
>> This is all pretty foundational. Xen can read static ACPI tables, but
>> it can't do AML. So to do a proper design for Xen, we need to know:
> Oo
On Tue, May 15, 2018 at 7:19 AM, George Dunlap wrote:
> On 05/11/2018 05:33 PM, Dan Williams wrote:
>> [ adding linux-nvdimm ]
>>
>> Great write up! Some comments below...
>
> Thanks for the quick response!
>
> It seems I still have some fundamental misconceptions about what's going
> on, so I'd b
On Tue, May 15, 2018 at 5:26 AM, Jan Beulich wrote:
On 15.05.18 at 12:12, wrote:
[..]
>> That is, each fsdax / devdax namespace has a superblock that, in part,
>> defines what parts are used for Linux and what parts are used for data. Or
>> to put it a different way: Linux decides which par
On 05/11/2018 05:33 PM, Dan Williams wrote:
> [ adding linux-nvdimm ]
>
> Great write up! Some comments below...
Thanks for the quick response!
It seems I still have some fundamental misconceptions about what's going
on, so I'd better start with that. :-)
Here's the part that I'm having a hard
> On May 15, 2018, at 1:26 PM, Jan Beulich wrote:
>
On 15.05.18 at 12:12, wrote:
>>> On May 15, 2018, at 11:05 AM, Roger Pau Monne wrote:
>>> On Fri, May 11, 2018 at 09:33:10AM -0700, Dan Williams wrote:
[ adding linux-nvdimm ]
Great write up! Some comments below...
>>> On 15.05.18 at 12:12, wrote:
>> On May 15, 2018, at 11:05 AM, Roger Pau Monne wrote:
>> On Fri, May 11, 2018 at 09:33:10AM -0700, Dan Williams wrote:
>>> [ adding linux-nvdimm ]
>>>
>>> Great write up! Some comments below...
>>>
>>> On Wed, May 9, 2018 at 10:35 AM, George Dunlap
>>> wrote
> On May 15, 2018, at 11:05 AM, Roger Pau Monne wrote:
>
> Just some replies/questions to some of the points raised below.
>
> On Fri, May 11, 2018 at 09:33:10AM -0700, Dan Williams wrote:
>> [ adding linux-nvdimm ]
>>
>> Great write up! Some comments below...
>>
>> On Wed, May 9, 2018 at 10
Just some replies/questions to some of the points raised below.
On Fri, May 11, 2018 at 09:33:10AM -0700, Dan Williams wrote:
> [ adding linux-nvdimm ]
>
> Great write up! Some comments below...
>
> On Wed, May 9, 2018 at 10:35 AM, George Dunlap
> wrote:
> >> To use a namespace, an operating s
[ adding linux-nvdimm ]
Great write up! Some comments below...
On Wed, May 9, 2018 at 10:35 AM, George Dunlap wrote:
> Dan,
>
> I understand that you're the NVDIMM maintainer for Linux. I've been
> working with your colleagues to try to sort out an architecture to allow
> NVRAM to be passed to
Dan,
I understand that you're the NVDIMM maintainer for Linux. I've been
working with your colleagues to try to sort out an architecture to allow
NVRAM to be passed to guests under the Xen hypervisor.
If you have time, I'd appreciate it if you could skim through at least
the first section of the
Below is an initial draft of an NVDIMM proposal. I'll submit a patch to
include it in the tree at some point, but I thought for initial
discussion it would be easier if it were copied in-line.
I've done a fair amount of investigation, but it's quite likely I've
made mistakes. Please send me corr
13 matches
Mail list logo
