All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Wang <jasowang@redhat.com>
To: jiangyiwen <jiangyiwen@huawei.com>,
	stefanha@redhat.com, stefanha@gmail.com
Cc: netdev@vger.kernel.org, kvm@vger.kernel.org,
	virtualization@lists.linux-foundation.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH 2/5] VSOCK: support fill data to mergeable rx buffer in host
Date: Thu, 8 Nov 2018 16:20:45 +0800	[thread overview]
Message-ID: <83572636-5027-0ffa-3b1e-1d1d44907f03@redhat.com> (raw)
In-Reply-To: <5BE397CA.5060000@huawei.com>


On 2018/11/8 上午9:56, jiangyiwen wrote:
> On 2018/11/7 21:32, Jason Wang wrote:
>> On 2018/11/7 下午3:11, jiangyiwen wrote:
>>> On 2018/11/7 14:18, Jason Wang wrote:
>>>> On 2018/11/6 下午2:30, jiangyiwen wrote:
>>>>>> Seems duplicated with the one used by vhost-net.
>>>>>>
>>>>>> In packed virtqueue implementation, I plan to move this to vhost.c.
>>>>>>
>>>>> Yes, this code is full copied from vhost-net, if it can be packed into
>>>>> vhost.c, it would be great.
>>>>>
>>>> If you try to reuse vhost-net, you don't even need to care about this:)
>>>>
>>>> Thanks
>>>>
>>>>
>>>> .
>>>>
>>> Hi Jason,
>>>
>>> Thank your advice, I will consider your idea. But I don't know
>>> what's stefan's suggestion? It seems that he doesn't care much
>>> about this community.:(
>> I think not. He is probably busy these days.
>>
>>
>>> I still hope this community can have some vitality.
>>>
>> Let's wait for few more days for the possible comments from Stefan or Michael. But I do prefer to unify the virtio networking datapath which will be easier to be extended and maintained.
>>
>> Thanks
>>
>>
>> .
>>
> Hi Jason,
>
> Actually vsock use virtio-net as transport path should be a better idea,
> I will try to consider the new idea.
>
> Thanks,
> Yiwen.
>

Good to know this and thanks!

  reply	other threads:[~2018-11-08 17:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05  7:45 [PATCH 2/5] VSOCK: support fill data to mergeable rx buffer in host jiangyiwen
2018-11-06  3:43 ` Jason Wang
2018-11-06  6:30   ` jiangyiwen
2018-11-07  6:18     ` Jason Wang
2018-11-07  7:11       ` jiangyiwen
2018-11-07 13:32         ` Jason Wang
2018-11-07 13:32         ` Jason Wang
2018-11-08  1:56           ` jiangyiwen
2018-11-08  1:56           ` jiangyiwen
2018-11-08  8:20             ` Jason Wang [this message]
2018-11-08  8:20             ` Jason Wang
2018-11-07  7:11       ` jiangyiwen
2018-11-07  6:18     ` Jason Wang
2018-11-06  6:30   ` jiangyiwen
2018-11-06  3:43 ` Jason Wang
2018-11-05  7:45 jiangyiwen

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=83572636-5027-0ffa-3b1e-1d1d44907f03@redhat.com \
    --to=jasowang@redhat.com \
    --cc=jiangyiwen@huawei.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=stefanha@gmail.com \
    --cc=stefanha@redhat.com \
    --cc=virtualization@lists.linux-foundation.org \
    /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 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.