[IA64] Weekly benchmark results [ww10]

[IA64] Weekly benchmark results [ww10]

[KUWAMURA Shin'ya]

Hi,

I report a benchmark result of this week on IPF using
ia64/xen-unstable and ia64/linux-2.6.18-xen.

On DomVTi, a kernel panic occurred when xen-vnif.ko was loaded. The
issue was fixed by reverting the following patch:
  http://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg/rev/c48f54365060

TEST ENVIRONMENT
    Machine          : Tiger4
    Kernel           : 2.6.18.8-xen
    Changeset        : 17205:716a637722e4 (ia64/xen-unstable)
		       471:ba72914de93a   (ia64/linux-2.6.18-xen)
		       78:9e4b5bb76049    (efi-vfirmware)
    Dom0 OS          : RHEL4 U2 (2P)
    DomU OS          : RHEL4 U2 (8P, using tap:aio)
    DomVTi OS        : RHEL4 U2 (8P, with PV-on-HVM drivers)
    Scheduler        : credit

TEST RESULTS
  DomU:
    unixbench4.1.0    : Pass
    bonnie++-1.03     : Pass
    ltp-full-20070930 : Pass
    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 and Fujitsu members

Re: [IA64] Weekly benchmark results [ww10]

[Masaki Kanno]

Hi,

create_workqueue() of the RHEL4U2 kernel has upper limit of 1st argument 
length.  The limit is 10.  The following code is long. 

  accel_watch_workqueue = create_workqueue("accel_watch");

Best regards,
 Kan

Fri, 14 Mar 2008 17:27:38 +0900 (JST), "KUWAMURA Shin'ya" wrote:

>Hi,
>
>I report a benchmark result of this week on IPF using
>ia64/xen-unstable and ia64/linux-2.6.18-xen.
>
>On DomVTi, a kernel panic occurred when xen-vnif.ko was loaded. The
>issue was fixed by reverting the following patch:
>  http://xenbits.xensource.com/ext/ia64/linux-2.6.18-xen.hg/rev/c48f54365060
>
>TEST ENVIRONMENT
>    Machine          : Tiger4
>    Kernel           : 2.6.18.8-xen
>    Changeset        : 17205:716a637722e4 (ia64/xen-unstable)
>		       471:ba72914de93a   (ia64/linux-2.6.18-xen)
>		       78:9e4b5bb76049    (efi-vfirmware)
>    Dom0 OS          : RHEL4 U2 (2P)
>    DomU OS          : RHEL4 U2 (8P, using tap:aio)
>    DomVTi OS        : RHEL4 U2 (8P, with PV-on-HVM drivers)
>    Scheduler        : credit
>
>TEST RESULTS
>  DomU:
>    unixbench4.1.0    : Pass
>    bonnie++-1.03     : Pass
>    ltp-full-20070930 : Pass
>    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 and Fujitsu members
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@lists.xensource.com
>http://lists.xensource.com/xen-devel

[PATCH] Reduce length of accel_watch workqueue name

[Neil Turton]

As reported reported (see link below) the first argument to
create_workqueue is limited to 10 character on RHEL4U2.  This patch
shortens the length and makes the workqueue name a little more descriptive.

http://lists.xensource.com/archives/html/xen-devel/2008-03/msg00417.html

Signed-off-by: Neil Turton <nturton@solarflare.com>

diff -r 3983b041fc51 drivers/xen/netfront/accel.c
--- a/drivers/xen/netfront/accel.c	Mon Mar 10 22:53:07 2008 +0000
+++ b/drivers/xen/netfront/accel.c	Mon Mar 17 14:01:17 2008 +0000
@@ -71,7 +71,7 @@ void netif_init_accel(void)
 	INIT_LIST_HEAD(&accelerators_list);
 	spin_lock_init(&accelerators_lock);

-	accel_watch_workqueue = create_workqueue("accel_watch");
+	accel_watch_workqueue = create_workqueue("net_accel");
 }

 void netif_exit_accel(void)

Re: [Xen-devel] [PATCH] Reduce length of accel_watch workqueue name

[KUWAMURA Shin'ya]

Hi Neil,

>>>>> On Mon, 17 Mar 2008 14:54:30 +0000
>>>>> nturton@solarflare.com(Neil Turton)  said:
> 
> -	accel_watch_workqueue = create_workqueue("accel_watch");
> +	accel_watch_workqueue = create_workqueue("net_accel");

This patch work fine. Thank you.

Best Regards,
-- 
  KUWAMURA Shin'ya