lkml.org 
[lkml]   [2003]   [Aug]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Nick's scheduler policy
Seems to do badly with CPU intensive tasks:

Kernbench: (make -j vmlinux, maximal tasks)
Elapsed System User CPU
2.6.0-test3 46.00 115.49 571.94 1494.25
2.6.0-test4-nick 49.37 131.31 611.15 1500.75

Oddly, schedule itself is significantly cheaper, but you seem
to end up with much more expense elsewhere. Thrashing tasks between
CPUs, maybe (esp given the increased user time)? I'll do a proper
baseline against test4, but I don't expect it to be any different, really.

diffprofile {2.6.0-test3,2.6.0-test4-nick}/kernbench/0/profile
12314 7.4% total
3843 16.3% page_remove_rmap
1657 20.8% __d_lookup
1322 9.4% do_anonymous_page
1143 21.5% __copy_to_user_ll
1034 55.3% atomic_dec_and_lock
683 48.4% free_hot_cold_page
669 393.5% filp_close
553 147.5% .text.lock.file_table
484 479.2% file_ra_state_init
409 24.3% buffered_rmqueue
391 24.9% kmem_cache_free
362 11.3% zap_pte_range
304 16.5% path_lookup
247 31.5% pte_alloc_one
237 68.3% pgd_ctor
229 19.0% file_move
224 16.7% link_path_walk
220 57.7% file_kill
188 7.9% do_no_page
164 24.6% __wake_up
162 4.4% find_get_page
146 24.4% generic_file_open
141 87.6% .text.lock.dcache
139 11.5% release_pages
131 51.4% vfs_read
127 40.2% dnotify_parent
...
-144 -4.2% __copy_from_user_ll
-149 -2.3% page_add_rmap
-352 -25.1% schedule
-3469 -6.8% default_idle

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:48    [W:0.445 / U:0.220 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site