Messages in this thread | | | Date | Wed, 5 Nov 2003 02:14:35 -0500 | From | Jakub Jelinek <> | Subject | Re: ext3 performance inconsistencies, 2.4/2.6 |
| |
On Tue, Nov 04, 2003 at 05:19:04PM -0500, Bill Rugolsky Jr. wrote: > On Fedora 0.95, Pentium M 1.6GHz, 2.4.22-1.2115.nptl, glibc-2.3.2-10, (NPTL 0.60), > I get: > > Version 1.03 ------Sequential Output------ --Sequential Input- --Random- > -Per Chr- --Block-- -Rewrite- -Per Chr- --Block-- --Seeks-- > Machine Size K/sec %CP K/sec %CP K/sec %CP K/sec %CP K/sec %CP /sec %CP > NPTL 100M 13070 100 +++++ +++ 14141 4 13099 100 +++++ +++ +++++ +++ > LinuxThreads 100M 25957 100 +++++ +++ 20037 5 26777 99 +++++ +++ +++++ +++ > > Ugh, still there.
BTW, there are 3 different cases where locking might be different in glibc. When -lpthread is not linked in, when -lpthread is linked in but pthread_create hasn't been compiled yet and when first pthread_create has been compiled already.
Could you post numbers for all these cases (ie. run the benchmark, then link the benchmark against -lpthread as well and rerun it and last link it against -lpthread and add: static void * tf (void *a) { return NULL; }
... pthread_t pt; pthread_create (&pt, NULL, tf, 0); pthread_join (pt, NULL); ... to benchmark's main (in each case NPTL and LinuxThreads)?
Jakub - 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/
| |