This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] Re: new netfront and occasional receive path lockup

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: new netfront and occasional receive path lockup
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Tue, 14 Sep 2010 21:44:29 +0300
Cc: "Xu, Dongxiao" <dongxiao.xu@xxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>, Gerald Turner <gturner@xxxxxxxxxx>
Delivery-date: Tue, 14 Sep 2010 11:45:21 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4C8FB6D3.7060202@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <87bp82cxwn.fsf@xxxxxxxxxxxxxxxxxxxx> <D5AB6E638E5A3E4B8F4406B113A5A19A2A658C2F@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <877hiqcrxt.fsf@xxxxxxxxxxxxxxxxxxxx> <D5AB6E638E5A3E4B8F4406B113A5A19A2A658D1C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <8739tecl6i.fsf@xxxxxxxxxxxxxxxxxxxx> <87vd69bpje.fsf@xxxxxxxxxxxxxxxxxxxx> <20100913160840.GC2804@xxxxxxxxxxx> <4C8E7D33.7090902@xxxxxxxx> <1284452709.14311.16721.camel@xxxxxxxxxxxxxxxxxxxxxx> <4C8FB6D3.7060202@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
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"" 

-- Pasi

Xen-devel mailing list