From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pasi =?iso-8859-1?Q?K=E4rkk=E4inen?= Subject: Re: Re: new netfront and occasional receive path lockup Date: Tue, 14 Sep 2010 21:44:29 +0300 Message-ID: <20100914184429.GF2804@reaktio.net> References: <87bp82cxwn.fsf@headboard.unzane.com> <877hiqcrxt.fsf@headboard.unzane.com> <8739tecl6i.fsf@headboard.unzane.com> <87vd69bpje.fsf@headboard.unzane.com> <20100913160840.GC2804@reaktio.net> <4C8E7D33.7090902@goop.org> <1284452709.14311.16721.camel@zakaz.uk.xensource.com> <4C8FB6D3.7060202@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: Content-Disposition: inline In-Reply-To: <4C8FB6D3.7060202@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: "Xu, Dongxiao" , "xen-devel@lists.xensource.com" , Ian Campbell , Gerald Turner List-Id: xen-devel@lists.xenproject.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=E4rkk=E4inen wrote: > >>> On Mon, Sep 13, 2010 at 09:01:57AM -0700, Gerald Turner wrote: > >>>> Then I restarted all domUs with use_smartpoll=3D0 and haven't had = any > >>>> lockups in 7 hours. > >>>> > >>> I think we should default xen/stable-2.6.32.x to use_smartpoll=3D0 = 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? >=20 > 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. >=20 > Fortunately I haven't pushed netfront smartpoll support upstream yet, s= o > the userbase is still fairly limited. I hope. >=20 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 ke= rnel.. Hopefully they'll pull the "Revert "xen/netfront: default smartpoll to on= "" soon.. -- Pasi