On Tue, Oct 11, 2016 at 12:48 PM, Konrad Rzeszutek Wilk <konrad.w...@oracle.com> wrote: > On Tue, Oct 11, 2016 at 12:28:56PM -0700, Dan Williams wrote: >> On Tue, Oct 11, 2016 at 11:33 AM, Konrad Rzeszutek Wilk >> <konrad.w...@oracle.com> wrote: >> > On Tue, Oct 11, 2016 at 10:51:19AM -0700, Dan Williams wrote: >> [..] >> >> Right, but why does the libnvdimm core need to know about this >> >> specific Xen reservation? For example, if Xen wants some in-kernel >> > >> > Let me turn this around - why does the libnvdimm core need to know about >> > Linux specific parts? Shouldn't this be OS agnostic, so that FreeBSD >> > for example can also poke a hole in this and fill it with its >> > OS-management meta-data? >> >> Specifically the core needs to know so that it can answer the Linux >> specific question of whether the pfn returned by ->direct_access() has >> a corresponding struct page or not. It's tied to the lifetime of the >> device and the usage of the reservation needs to be coordinated >> against the references of those pages. If FreeBSD decides it needs to >> reserve "struct page" capacity at the start of the device, I would >> hope that it reuses the same on-device info block that Linux is using >> and not create a new "FreeBSD-mode" device type. > > The issue here (as I understand, I may be missing something new) > is that the size of this special namespace may be different. That is > the 'struct page' on FreeBSD could be 256 bytes while on Linux it is > 64 bytes (numbers pulled out of the sky). > > Hence one would have to expand or such to re-use this.
Sure, but we could support that today. If FreeBSD lays down the info block it is free to make a bigger reservation and Linux would be happy to use a smaller subset. If we, as an industry, want this "struct page" reservation to be common we can take it to a standards body to make as a cross-OS guarantee... but I think this is separate from the Xen reservation. >> To be honest I do not yet understand what metadata Xen wants to store >> in the device, but it seems the producer and consumer of that metadata >> is Xen itself and not the wider Linux kernel as is the case with >> struct page. Can you fill me in on what problem Xen solves with this > > Exactly! >> reservation? > > The same as Linux - its variant of 'struct page'. Which I think is > smaller than the Linux one, but perhaps it is not? > If the hypervisor needs to know where it can store some metadata, can that be satisfied with userspace tooling in Dom0? Something like, "/dev/pmem0p1 == Xen metadata" and "/dev/pmem0p2 == DAX filesystem with files to hand to guests". So my question is not about the rationale for having metadata, it's why does the Linux kernel need to know about the Xen reservation? As far as I can see it is independent / opaque to the kernel.
