All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Gerald Turner <gturner@unzane.com>
Cc: "Xu, Dongxiao" <dongxiao.xu@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Re: new netfront and occasional receive path lockup
Date: Mon, 13 Sep 2010 19:08:40 +0300	[thread overview]
Message-ID: <20100913160840.GC2804@reaktio.net> (raw)
In-Reply-To: <87vd69bpje.fsf@headboard.unzane.com>

On Mon, Sep 13, 2010 at 09:01:57AM -0700, Gerald Turner wrote:
> Gerald Turner <gturner@unzane.com> writes:
> 
> > "Xu, Dongxiao" <dongxiao.xu@intel.com> writes:
> >
> >> Thanks for your detail information.
> >>
> >> Unfortunately I don't have such platform that could launch more than
> >> 10 guests in hand.
> >>
> >> Here is another patch (see attached file) that fix another potential
> >> race.
> >>
> >> Do you have bandwidth to have a try? Thanks in advance!
> >>
> >
> > I built a kernel with your additional patch.
> >
> > I have it running on all 13 domU's with use_smartpoll=1.
> >
> > I'll report tomorrow morning whether there were any lockups.
> >
> > FYI, total today I had 6 lockups with use_smartpoll=1 and the previous
> > patch.
> >
> 
> Sorry bad news again...
> 
> Had 5 lockups within 4 hours.
> 
> Then I restarted all domUs with use_smartpoll=0 and haven't had any
> lockups in 7 hours.
>

I think we should default xen/stable-2.6.32.x to use_smartpoll=0 for the time being
until this is sorted out..

-- Pasi

  reply	other threads:[~2010-09-13 16:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-22 16:43 new netfront and occasional receive path lockup Christophe Saout
2010-08-22 18:37 ` Christophe Saout
2010-08-24  0:53   ` Jeremy Fitzhardinge
2010-08-23 14:26 ` Christophe Saout
2010-08-23 16:04   ` Konrad Rzeszutek Wilk
2010-08-23 17:09     ` Christophe Saout
2010-08-24  0:46 ` Jeremy Fitzhardinge
2010-08-25  0:51   ` Xu, Dongxiao
2010-09-09 18:50     ` Pasi Kärkkäinen
2010-09-10  0:55       ` Jeremy Fitzhardinge
2010-09-10  1:45         ` Xu, Dongxiao
2010-09-10  2:25           ` Jeremy Fitzhardinge
2010-09-10  2:37             ` Xu, Dongxiao
2010-09-10  2:42               ` Jeremy Fitzhardinge
2010-09-12  1:00           ` Gerald Turner
2010-09-12  8:55             ` Jeremy Fitzhardinge
2010-09-12 17:23               ` Pasi Kärkkäinen
2010-09-12 22:40               ` Gerald Turner
2010-09-13  0:03                 ` Gerald Turner
2010-09-13  0:54                   ` Xu, Dongxiao
2010-09-13  2:12                     ` Gerald Turner
2010-09-13  2:34                       ` Xu, Dongxiao
2010-09-13  4:38                         ` Gerald Turner
2010-09-13 16:01                           ` Gerald Turner
2010-09-13 16:08                             ` Pasi Kärkkäinen [this message]
2010-09-13 19:36                               ` Jeremy Fitzhardinge
2010-09-14  8:25                                 ` Ian Campbell
2010-09-14 17:54                                   ` Jeremy Fitzhardinge
2010-09-14 18:44                                     ` Pasi Kärkkäinen
2010-09-15  9:46                                       ` Ian Campbell
2010-09-14  0:26                             ` Xu, Dongxiao

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=20100913160840.GC2804@reaktio.net \
    --to=pasik@iki.fi \
    --cc=dongxiao.xu@intel.com \
    --cc=gturner@unzane.com \
    --cc=jeremy@goop.org \
    --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.