search for: opnfv

Claudio Fontana wrote on 2015-09-07: > Coming late to the party, > > On 31.08.2015 16:11, Michael S. Tsirkin wrote: >> Hello! >> During the KVM forum, we discussed supporting virtio on top >> of ivshmem. I have considered it, and came up with an alternative >> that has several advantages over that - please see below. >> Comments welcome. > > as Jan

On 18/09/2015 18:29, Claudio Fontana wrote: > The Virtio Peer shared memory communication device (virtio-peer) is a > virtual device which allows high performance low latency guest to guest > communication. It uses a new queue extension feature tentatively called > VIRTIO_F_WINDOW which indicates that descriptor tables, available and > used rings and Queue Data reside in physical

On 18/09/2015 18:29, Claudio Fontana wrote: > The Virtio Peer shared memory communication device (virtio-peer) is a > virtual device which allows high performance low latency guest to guest > communication. It uses a new queue extension feature tentatively called > VIRTIO_F_WINDOW which indicates that descriptor tables, available and > used rings and Queue Data reside in physical

On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages

On 09.09.2015 08:40, Zhang, Yang Z wrote: > Claudio Fontana wrote on 2015-09-07: >> Coming late to the party, >> >> On 31.08.2015 16:11, Michael S. Tsirkin wrote: >>> Hello! >>> During the KVM forum, we discussed supporting virtio on top >>> of ivshmem. I have considered it, and came up with an alternative >>> that has several advantages

On Tue, Sep 01, 2015 at 05:01:07PM -0700, Nakajima, Jun wrote: > On Tue, Sep 1, 2015 at 9:28 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > > On 2015-09-01 18:02, Michael S. Tsirkin wrote: > ... > >> You don't need to be able to map all guest memory if you know > >> guest won't try to allow device access to all of it. > >> It's a

On Tue, Sep 01, 2015 at 05:01:07PM -0700, Nakajima, Jun wrote: > On Tue, Sep 1, 2015 at 9:28 AM, Jan Kiszka <jan.kiszka at siemens.com> wrote: > > On 2015-09-01 18:02, Michael S. Tsirkin wrote: > ... > >> You don't need to be able to map all guest memory if you know > >> guest won't try to allow device access to all of it. > >> It's a

...l-bounces+varun.sethi=freescale.com at nongnu.org] On > Behalf Of Nakajima, Jun > Sent: Monday, August 31, 2015 1:36 PM > To: Michael S. Tsirkin > Cc: virtio-dev at lists.oasis-open.org; Jan Kiszka; > Claudio.Fontana at huawei.com; qemu-devel at nongnu.org; Linux > Virtualization; opnfv-tech-discuss at lists.opnfv.org > Subject: Re: [Qemu-devel] rfc: vhost user enhancements for vm2vm > communication > > On Mon, Aug 31, 2015 at 7:11 AM, Michael S. Tsirkin <mst at redhat.com> > wrote: > > Hello! > > During the KVM forum, we discussed supporting virt...

...l-bounces+varun.sethi=freescale.com at nongnu.org] On > Behalf Of Nakajima, Jun > Sent: Monday, August 31, 2015 1:36 PM > To: Michael S. Tsirkin > Cc: virtio-dev at lists.oasis-open.org; Jan Kiszka; > Claudio.Fontana at huawei.com; qemu-devel at nongnu.org; Linux > Virtualization; opnfv-tech-discuss at lists.opnfv.org > Subject: Re: [Qemu-devel] rfc: vhost user enhancements for vm2vm > communication > > On Mon, Aug 31, 2015 at 7:11 AM, Michael S. Tsirkin <mst at redhat.com> > wrote: > > Hello! > > During the KVM forum, we discussed supporting virt...

BTW, can you please take a look at the following URL to see my understanding is correct? Our engineers are saying that they are not really sure if they understood your proposal (especially around IOMMU), and I drew a figure, adding notes... https://wiki.opnfv.org/vm2vm_mst Thanks, -- Jun Intel Open Source Technology Center

...w storage features * High availability, live migration and fault tolerance * Emulation and TCG * Firmware: ACPI, UEFI, coreboot, U-Boot, etc. Management and infrastructure * Managing KVM: Libvirt, OpenStack, oVirt, etc. * Storage: Ceph, Gluster, SPDK, etc.r * Network Function Virtualization: DPDK, OPNFV, OVN, etc. * Provisioning =============== SUBMITTING YOUR PROPOSAL =============== Abstracts due: June 15, 2017 Please submit a short abstract (~150 words) describing your presentation proposal. Slots vary in length up to 45 minutes. Also include the proposal type -- one of: - technical talk - e...

...w storage features * High availability, live migration and fault tolerance * Emulation and TCG * Firmware: ACPI, UEFI, coreboot, U-Boot, etc. Management and infrastructure * Managing KVM: Libvirt, OpenStack, oVirt, etc. * Storage: Ceph, Gluster, SPDK, etc.r * Network Function Virtualization: DPDK, OPNFV, OVN, etc. * Provisioning =============== SUBMITTING YOUR PROPOSAL =============== Abstracts due: June 15, 2017 Please submit a short abstract (~150 words) describing your presentation proposal. Slots vary in length up to 45 minutes. Also include the proposal type -- one of: - technical talk - e...

...w storage features * High availability, live migration and fault tolerance * Emulation and TCG * Firmware: ACPI, UEFI, coreboot, U-Boot, etc. Management and infrastructure * Managing KVM: Libvirt, OpenStack, oVirt, etc. * Storage: Ceph, Gluster, SPDK, etc.r * Network Function Virtualization: DPDK, OPNFV, OVN, etc. * Provisioning ======================== SUBMITTING YOUR PROPOSAL ======================== Abstracts due: June 15, 2019 Please submit a short abstract (~150 words) describing your presentation proposal. Slots vary in length up to 45 minutes. Submit your proposal here: https://events....