All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valtteri Kiviniemi <valtteri.kiviniemi@dataproof.fi>
To: Christophe Saout <christophe@saout.de>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Strange lag with pv_ops dom0 kernel
Date: Wed, 20 May 2009 05:06:41 +0300	[thread overview]
Message-ID: <4A1365B1.2090101@dataproof.fi> (raw)
In-Reply-To: <1242778985.4384.1.camel@leto.intern.saout.de>

Hi,

I dont think that's the case because the nic is autonegotiation the link 
and in dmesg I can see right after boot:

eth0: Link is Up 100 Mbps Full Duplex, Flow Control: None
eth0: 10/100 speed: disabling TSO

- Valtteri Kiviniemi

Christophe Saout kirjoitti:
> Hi Valtteri,
> 
>> I'm testing the 2.6.30-rc3-tip pv_ops kernel with Xen 3.4 (also tried 
>> 2.6.30-rc5-tip) and everything is working fine except domU performance.
>>
>> domU's boot up quickly but theres some strange lag. For example just 
>> typing "ps aux" or "dmesg" takes 5-10 seconds to finish. Load averages 
>> are 0 and cpu-usage reported by xentop is minimal. Theres also no 
>> indication of io-wait.
> 
> This sounds like the known issue with Dom0 bouncing TSO packets.  It
> should go away once you disable TSO in your DomU's:
> 
> /usr/sbin/ethtool -K eth0 tso off
> 
> 
> 	Christophe
> 
> 

  reply	other threads:[~2009-05-20  2:06 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 12:26 [ANNOUNCE] Xen 3.4.0 released! Keir Fraser
2009-05-18 16:19 ` Valtteri Kiviniemi
2009-05-19  3:25   ` wei zhou
2009-05-19  3:32     ` Yi, Shunli
2009-05-19  4:25       ` [Xen-devel] " Keir Fraser
2009-05-19  7:53         ` wei zhou
2009-05-19 11:56           ` Stefano Stabellini
2009-05-19 16:06   ` [Xen-devel] " Ian Jackson
2009-05-19 17:36     ` Ian Jackson
2009-05-19 17:51       ` Re: [Xen-devel] " Dustin Henning
2009-05-19 17:51       ` [Xen-users] " Dustin Henning
     [not found]       ` <m2n.s.1M6Wut-002Sa1@chiark.greenend.org.uk>
2009-05-20 11:22         ` Ian Jackson
2009-05-19  0:45 ` Mark Johnson
2009-05-19  0:51   ` Keir Fraser
2009-05-19  1:23 ` zen
2009-05-19  1:34   ` Strange lag with pv_ops dom0 kernel Valtteri Kiviniemi
2009-05-19  1:58     ` Valtteri Kiviniemi
2009-05-19 23:39       ` Jeremy Fitzhardinge
2009-05-20  2:04         ` Valtteri Kiviniemi
2009-05-20  0:23     ` Christophe Saout
2009-05-20  2:06       ` Valtteri Kiviniemi [this message]
2009-05-20  7:18         ` Christophe Saout
2009-05-20 23:22           ` Valtteri Kiviniemi
2009-05-23 13:36             ` Valtteri Kiviniemi
2009-05-24 23:48         ` Debian unstable (sid) domU crashes dom0 on startup with pv_ops kernel Valtteri Kiviniemi
2009-05-24 23:56           ` Valtteri Kiviniemi
2009-05-25  1:51             ` Valtteri Kiviniemi
2009-05-25 20:29             ` Valtteri Kiviniemi
2009-05-27 22:49               ` Jeremy Fitzhardinge
2009-05-28 18:10                 ` Valtteri Kiviniemi
2009-05-19  1:42   ` [ANNOUNCE] Xen 3.4.0 released! Keir Fraser
2009-05-19  2:39     ` zen
2009-05-20  1:04     ` Dirk Utterback
2009-05-20  5:44       ` Keir Fraser
2009-05-19 16:56 ` Li, Xin
2009-05-19 17:04   ` [Xen-devel] " Pasi Kärkkäinen
2009-05-19 22:21     ` Keir Fraser
2009-05-20  6:44       ` Pasi Kärkkäinen
2009-05-20 12:13         ` [Xen-devel] " Keir Fraser

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=4A1365B1.2090101@dataproof.fi \
    --to=valtteri.kiviniemi@dataproof.fi \
    --cc=christophe@saout.de \
    --cc=xen-devel@lists.xensource.com \
    /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.