On 17/01/2017 20:00, Michael S. Tsirkin wrote:
>>> vhost user is not supposed to use maskfd at all.
>>>
>>> We have this code:
>>>if (net->nc->info->type == NET_CLIENT_DRIVER_VHOST_USER) {
>>>dev->use_guest_notifier_mask = false;
>>>}
>>>
>>> isn't it effective?
>>
>>
On Tue, Jan 17, 2017 at 06:53:17PM +, Felipe Franciosi wrote:
>
> > On 17 Jan 2017, at 10:41, Michael S. Tsirkin wrote:
> >
> > On Fri, Jan 13, 2017 at 10:29:46PM +, Felipe Franciosi wrote:
> >>
> >>> On 13 Jan 2017, at 10:18, Michael S. Tsirkin wrote:
> >>>
> >>> On Fri, Jan 13, 2017
> On 17 Jan 2017, at 10:41, Michael S. Tsirkin wrote:
>
> On Fri, Jan 13, 2017 at 10:29:46PM +, Felipe Franciosi wrote:
>>
>>> On 13 Jan 2017, at 10:18, Michael S. Tsirkin wrote:
>>>
>>> On Fri, Jan 13, 2017 at 05:15:22PM +, Felipe Franciosi wrote:
> On 13 Jan 2017, at 09:04
On Mon, Jan 16, 2017 at 06:27:12PM +, Felipe Franciosi wrote:
> Hi Michael,
>
> > On 16 Jan 2017, at 10:22, Michael S. Tsirkin wrote:
> >
> > On Thu, Jan 12, 2017 at 05:14:07PM -0800, Felipe Franciosi wrote:
> >> Currently, VQs are started as soon as a SET_VRING_KICK is received. That
> >> i
On Fri, Jan 13, 2017 at 10:29:46PM +, Felipe Franciosi wrote:
>
> > On 13 Jan 2017, at 10:18, Michael S. Tsirkin wrote:
> >
> > On Fri, Jan 13, 2017 at 05:15:22PM +, Felipe Franciosi wrote:
> >>
> >>> On 13 Jan 2017, at 09:04, Michael S. Tsirkin wrote:
> >>>
> >>> On Fri, Jan 13, 2017
Hi Michael,
> On 16 Jan 2017, at 10:22, Michael S. Tsirkin wrote:
>
> On Thu, Jan 12, 2017 at 05:14:07PM -0800, Felipe Franciosi wrote:
>> Currently, VQs are started as soon as a SET_VRING_KICK is received. That
>> is too early in the VQ setup process, as the backend might not yet have
>> a call
On Thu, Jan 12, 2017 at 05:14:07PM -0800, Felipe Franciosi wrote:
> Currently, VQs are started as soon as a SET_VRING_KICK is received. That
> is too early in the VQ setup process, as the backend might not yet have
> a callfd to notify in case it received a kick and fully processed the
> request/co
> On 13 Jan 2017, at 10:18, Michael S. Tsirkin wrote:
>
> On Fri, Jan 13, 2017 at 05:15:22PM +, Felipe Franciosi wrote:
>>
>>> On 13 Jan 2017, at 09:04, Michael S. Tsirkin wrote:
>>>
>>> On Fri, Jan 13, 2017 at 03:09:46PM +, Felipe Franciosi wrote:
Hi Marc-Andre,
> On 1
On Fri, Jan 13, 2017 at 05:15:22PM +, Felipe Franciosi wrote:
>
> > On 13 Jan 2017, at 09:04, Michael S. Tsirkin wrote:
> >
> > On Fri, Jan 13, 2017 at 03:09:46PM +, Felipe Franciosi wrote:
> >> Hi Marc-Andre,
> >>
> >>> On 13 Jan 2017, at 07:03, Marc-André Lureau wrote:
> >>>
> >>> H
> On 13 Jan 2017, at 09:04, Michael S. Tsirkin wrote:
>
> On Fri, Jan 13, 2017 at 03:09:46PM +, Felipe Franciosi wrote:
>> Hi Marc-Andre,
>>
>>> On 13 Jan 2017, at 07:03, Marc-André Lureau wrote:
>>>
>>> Hi
>>>
>>> - Original Message -
Currently, VQs are started as soon as a
On Fri, Jan 13, 2017 at 03:09:46PM +, Felipe Franciosi wrote:
> Hi Marc-Andre,
>
> > On 13 Jan 2017, at 07:03, Marc-André Lureau wrote:
> >
> > Hi
> >
> > - Original Message -
> >> Currently, VQs are started as soon as a SET_VRING_KICK is received. That
> >> is too early in the VQ s
Hi Marc-Andre,
> On 13 Jan 2017, at 07:03, Marc-André Lureau wrote:
>
> Hi
>
> - Original Message -
>> Currently, VQs are started as soon as a SET_VRING_KICK is received. That
>> is too early in the VQ setup process, as the backend might not yet have
>
> I think we may want to reconsid
Hi
- Original Message -
> Currently, VQs are started as soon as a SET_VRING_KICK is received. That
> is too early in the VQ setup process, as the backend might not yet have
I think we may want to reconsider queue_set_started(), move it elsewhere, since
kick/call fds aren't mandatory to p
Currently, VQs are started as soon as a SET_VRING_KICK is received. That
is too early in the VQ setup process, as the backend might not yet have
a callfd to notify in case it received a kick and fully processed the
request/command. This patch only starts a VQ when a SET_VRING_CALL is
received.
Sig
14 matches
Mail list logo
