From: Randy Dunlap <rdunlap@infradead.org>
To: Jason Wang <jasowang@redhat.com>,
mst@redhat.com, linux-kernel@vger.kernel.org,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org
Cc: tiwei.bie@intel.com, jgg@mellanox.com,
maxime.coquelin@redhat.com, cunming.liang@intel.com,
zhihong.wang@intel.com, rob.miller@broadcom.com,
xiao.w.wang@intel.com, haotian.wang@sifive.com,
lingshan.zhu@intel.com, eperezma@redhat.com, lulu@redhat.com,
parav@mellanox.com, kevin.tian@intel.com, stefanha@redhat.com,
hch@infradead.org, aadam@redhat.com, jiri@mellanox.com,
shahafs@mellanox.com, hanand@xilinx.com, mhabets@solarflare.com
Subject: Re: [PATCH V3 4/5] virtio: introduce a vDPA based transport
Date: Wed, 19 Feb 2020 20:07:49 -0800 [thread overview]
Message-ID: <2c5a3a84-be56-3003-8d71-d46645664bab@infradead.org> (raw)
In-Reply-To: <20200220035650.7986-5-jasowang@redhat.com>
On 2/19/20 7:56 PM, Jason Wang wrote:
> diff --git a/drivers/virtio/Kconfig b/drivers/virtio/Kconfig
> index 9c4fdb64d9ac..0df3676b0f4f 100644
> --- a/drivers/virtio/Kconfig
> +++ b/drivers/virtio/Kconfig
> @@ -43,6 +43,19 @@ config VIRTIO_PCI_LEGACY
>
> If unsure, say Y.
>
> +config VIRTIO_VDPA
> + tristate "vDPA driver for virtio devices"
> + select VDPA
> + select VIRTIO
> + help
> + This driver provides support for virtio based paravirtual
> + device driver over vDPA bus. For this to be useful, you need
> + an appropriate vDPA device implementation that operates on a
> + physical device to allow the datapath of virtio to be
> + offloaded to hardware.
> +
> + If unsure, say M.
> +
Please use tabs consistently for indentation, not spaces,
except in the Kconfig help text, which should be 1 tab + 2 spaces.
> config VIRTIO_PMEM
> tristate "Support for virtio pmem driver"
> depends on VIRTIO
--
~Randy
next prev parent reply other threads:[~2020-02-20 4:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 3:56 [PATCH V3 0/5] vDPA support Jason Wang
2020-02-20 3:56 ` [PATCH V3 1/5] vhost: factor out IOTLB Jason Wang
2020-02-20 4:04 ` Randy Dunlap
2020-02-20 5:39 ` Jason Wang
2020-02-20 3:56 ` [PATCH V3 2/5] vringh: IOTLB support Jason Wang
2020-02-20 3:56 ` [PATCH V3 3/5] vDPA: introduce vDPA bus Jason Wang
2020-02-20 4:06 ` Randy Dunlap
2020-02-20 5:40 ` Jason Wang
2020-02-20 3:56 ` [PATCH V3 4/5] virtio: introduce a vDPA based transport Jason Wang
2020-02-20 4:07 ` Randy Dunlap [this message]
2020-02-20 5:40 ` Jason Wang
2020-02-20 3:56 ` [PATCH V3 5/5] vdpasim: vDPA device simulator Jason Wang
2020-02-20 4:09 ` Randy Dunlap
2020-02-20 5:41 ` 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=2c5a3a84-be56-3003-8d71-d46645664bab@infradead.org \
--to=rdunlap@infradead.org \
--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=jasowang@redhat.com \
--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=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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).