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

Re: [Xen-devel] [Patch 2 of 2]: PV-domain SMP performance Linux-part

To: Juergen Gross <juergen.gross@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Patch 2 of 2]: PV-domain SMP performance Linux-part
From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
Date: Mon, 19 Jan 2009 17:32:16 +0000
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Delivery-date: Mon, 19 Jan 2009 09:32:40 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=Q1ede+8YFqq9wF7N62jN5EjEBux/lTK5fSYyxukalE4=; b=cPculheKx9/CcTj6BzdT7AR+FxXpca7utQ8Fs984/f/cI1PV4KFAG0UvRjUlviJelr gpUyvBnfkC0w78XSkmVlstPjWm0DegdOLyr3+w1vFF0Wtm0p2qjA7q+CP/6Jg1rXcU0a DvUhinBGw/n/DcqhDI4us/33FyKhwRTZqpodA=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=wvhoUUrRxNgdNzlgRsN8aWXOr6X1Ju9f+4uSxXR+PK//RxpMbPgVZ0YG4itoEjM0xA 31mVXY1oGaiVyiqqsKkk6eBV1w7WkkZ7TAp1SdvSmQJsmgsb12c73f9PnNQlxu6e4JO+ JAhHEbqGKHZVoLGWhEhYSO1PRLHyPG9HYCj28=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <496B3DD3.6010402@xxxxxxxxxxxxxxxxxxx>
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: <494B7892.76E4.0078.0@xxxxxxxxxx> <C5712033.206AD%keir.fraser@xxxxxxxxxxxxx> <de76405a0812190715r7f105f75rf4cbcede1fdd86e3@xxxxxxxxxxxxxx> <496B3DD3.6010402@xxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, Jan 12, 2009 at 12:55 PM, Juergen Gross
<juergen.gross@xxxxxxxxxxxxxxxxxxx> wrote:
> Conclusion:
> -----------
> Differences not really big, but my "no deschedule" patch had least elapsed
> time for build-jobs, while scp was able to transfer same amount of data as
> in slower original system.
> The "Yield in spinlock" patch had slightly better dbench performance, but
> interactive shell commands were a pain sometimes! I suspect some problem in
> George's patches during low system load to be the main reason for this
> behaviour. Without George's patches the "Yield in spinlock" was very similar
> to the original system.

Hmm, the shell performance is a little worrying.  There may be
something strange going on...

Without my patches (at least, without the "yield reduces priority"
patch), "yield" is basically a no-op, so "yield in spinlock" is
functionally equivalent to the original system.

According to your numbers, the "user time" and "system time" were
exactly the same (only 0.6 seconds longer on system time), even though
the overall build took 52 seconds longer.  Is it possible that the
"yield" patches actually made it run less often?

scp works over tcp, which is often sensitive to latency; so it's
possible that the lowered priority on yield caused "hiccoughs", both
in the scp connections, and the interactive shell performance.

Anyway, I'll be looking into it after doing a scheduler update.

Peace,
 -George

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