From: David Mosberger <davidm@hpl.hp.com>
To: "David S. Miller" <davem@redhat.com>
Cc: davidm@hpl.hp.com, anton@samba.org, linux-kernel@vger.kernel.org,
zippel@linux-m68k.org
Subject: Re: thread_info implementation
Date: Mon, 11 Feb 2002 18:46:00 -0800 [thread overview]
Message-ID: <15464.33256.837784.657759@napali.hpl.hp.com> (raw)
In-Reply-To: <20020211.183603.111204707.davem@redhat.com>
In-Reply-To: <15464.30088.754007.311391@napali.hpl.hp.com> <20020211.182208.102575913.davem@redhat.com> <15464.32354.452126.182563@napali.hpl.hp.com> <20020211.183603.111204707.davem@redhat.com>
>>>>> On Mon, 11 Feb 2002 18:36:03 -0800 (PST), "David S. Miller" <davem@redhat.com> said:
DaveM> All performance tests I ran were "about the same" on sparc64,
DaveM> on x86 we really only have one anomaly on one of Linus's SMP
DaveM> x86 machines (fork+exec from lmbench on dual-Athlon) and I'm
DaveM> going to push to investigate that further.
OK, so back to square one: why am I supposed to do all this work for
something that will likely slow things slightly down and, at best,
doesn't hurt performance? The old set up works great and as far as
I'm concerned, is not broken.
Don't get me wrong. I'm willing to invest time to switch to the new
setup, but I'd like to have a good reason before doing so. That's not
asking for too much, is it?
--david
next prev parent reply other threads:[~2002-02-12 2:46 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 21:08 Roman Zippel
2002-02-11 20:50 ` Anton Blanchard
2002-02-12 0:01 ` Roman Zippel
2002-02-12 0:10 ` David Howells
2002-02-12 0:22 ` Roman Zippel
2002-02-12 0:46 ` David S. Miller
2002-02-12 0:57 ` Roman Zippel
2002-02-12 0:57 ` David S. Miller
2002-02-12 1:10 ` Roman Zippel
2002-02-12 13:01 ` Bjorn Wesen
2002-02-12 13:49 ` David S. Miller
2002-02-12 1:01 ` David Mosberger
2002-02-12 1:21 ` David Mosberger
2002-02-12 1:36 ` David Mosberger
2002-02-12 1:53 ` David Mosberger
2002-02-12 2:30 ` David Mosberger
2002-02-12 2:46 ` David Mosberger [this message]
2002-02-12 3:01 ` David Mosberger
2002-02-12 3:18 ` David Mosberger
2002-02-12 3:32 ` David Mosberger
2002-02-12 4:16 ` David Mosberger
2002-02-12 4:33 ` David Mosberger
2002-02-12 5:26 ` Richard Henderson
2002-02-12 5:50 ` David Mosberger
2002-02-13 11:18 ` Anton Blanchard
2002-02-12 5:32 ` David S. Miller
2002-02-12 5:57 ` Richard Henderson
2002-02-12 2:49 ` Davide Libenzi
2002-02-12 1:07 ` David S. Miller
2002-02-12 1:32 ` David S. Miller
2002-02-12 1:41 ` David S. Miller
2002-02-12 2:22 ` David S. Miller
2002-02-12 2:36 ` David S. Miller
2002-02-12 2:51 ` David S. Miller
2002-02-12 3:04 ` David S. Miller
2002-02-12 3:23 ` David S. Miller
2002-02-12 3:42 ` David S. Miller
2002-02-12 4:21 ` David S. Miller
2002-02-12 17:14 ` Pavel Machek
2002-02-13 0:46 ` David S. Miller
2002-02-13 1:30 ` Roman Zippel
2002-02-12 9:12 ` Roman Zippel
2002-02-12 9:30 ` Jeff Garzik
2002-02-12 10:14 ` Roman Zippel
2002-02-12 13:21 ` David Howells
2002-02-12 19:15 ` David Mosberger
2002-02-12 19:38 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2002-02-11 17:39 Arkadiy Chapkis - Arc
2002-02-11 20:19 ` Robert Love
2002-02-11 20:42 ` Luigi Genoni
2002-02-11 20:48 ` Robert Love
2002-02-11 23:37 ` Jeff Garzik
2002-02-11 23:49 ` Richard Henderson
2002-02-12 0:09 ` Dave Jones
2002-02-12 0:20 ` Jeff Garzik
2002-02-12 0:24 ` Dave Jones
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=15464.33256.837784.657759@napali.hpl.hp.com \
--to=davidm@hpl.hp.com \
--cc=anton@samba.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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®