All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Traugott <stevegt@TerraLuna.Org>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: blocking Xen 3.X production use: soft lockup bugs
Date: Fri, 4 Aug 2006 13:21:21 -0700	[thread overview]
Message-ID: <20060804202121.GA13827@terraluna.org> (raw)
In-Reply-To: <1efc279e1b6db92d9564c61b25c06df8@cl.cam.ac.uk>

You nailed it, Keir.   

On Thu, Aug 03, 2006 at 09:03:18AM +0100, Keir Fraser wrote:
> Also older versions using sedf scheduler (which has now been patched to 
> avoid this) could end up with domain0 consuming all CPU and starving 
> other guests, leading to softlockup errors. We haven't seen any such 
> errors on our own test machines since this was fixed. Of course, that 
> doesn't mean there aren't problems with other test scenarios!

That is exactly what was happening.  I did more testing yesterday and
last night (-testing changeset 9732), and realized that I was only
seeing soft lockups on the second of two domU guests, and only when
running a heavy load in dom0.  According to 'xm vcpu-list' the second
guest was on CPU 0, as was the workload in dom0...  I added more
workload processes to consume both CPUs in dom0, and of course when I
did that, the first guest ground to a halt and started showing soft
lockups as well.

I was usually able to trigger the soft lockups in a few seconds simply
by running one or more of these in dom0:

    cat /dev/zero > /dev/null
    
Variants of 'nc -ub 255.255.255.255 10000 < /dev/zero' and 
'nc -u -l -p 10000 > /dev/null' in dom0 or domU also made things 
interesting, though I'm not sure that the network traffic is a factor.  
(Kids, don't do this on a production net...)  

So I built -unstable changeset 10868, and ran an even heavier workload
(the above, plus 'bonnie' in the guests) on dom0 and two guests
overnight, and they experienced no soft lockups; running -unstable,
changeset 10868, credit scheduler.  This same workload would have
caused soft lockups within seconds in -testing changeset 9732 using
the sedf scheduler; I may not have been able to get it started at all.
Response time remained subsecond under -unstable; -testing would have
been on its knees.

Steve
-- 
Stephen G. Traugott  (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
stevegt@TerraLuna.Org 
http://www.stevegt.com -- http://Infrastructures.Org

  reply	other threads:[~2006-08-04 20:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-02 22:25 blocking Xen 3.X production use: soft lockup bugs Ian Pratt
2006-08-03  0:27 ` Steve Traugott
2006-08-03  8:07   ` Keir Fraser
2006-08-03  8:03 ` Keir Fraser
2006-08-04 20:21   ` Steve Traugott [this message]
2006-08-05  8:50     ` Keir Fraser
2006-08-05 11:59       ` Harry Butterworth
2006-08-05 13:45         ` Keir Fraser
2006-08-05 14:33           ` Harry Butterworth
2006-08-12  1:46       ` stress testing was: " Steve Traugott
  -- strict thread matches above, loose matches on Subject: below --
2006-08-07 14:15 Harry Butterworth
2006-08-05  7:38 Ian Pratt
2006-08-02 20:54 Steve Traugott
2006-08-02 22:48 ` Steve Traugott

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=20060804202121.GA13827@terraluna.org \
    --to=stevegt@terraluna.org \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.