WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Re: [TEST PATCH] xen/blkfront: use blk_rq_map_sg togenerate

To: "Jeremy Fitzhardinge" <jeremy@xxxxxxxx>, "Greg Harris" <greg.harris@xxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [TEST PATCH] xen/blkfront: use blk_rq_map_sg togenerate ring entries
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Mon, 09 Feb 2009 09:52:01 +0000
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Jens Axboe <jens.axboe@xxxxxxxxxx>
Delivery-date: Mon, 09 Feb 2009 01:51:43 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <498CA8C8.6050808@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: <11773622.8411271233953279537.JavaMail.root@ouachita> <498CA8C8.6050808@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> Jeremy Fitzhardinge <jeremy@xxxxxxxx> 06.02.09 22:16 >>>
>Greg Harris wrote:
>> It looks like this patch applied against 2.6.28.2 resolves the issue for us 
>> -- our spinner has been running for two days now without a panic.  We've 
>> been testing this by spinning around an installer which creates file systems 
>> across two disks and then installs a base Linux system and some additional 
>> software.  Previously we were running into these panics towards the end of 
>> file-system creation.  
>>   
>
>Thanks very much for testing.
>
>> Will this patch be part of the next upstream kernel release?
>>   
>
>Yes, and it should go into the next stable kernel too.

But isn't this just reducing the likelihood of hitting the problem? Without
understanding why the entry limit gets exceeded (and fixing that), the
potential for this to happen again is still there.

Of course, the change made here has its own benefits, so I fully agree
it should be applied (though I wonder whether it's indeed a -stable
candidate).

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel