All of lore.kernel.org
 help / color / mirror / Atom feed
From: xuehai zhang <hai@cs.uchicago.edu>
To: "Petersson, Mats" <mats.petersson@amd.com>
Cc: Xen Mailing List <xen-devel@lists.xensource.com>
Subject: Re: open/stat64 syscalls run faster on Xen VM than standard Linux
Date: Mon, 28 Nov 2005 08:47:31 -0600	[thread overview]
Message-ID: <438B1883.1090805@cs.uchicago.edu> (raw)
In-Reply-To: <907625E08839C4409CE5768403633E0B0EAAC3@sefsexmb1.amd.com>

Petersson, Mats wrote:
>  
> 
> 
>>-----Original Message-----
>>From: xen-devel-bounces@lists.xensource.com 
>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of 
>>xuehai zhang
>>Sent: 28 November 2005 08:21
>>To: Xen Mailing List
>>Subject: [Xen-devel] open/stat64 syscalls run faster on Xen 
>>VM than standard Linux
>>
>>Dear all,
>>When I debugged the execution performance of an application 
>>using strace, I found there are some system calls like open 
>>and stat64 which run faster on XenLinux than the standard 
>>Linux. The following is the output of running "strace -c 
>>/bin/sh -c /bin/echo foo" on both systems. An open call runs 
>>averagely 109 usec on standard Linux but only 41 usecs on 
>>XenLinux. An stat64 call runs
>>75 usecs on standard Linux but only 19 usecs on XenLinux.
>>The Xen VM runs on the same physical machine as the standard 
>>Linux. It uses loopback files in dom0 as the backends of VBDs.
>>Any insight is highly appreciated.
> 
> 
> And are you using the same Loopback file-system when running native
> Linux? If not, it's probably the main cause of the difference. 

No, the native Linux runs on a regular linux machine and use the raw hard disk partitions.
Xuehai

  reply	other threads:[~2005-11-28 14:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-28 14:36 open/stat64 syscalls run faster on Xen VM than standard Linux Petersson, Mats
2005-11-28 14:47 ` xuehai zhang [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-29 12:59 Petersson, Mats
2005-11-29 13:48 ` xuehai zhang
2005-11-28 18:17 Petersson, Mats
2005-11-28 16:15 Petersson, Mats
2005-11-28 17:16 ` xuehai zhang
2005-11-28 19:37   ` Anthony Liguori
2005-11-28 14:45 Petersson, Mats
2005-11-28 15:28 ` xuehai zhang
2005-11-28 15:50 ` xuehai zhang
2005-11-28 16:07   ` Stephen C. Tweedie
2005-11-28 16:27     ` xuehai zhang
2005-11-28 17:10       ` Stephen C. Tweedie
2005-11-29  4:50         ` Tim Freeman
2005-11-29 13:27         ` xuehai zhang
2005-11-28  8:21 xuehai zhang
2005-11-28 14:38 ` Anthony Liguori
2005-11-28 14:59   ` xuehai zhang
2005-11-29 12:39   ` xuehai zhang
2005-11-29 12:58     ` xuehai zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=438B1883.1090805@cs.uchicago.edu \
    --to=hai@cs.uchicago.edu \
    --cc=mats.petersson@amd.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.