回复：您好！
高级秘书、助理和行政人员技能提高训练营 行政管理实操训练 以上课程北上广即将开班，详情请阅读附件 ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver
> > Are you saying do it as existing i.e ACPI pmem like interface? > > The reason we have created this new driver is exiting pmem driver > > does not define proper semantics for guest flushing requests. > > At this point I'm caring about the Linux-internal interface, and > for that it should be integrated into the nvdimm subsystem and not > a block driver. How the host <-> guest interface looks is a different > idea. > > > > > Regarding block support of driver, we want to achieve DAX support > > to bypass guest page cache. Also, we want to utilize existing DAX > > capable file-system interfaces(e.g fsync) from userspace file API's > > to trigger the host side flush request. > > Well, if you want to support XFS+DAX better don't make it a block > devices, because I'll post patches soon to stop using the block device > entirely for the DAX case. o.k I will look at your patches once they are in mailing list. Thanks for the heads up. If I am guessing it right, we don't need block device additional features for pmem? We can bypass block device features like blk device cache flush etc. Also, still we would be supporting ext4 & XFS filesystem with pmem? If there is time to your patches can you please elaborate on this a bit. Thanks, Pankaj ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver
On Tue, Oct 17, 2017 at 03:40:56AM -0400, Pankaj Gupta wrote: > Are you saying do it as existing i.e ACPI pmem like interface? > The reason we have created this new driver is exiting pmem driver > does not define proper semantics for guest flushing requests. At this point I'm caring about the Linux-internal interface, and for that it should be integrated into the nvdimm subsystem and not a block driver. How the host <-> guest interface looks is a different idea. > > Regarding block support of driver, we want to achieve DAX support > to bypass guest page cache. Also, we want to utilize existing DAX > capable file-system interfaces(e.g fsync) from userspace file API's > to trigger the host side flush request. Well, if you want to support XFS+DAX better don't make it a block devices, because I'll post patches soon to stop using the block device entirely for the DAX case. ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
Re: [Qemu-devel] [RFC 2/2] KVM: add virtio-pmem driver
> > I think this driver is at entirely the wrong level. > > If you want to expose pmem to a guest with flushing assist do it > as pmem, and not a block driver. Are you saying do it as existing i.e ACPI pmem like interface? The reason we have created this new driver is exiting pmem driver does not define proper semantics for guest flushing requests. Regarding block support of driver, we want to achieve DAX support to bypass guest page cache. Also, we want to utilize existing DAX capable file-system interfaces(e.g fsync) from userspace file API's to trigger the host side flush request. Below link has details of previous discussion: https://marc.info/?l=kvm&m=150091133700361&w=2 Thanks, Pankaj ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
Re: [RFC 2/2] KVM: add virtio-pmem driver
I think this driver is at entirely the wrong level. If you want to expose pmem to a guest with flushing assist do it as pmem, and not a block driver. ___ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
