netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <xen-devel@lists.xenproject.org>,
	<ian.campbell@citrix.com>, <wei.liu2@citrix.com>
Subject: Re: [PATCHv1 net] xen-netback: support frontends without feature-rx-notify again
Date: Thu, 18 Dec 2014 17:55:31 +0000	[thread overview]
Message-ID: <54931513.8040606@citrix.com> (raw)
In-Reply-To: <20141218.125009.1837191564956948256.davem@davemloft.net>

On 18/12/14 17:50, David Miller wrote:
> From: David Vrabel <david.vrabel@citrix.com>
> Date: Thu, 18 Dec 2014 11:13:06 +0000
> 
>> Commit bc96f648df1bbc2729abbb84513cf4f64273a1f1 (xen-netback: make
>> feature-rx-notify mandatory) incorrectly assumed that there were no
>> frontends in use that did not support this feature.  But the frontend
>> driver in MiniOS does not and since this is used by (qemu) stubdoms,
>> these stopped working.
>>
>> Netback sort of works as-is in this mode except:
>>
>> - If there are no Rx requests and the internal Rx queue fills, only
>>   the drain timeout will wake the thread.  The default drain timeout
>>   of 10 s would give unacceptable pauses.
>>
>> - If an Rx stall was detected and the internal Rx queue is drained,
>>   then the Rx thread would never wake.
>>
>> Handle these two cases (when feature-rx-notify is disabled) by:
>>
>> - Reducing the drain timeout to 30 ms.
>>
>> - Disabling Rx stall detection.
>>
>> Reported-by: John <jw@nuclearfallout.net>
>> Tested-by: John <jw@nuclearfallout.net>
>> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
> 
> Applied, and I assume that 3.18 -stable needs this as well?

Yes, please.  Without it, netback just doesn't work with an important
use case.

Thanks.

David

  reply	other threads:[~2014-12-18 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18 11:13 [PATCHv1 net] xen-netback: support frontends without feature-rx-notify again David Vrabel
2014-12-18 11:51 ` Wei Liu
2014-12-18 17:50 ` David Miller
2014-12-18 17:55   ` David Vrabel [this message]
2015-01-05 11:51 ` Ian Campbell

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=54931513.8040606@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=davem@davemloft.net \
    --cc=ian.campbell@citrix.com \
    --cc=netdev@vger.kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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 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).