From: torvalds@transmeta.com (Linus Torvalds)
To: linux-kernel@vger.kernel.org
Subject: Re: horrible disk thorughput on itanium
Date: Fri, 7 Dec 2001 06:15:50 +0000 (UTC) [thread overview]
Message-ID: <9upmqm$7p4$1@penguin.transmeta.com> (raw)
In-Reply-To: <p73r8q86lpn.fsf@amdsim2.suse.de> <Pine.LNX.4.33.0112070710120.747-100000@mikeg.weiden.de>
In article <Pine.LNX.4.33.0112070710120.747-100000@mikeg.weiden.de>,
Mike Galbraith <mikeg@wen-online.de> wrote:
>
>> Andrew Morton <akpm@zip.com.au> writes:
>>
>> As far as I can see bonnie++ doesn't use putc_unlocked, but putc.
>
>Plain old Bonnie suffered from the same thing. I long ago made it
>use putc_unlocked() here because throughput was horrible otherwise.
Oh, yeah, blame it on bonnie.
"Our C library 'putc' is horribly sucky"
"Well, then, use something else then".
Isn't somebody ashamed of glibc and willing to try to fix it? It might
be as simple as just testing a static flag "have I used pthread_create"
or even a function pointer that gets switched around at pthread_create..
"putc()" is a standard function. If it sucks, let's get it fixed. And
instead of changing bonnie, how about pinging the _real_ people who
write sucky code?
Linus
next prev parent reply other threads:[~2001-12-07 6:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011206110713.A8404@cox.rr.com.suse.lists.linux.kernel>
[not found] ` <3C0FD955.4510B738@zip.com.au.suse.lists.linux.kernel>
2001-12-06 22:13 ` horrible disk thorughput on itanium Andi Kleen
2001-12-07 6:11 ` Mike Galbraith
2001-12-07 6:15 ` Linus Torvalds [this message]
2001-12-07 12:32 ` Greg Hennessy
2001-12-07 17:57 ` Marco Colombo
[not found] <p73r8q86lpn.fsf@amdsim2.suse.de.suse.lists.linux.kernel>
[not found] ` <Pine.LNX.4.33.0112070710120.747-100000@mikeg.weiden.de.suse.lists.linux.kernel>
[not found] ` <9upmqm$7p4$1@penguin.transmeta.com.suse.lists.linux.kernel>
2001-12-07 13:54 ` Andi Kleen
2001-12-07 14:20 ` Padraig Brady
2001-12-07 16:14 ` Richard Gooch
2001-12-07 17:18 ` Robert Love
2001-12-07 17:40 ` Richard Gooch
2001-12-07 17:48 ` Robert Love
2001-12-07 17:45 ` Linus Torvalds
2001-12-07 17:58 ` Andi Kleen
2001-12-07 18:14 ` Michael Poole
2001-12-07 18:35 ` Padraig Brady
2001-12-07 21:22 ` Michael Poole
2001-12-07 21:37 ` Padraig Brady
2001-12-07 22:26 ` Michael Poole
2001-12-07 18:15 ` Linus Torvalds
2001-12-07 18:41 ` Padraig Brady
2001-12-07 18:33 ` Padraig Brady
2001-12-07 20:44 ` Greg Hennessy
2001-12-07 21:37 ` Marco Colombo
2001-12-07 20:42 ` David S. Miller
2001-12-07 6:42 Dan Kegel
-- strict thread matches above, loose matches on Subject: below --
2001-12-06 16:07 Greg Hennessy
2001-12-06 16:17 ` Arjan van de Ven
2001-12-06 20:47 ` Andrew Morton
2001-12-09 23:13 ` Kurt Garloff
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='9upmqm$7p4$1@penguin.transmeta.com' \
--to=torvalds@transmeta.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox