[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] linux c/s 391

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>, <steven.smith@xxxxxxxxxxxxx>
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Mon, 21 Jan 2008 09:59:37 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 21 Jan 2008 01:59:30 -0800
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

The comment in the first hunk of that patch contradicts the added code:
mdelay() is a busy wait loop, i.e. CPU consumption is getting worse. Is it
possible that msleep() or msleep_interruptible() was meant to be used
here?

Additionally, since blktap was derived from blkback, shouldn't a similar
change bo done there?

Jan


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

Follow-Ups:
- [Xen-devel] Re: linux c/s 391
  - From: Keir Fraser

Prev by Date: [Xen-devel] VMX status report. Xen: #16764 & Xen0: #391 -- one new issue
Next by Date: Re: [Xen-devel] [PATCH 2 of 2] Make tools/check scripts cross-friendly
Previous by thread: [Xen-devel] VMX status report. Xen: #16764 & Xen0: #391 -- one new issue
Next by thread: [Xen-devel] Re: linux c/s 391
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.