xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Jacek Konieczny <jajcus@jajcus.net>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Wei Liu <wei.liu2@citrix.com>, Mariusz Mazur <mmazur@axeos.com>,
	xen-devel@lists.xen.org
Subject: Re: [BUG] VIF rate limiting locks up network in the whole system
Date: Fri, 09 May 2014 15:43:08 +0200	[thread overview]
Message-ID: <536CDB6C.60505@jajcus.net> (raw)
In-Reply-To: <1399640478.561.7.camel@kazak.uk.xensource.com>

On 05/09/14 15:01, Ian Campbell wrote:
> On Fri, 2014-05-09 at 14:44 +0200, Jacek Konieczny wrote:
>>
>> I have tried that:
>>
>> xl create -p ratelimittest1.cfg
>> xenstore-rm /local/domain/0/backend/vif/3/0/feature-gso-tcpv6
>> xenstore-rm /local/domain/0/backend/vif/3/0/feature-ipv6-csum-offload
>> xenstore-rm /local/domain/0/backend/vif/3/0/feature-split-event-channels
>>
>> It didn't help. Nothing had exploded, though.
> 
> Can you tell if those features were actually enabled or not afterwards?
> ethtool in the guest and on the dom0 vifX.Y device should have changed,
> or possibly it would be reflected in the dmesg.

ethtool in the guest changes when I change the offload settings, though
my ethtool doesn't seem to show IPv6 offloading settings.

In dom0 'ethtool -k' output doesn't change, as this seems to be
triggered by the guest features, which are written to xenstore after the
domain is unpaused and the kernel boots.

> For split event channel I think there will be only one evtchn key in
> xenstore instead of two.

Yes, and there is only one 'event-channel' instead of separate RX and TX
channels.

So it seems, the 'xenstore-rm' does the trick, at list partially.

Greets,
    Jacek

      reply	other threads:[~2014-05-09 13:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09  7:03 [BUG] VIF rate limiting locks up network in the whole system Jacek Konieczny
2014-05-09  9:18 ` Ian Campbell
2014-05-09 10:25   ` Jacek Konieczny
2014-05-09 10:32     ` Ian Campbell
2014-05-09 11:44       ` Jacek Konieczny
2014-05-09 11:55         ` Ian Campbell
2014-05-09 12:44           ` Jacek Konieczny
2014-05-09 13:01             ` Ian Campbell
2014-05-09 13:43               ` Jacek Konieczny [this message]

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=536CDB6C.60505@jajcus.net \
    --to=jajcus@jajcus.net \
    --cc=Ian.Campbell@citrix.com \
    --cc=mmazur@axeos.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.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).