mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>,
	Linus Torvalds <torvalds@osdl.org>,
	Paul Venezia <pvenezia@jpj.net>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ulrich Drepper <drepper@redhat.com>
Subject: Re: ext3 performance inconsistencies, 2.4/2.6
Date: Wed, 5 Nov 2003 02:14:35 -0500	[thread overview]
Message-ID: <20031105021435.W2097@devserv.devel.redhat.com> (raw)
In-Reply-To: <20031104221904.GE30612@ti19.telemetry-investments.com>; from brugolsky@telemetry-investments.com on Tue, Nov 04, 2003 at 05:19:04PM -0500

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

  parent reply	other threads:[~2003-11-05  7:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-04 19:10 Paul Venezia
2003-11-04 19:36 ` Linus Torvalds
2003-11-04 20:20   ` Bill Rugolsky Jr.
2003-11-04 20:30     ` Linus Torvalds
2003-11-04 21:07       ` Paul Venezia
2003-11-04 21:28         ` Bill Rugolsky Jr.
2003-11-04 21:40           ` Linus Torvalds
2003-11-04 22:00             ` Ulrich Drepper
2003-11-04 22:31               ` Linus Torvalds
2003-11-04 23:48                 ` Ulrich Drepper
2003-11-04 23:56                   ` Linus Torvalds
2003-11-05  0:58                   ` jlnance
2003-11-05  7:08                     ` Jakub Jelinek
2003-11-04 22:19             ` Bill Rugolsky Jr.
2003-11-04 22:26               ` Bill Rugolsky Jr.
2003-11-05  7:14               ` Jakub Jelinek [this message]
2003-11-04 21:39       ` Bill Rugolsky Jr.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20031105021435.W2097@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=brugolsky@telemetry-investments.com \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pvenezia@jpj.net \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®