Hi Xie,
(2014/11/10 17:07), Xie, Huawei wrote:
> Here all layer 2 implementations are required to return same type of
> vhost_net_device_ops function pointers to
> layer 1, so layer 1 need to do some kind of preprocessing of its message or
> wrap some private message ctx in like vhost_device_ctx
Hi Xie,
(2014/11/08 5:43), Xie, Huawei wrote:
>> -struct vhost_net_device_ops const *get_virtio_net_callbacks(void);
>> +struct vhost_net_device_ops const *get_virtio_net_callbacks(
>> +vhost_driver_type_t type);
> Tetsuya:
> I feel currently it is better we still keep the common
> ge
> -Original Message-
> From: Tetsuya Mukawa [mailto:mukawa at igel.co.jp]
> Sent: Sunday, November 09, 2014 10:13 PM
> To: Xie, Huawei; dev at dpdk.org
> Cc: nakajima.yoshihiro at lab.ntt.co.jp; masutani.hitoshi at lab.ntt.co.jp
> Subject: Re: [dpdk-dev] [RFC PATCH 3/7
> -struct vhost_net_device_ops const *get_virtio_net_callbacks(void);
> +struct vhost_net_device_ops const *get_virtio_net_callbacks(
> + vhost_driver_type_t type);
Tetsuya:
I feel currently it is better we still keep the common
get_virtio_net_callbacks().
For the message flow from c
This patch adds an abstraction layer to interpret messages from QEMU.
This abstraction layer is needed because there are differences in
message formats between vhost-cuse and vhost-user.
Signed-off-by: Tetsuya Mukawa
---
lib/librte_vhost/vhost-net-cdev.c | 2 +-
lib/librte_vhost/vhost-net.h
5 matches
Mail list logo
