From: Jakub Jelinek <jakub@redhat.com>
To: jlnance@unity.ncsu.edu
Cc: Ulrich Drepper <drepper@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: ext3 performance inconsistencies, 2.4/2.6
Date: Wed, 5 Nov 2003 02:08:32 -0500 [thread overview]
Message-ID: <20031105020832.V2097@devserv.devel.redhat.com> (raw)
In-Reply-To: <20031105005816.GA5971@ncsu.edu>; from jlnance@unity.ncsu.edu on Tue, Nov 04, 2003 at 07:58:16PM -0500
On Tue, Nov 04, 2003 at 07:58:16PM -0500, jlnance@unity.ncsu.edu wrote:
> On Tue, Nov 04, 2003 at 03:48:28PM -0800, Ulrich Drepper wrote:
> >
> > The first is the old nptl code, the second LinuxThreads, the third the
> > current nptl code.
>
> By current, do you mean what is in Fedora, or you personal development copy?
Ulrich meant glibc CVS HEAD.
For some reason, stdio locking was not using the jump around lock prefix
variant of locking:
__asm __volatile ("cmpl $0, %%gs:%P6\n\t" \
"je,pt 0f\n\t" \
"lock\n" \
"0:\tcmpxchgl %1, %2\n\t" \
"jnz _L_mutex_lock_%=\n\t" \
".subsection 1\m\t" ...
but one without the first 2 insns, so there were 2 instructions with lock
prefix in putc and similar functions even when only one thread was running.
Jakub
next prev parent reply other threads:[~2003-11-05 7:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 19:10 ext3 performance inconsistencies, 2.4/2.6 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 [this message]
2003-11-04 22:19 ` Bill Rugolsky Jr.
2003-11-04 22:26 ` Bill Rugolsky Jr.
2003-11-05 7:14 ` Jakub Jelinek
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=20031105020832.V2097@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=drepper@redhat.com \
--cc=jlnance@unity.ncsu.edu \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.