Messages in this thread |  | | Date | Wed, 17 May 2023 15:43:03 +0800 | | Subject | Re: Re: [PATCH v2 1/2] virtio: abstract virtqueue related methods | | From | zhenwei pi <> |
| |
On 5/17/23 15:39, Christoph Hellwig wrote: > On Wed, May 17, 2023 at 10:54:23AM +0800, zhenwei pi wrote: >> All the vring based virtqueue methods could be abstratct in theory, >> MST suggested that add/get bufs and kick functions are quite perfmance >> sensitive, so export these functions from virtio_ring.ko, drivers >> still call them in a fast path. > > Who is going to use this? And why do you think every virtio users > would want to pay for indirect calls just for your shiny new feature? > > This seems like an amazingly bad idea to me.
Hi,
I have a plan to introduce 'Virtio Over Fabrics'(TCP&RDMA) as Virtio transport, as mentioned in cover letter of this series: 3 weeks ago, I posted a proposal 'Virtio Over Fabrics': https://lists.oasis-open.org/archives/virtio-comment/202304/msg00442.html
Jason and Stefan pointed out that a non-vring based virtqueue has a chance to overwrite virtqueue instead of using vring virtqueue.
-- zhenwei pi
|  |