From: Jason Wang <jasowang@redhat.com> To: Harpreet Singh Anand <hanand@xilinx.com>, "mst@redhat.com" <mst@redhat.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>, "virtualization@lists.linux-foundation.org" <virtualization@lists.linux-foundation.org>, "netdev@vger.kernel.org" <netdev@vger.kernel.org> Cc: "tiwei.bie@intel.com" <tiwei.bie@intel.com>, "jgg@mellanox.com" <jgg@mellanox.com>, "maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>, "cunming.liang@intel.com" <cunming.liang@intel.com>, "zhihong.wang@intel.com" <zhihong.wang@intel.com>, "rob.miller@broadcom.com" <rob.miller@broadcom.com>, "xiao.w.wang@intel.com" <xiao.w.wang@intel.com>, "haotian.wang@sifive.com" <haotian.wang@sifive.com>, "lingshan.zhu@intel.com" <lingshan.zhu@intel.com>, "eperezma@redhat.com" <eperezma@redhat.com>, "lulu@redhat.com" <lulu@redhat.com>, "parav@mellanox.com" <parav@mellanox.com>, "kevin.tian@intel.com" <kevin.tian@intel.com>, "stefanha@redhat.com" <stefanha@redhat.com>, "rdunlap@infradead.org" <rdunlap@infradead.org>, "hch@infradead.org" <hch@infradead.org>, "aadam@redhat.com" <aadam@redhat.com>, "jiri@mellanox.com" <jiri@mellanox.com>, "shahafs@mellanox.com" <shahafs@mellanox.com>, "mhabets@solarflare.com" <mhabets@solarflare.com> Subject: Re: [PATCH V4 3/5] vDPA: introduce vDPA bus Date: Mon, 24 Feb 2020 14:48:48 +0800 [thread overview] Message-ID: <d6ea5dcb-3933-920b-523e-a494d323ef8a@redhat.com> (raw) In-Reply-To: <BY5PR02MB63714A03B7135F8C4054C1E8BBEC0@BY5PR02MB6371.namprd02.prod.outlook.com> On 2020/2/24 下午2:14, Harpreet Singh Anand wrote: > Is there a plan to add an API in vDPA_config_ops for getting the notification area from the VDPA device (something similar to get_notify_area in the VDPA DPDK case)? This will make the notifications from the guest (vhost_vdpa use case) to the VDPA device more efficient - at least for virtio 1.0+ drivers in the VM. > > I believe this would require enhancement to the vhost ioctl (something similar to the VHOST_USER_SLAVE_VRING_HOST_NOTIFIER_MSG). Yes, we plan to add that on top. Basically, here's what we plan to do: (sorted by urgency) 1) direct doorbell mapping as you asked here 2) direct interrupt injection (when platform support, e.g through posted interrupt) 3) control virtqueue support Thanks > > > Regards, > Harpreet >
WARNING: multiple messages have this Message-ID (diff)
From: Jason Wang <jasowang@redhat.com> To: Harpreet Singh Anand <hanand@xilinx.com>, "mst@redhat.com" <mst@redhat.com>, "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>, "kvm@vger.kernel.org" <kvm@vger.kernel.org>, "virtualization@lists.linux-foundation.org" <virtualization@lists.linux-foundation.org>, "netdev@vger.kernel.org" <netdev@vger.kernel.org> Cc: "tiwei.bie@intel.com" <tiwei.bie@intel.com>, "jgg@mellanox.com" <jgg@mellanox.com>, "maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>, "cunming.liang@intel.com" <cunming.liang@intel.com>, "zhihong.wang@intel.com" <zhihong.wang@intel.com>, "rob.miller@broadcom.com" <rob.miller@broadcom.com>, "xiao.w.wang@intel.com" <xiao.w.wang@intel.com>, "haotian.wang@sifive.com" <haotian.wang@sifive.com>, "lingshan.zhu@intel.com" <lingshan.zhu@intel.com>, "eperezma@redhat.com" <eperezma@redhat.com>, "lulu@redhat.com" <lulu@redhat.com>, "parav@mellanox.com" <parav@mellanox.com>, "kevin.tian@intel.com" <kevin.tian@intel.com>, "stefanha@redhat.com" <stefanha@redhat.com>, "rdunlap@infradead.org" <rdunlap@infradead.org>, "hch@infradead.org" <hch@infradead.org>, aadam@r Subject: Re: [PATCH V4 3/5] vDPA: introduce vDPA bus Date: Mon, 24 Feb 2020 14:48:48 +0800 [thread overview] Message-ID: <d6ea5dcb-3933-920b-523e-a494d323ef8a@redhat.com> (raw) In-Reply-To: <BY5PR02MB63714A03B7135F8C4054C1E8BBEC0@BY5PR02MB6371.namprd02.prod.outlook.com> On 2020/2/24 下午2:14, Harpreet Singh Anand wrote: > Is there a plan to add an API in vDPA_config_ops for getting the notification area from the VDPA device (something similar to get_notify_area in the VDPA DPDK case)? This will make the notifications from the guest (vhost_vdpa use case) to the VDPA device more efficient - at least for virtio 1.0+ drivers in the VM. > > I believe this would require enhancement to the vhost ioctl (something similar to the VHOST_USER_SLAVE_VRING_HOST_NOTIFIER_MSG). Yes, we plan to add that on top. Basically, here's what we plan to do: (sorted by urgency) 1) direct doorbell mapping as you asked here 2) direct interrupt injection (when platform support, e.g through posted interrupt) 3) control virtqueue support Thanks > > > Regards, > Harpreet >
next prev parent reply other threads:[~2020-02-24 6:49 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-02-20 6:11 [PATCH V4 0/5] vDPA support Jason Wang 2020-02-20 6:11 ` [PATCH V4 1/5] vhost: factor out IOTLB Jason Wang 2020-02-20 6:11 ` [PATCH V4 2/5] vringh: IOTLB support Jason Wang 2020-02-20 6:11 ` [PATCH V4 3/5] vDPA: introduce vDPA bus Jason Wang 2020-02-20 15:14 ` Jason Gunthorpe 2020-02-20 15:14 ` Jason Gunthorpe 2020-02-21 7:54 ` Jason Wang 2020-02-21 7:54 ` Jason Wang 2020-02-24 6:14 ` Harpreet Singh Anand 2020-02-24 6:14 ` Harpreet Singh Anand 2020-02-24 6:48 ` Jason Wang [this message] 2020-02-24 6:48 ` Jason Wang 2020-02-20 6:11 ` [PATCH V4 4/5] virtio: introduce a vDPA based transport Jason Wang 2020-02-20 15:19 ` Jason Gunthorpe 2020-02-20 15:19 ` Jason Gunthorpe 2020-02-21 8:06 ` Jason Wang 2020-02-21 8:06 ` Jason Wang 2020-02-20 6:11 ` [PATCH V4 5/5] vdpasim: vDPA device simulator Jason Wang 2020-02-20 15:12 ` Jason Gunthorpe 2020-02-20 15:12 ` Jason Gunthorpe 2020-02-21 7:57 ` Jason Wang 2020-02-21 7:57 ` Jason Wang 2020-02-26 6:12 ` Jason Wang 2020-02-26 6:12 ` Jason Wang 2020-02-26 17:19 ` Jason Gunthorpe 2020-02-26 17:19 ` Jason Gunthorpe 2020-02-21 8:33 ` Harpreet Singh Anand 2020-02-21 8:33 ` Harpreet Singh Anand 2020-02-21 8:50 ` Jason Wang 2020-02-21 8:50 ` Jason Wang
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=d6ea5dcb-3933-920b-523e-a494d323ef8a@redhat.com \ --to=jasowang@redhat.com \ --cc=aadam@redhat.com \ --cc=cunming.liang@intel.com \ --cc=eperezma@redhat.com \ --cc=hanand@xilinx.com \ --cc=haotian.wang@sifive.com \ --cc=hch@infradead.org \ --cc=jgg@mellanox.com \ --cc=jiri@mellanox.com \ --cc=kevin.tian@intel.com \ --cc=kvm@vger.kernel.org \ --cc=lingshan.zhu@intel.com \ --cc=linux-kernel@vger.kernel.org \ --cc=lulu@redhat.com \ --cc=maxime.coquelin@redhat.com \ --cc=mhabets@solarflare.com \ --cc=mst@redhat.com \ --cc=netdev@vger.kernel.org \ --cc=parav@mellanox.com \ --cc=rdunlap@infradead.org \ --cc=rob.miller@broadcom.com \ --cc=shahafs@mellanox.com \ --cc=stefanha@redhat.com \ --cc=tiwei.bie@intel.com \ --cc=virtualization@lists.linux-foundation.org \ --cc=xiao.w.wang@intel.com \ --cc=zhihong.wang@intel.com \ /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: linkBe 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.