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

[Xen-devel] How come same structure has different sizes for dom0 and domU

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
From: "Lily Huang" <ushuanglily@xxxxxxxxx>
Date: Fri, 9 Jun 2006 15:55:34 -0400
Delivery-date: Fri, 09 Jun 2006 12:55:57 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=k3KnpPna5aE72NTK2UIw4satkXE48YeNaX/eH26d2zVDj4tCXorc7Fr476tIjulyW6RzVHzx7UH47jnI9zw8sqtDKmpwrl9ZYoC77Ljjmrz4R6WqrtvHMQM601qFqJxuIiSTQbKiMZ6ykgTtHPC0iVPUjgXUTtkcgcVi368wvPo=
List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I found that dentry and inode have different sizes in Dom0 and domU. In particular,

in Dom0:

dentry: 128 bytes
inode: 312 bytes

in DomU:

dentry: 132 bytes
inode: 344 bytes

How could this happen? Is there any way to make them same?

lily

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

Follow-Ups:
- Re: [Xen-devel] How come same structure has different sizes for dom0 and domU
  - From: Chris Wright

Prev by Date: [Xen-devel] Re: [Xen-changelog] [xen-unstable] [LINUX][XENBUS] replace xenbus_transaction_t with an opaque transaction ID.
Next by Date: [Xen-devel] [PATCH] cpuid handling for guest
Previous by thread: [Xen-devel] Re: [Xen-changelog] [xen-unstable] [LINUX][XENBUS] replace xenbus_transaction_t with an opaque transaction ID.
Next by thread: Re: [Xen-devel] How come same structure has different sizes for dom0 and domU
Index(es):
- Date
- Thread

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