All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
	xen-devel@lists.xensource.com, Adam Heath <doogie@brainfood.com>
Subject: Re: Loopback Performance (Was Re: Disk naming)
Date: Fri, 15 Apr 2005 19:12:23 -0500	[thread overview]
Message-ID: <42605867.30202@us.ibm.com> (raw)
In-Reply-To: <200504160029.15936.mark.williamson@cl.cam.ac.uk>

Mark Williamson wrote:

>On Friday 15 April 2005 23:11, Anthony Liguori wrote:
>  
>
>I'm sorry but I don't follow this.  The inodes for the filesystem inside it 
>only need to be looked up by the guest filesystem driver.  The inode for the 
>disk file only needs to be looked up once in dom0 when the file is opened 
>(the metadata will then be cached).  Am I missing something?
>  
>
I meant looking up the data blocks in the inode.  You may be hitting 
triple-indirect blocks twice.

I don't know enough about the kernel level caching to say anything 
definitive.  I do have some ideas who to ask though.

Regards,
Anthony Liguori

>The data you've collected are interesting though.  I wonder if searching the 
>LKML archives might yield any interesting discussion about the loop device's 
>behaviour.
>
>Cheers,
>Mark
>  
>

      reply	other threads:[~2005-04-16  0:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-15 21:44 Disk naming (Was Re: [PATCH] Guest boot loadersupport[1/2]) Ian Pratt
2005-04-15 22:11 ` Loopback Performance (Was Re: Disk naming) Anthony Liguori
2005-04-15 23:29   ` Mark Williamson
2005-04-16  0:12     ` Anthony Liguori [this message]

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=42605867.30202@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=doogie@brainfood.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --cc=mark.williamson@cl.cam.ac.uk \
    --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.