All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Pasi Kärkkäinen" <pasik@iki.fi>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "Xu, Dongxiao" <dongxiao.xu@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Gerald Turner <gturner@unzane.com>
Subject: Re: Re: new netfront and occasional receive path lockup
Date: Tue, 14 Sep 2010 21:44:29 +0300	[thread overview]
Message-ID: <20100914184429.GF2804@reaktio.net> (raw)
In-Reply-To: <4C8FB6D3.7060202@goop.org>

On Tue, Sep 14, 2010 at 10:54:27AM -0700, Jeremy Fitzhardinge wrote:
>  On 09/14/2010 01:25 AM, Ian Campbell wrote:
> > On Mon, 2010-09-13 at 20:36 +0100, Jeremy Fitzhardinge wrote:
> >> On 09/13/2010 09:08 AM, Pasi Kärkkäinen wrote:
> >>> On Mon, Sep 13, 2010 at 09:01:57AM -0700, Gerald Turner wrote:
> >>>> 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..
> >> Agreed.
> > Should we also consider adding a netback option to disable it for the
> > system as a whole as well? Or are the issues strictly in-guest only?
> >
> > Perhaps netback should support a xenstore key to allow a toolstack to
> > configure this property per guest?
> 
> It depends on what the problem is.  If there's a basic problem with the
> smartpoll front<->back communication protocol then we'll probably have
> to revert the whole thing and start over.  If the bug is just something
> in the frontend then we can disable it there until resolved.
> 
> Fortunately I haven't pushed netfront smartpoll support upstream yet, so
> the userbase is still fairly limited.  I hope.
> 

There has been quite a few people on ##xen on irc complaining about it..

I think the smartpoll code has ended up in Debian Squeeze 2.6.32-5-xen kernel..
Hopefully they'll pull the "Revert "xen/netfront: default smartpoll to on"" soon..

-- Pasi

  reply	other threads:[~2010-09-14 18:44 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
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 [this message]
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=20100914184429.GF2804@reaktio.net \
    --to=pasik@iki.fi \
    --cc=Ian.Campbell@citrix.com \
    --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.