[Xen-ia64-devel] [IA64] Weekly benchmark results [ww42]
Hi, I report a benchmark result of this week on IPF using ia64/xen-unstable and ia64/linux-2.6.18-xen. On domU, syslog01 failed in LTP, but passed when tested again. TEST ENVIRONMENT Machine : Tiger4 Kernel : 2.6.18.8-xen Changeset: 18688:02c8733e2d91 (ia64/xen-unstable) 705:c87adc976013 (ia64/linux-2.6.18-xen) 131:9210bd27a551 (efi-vfirmware) ea324bf(qemu-xen-unstable) Dom0 OS : RHEL4 U2 (2P) DomU OS : RHEL4 U2 (8P, using tap:aio) DomVTi OS: RHEL4 U2 (8P, with PV-on-HVM drivers) CONFIG_QEMU : ioemu-remote TEST RESULTS DomU: unixbench4.1.0: Pass bonnie++-1.03 : Pass ltp-full-20070930 : 1/835 FAIL (syslog01) iozone3_191 : Pass lmbench-3.0-a5: Pass DomVTi: unixbench4.1.0: Pass bonnie++-1.03 : Pass ltp-full-20070930 : Pass iozone3_191 : Pass lmbench-3.0-a5: Pass Best regards, KUWAMURA Shin'ya and Fujitsu members ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] [IA64] Weekly benchmark results [ww42]
Hi Isaku, On <[EMAIL PROTECTED]> Isaku Yamahata wrote: > > On Fri, Oct 19, 2007 at 06:30:54PM +0900, KUWAMURA Shin'ya wrote: > > The failures related with direct IO were fixed. > > Since the dio issues begun when xenLinux base version was > changed from 2.6.16 to 2.6.18, I supposed that it was > not Xen VMM issue, but linux kernel or ltp issue. > However nothing backed it up. I think diotest failures are caused by bugs of Linux kernel 2.6.18, because the native 2.6.18 kernel also fails and failures disappeared by updating to 2.6.18.8. Best Regards, -- KUWAMURA Shin'ya ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
Re: [Xen-ia64-devel] [IA64] Weekly benchmark results [ww42]
On Fri, Oct 19, 2007 at 06:30:54PM +0900, KUWAMURA Shin'ya wrote: > I report a benchmark result of this week on IPF using > ia64/xen-unstable and ia64/linux-2.6.18-xen. > > The failures related with direct IO were fixed. Hi. Have you got any idea which c/s resolved it? By quick scanning the change log, I wasn't able to find it. Since the dio issues begun when xenLinux base version was changed from 2.6.16 to 2.6.18, I supposed that it was not Xen VMM issue, but linux kernel or ltp issue. However nothing backed it up. -- yamahata ___ Xen-ia64-devel mailing list Xen-ia64-devel@lists.xensource.com http://lists.xensource.com/xen-ia64-devel
